Loading…
Loading…
technology
Hosted by Justin Brodley, Jonathan Baker, Ryan Lucas and Matt Kohn | Cloud Computing & AI News · technology · EN-US · 349 episodes
The Cloud Pod delivers weekly cloud computing and AI news for engineers, architects, and technology leaders. Join Justin Brodley, Jonathan Baker, Ryan Lucas, and Matt Kohn as they break down the latest from AWS, Azure, and Google Cloud — covering new services, platform updates, FinOps strategies, and the AI innovations reshaping the industry. Stay ahead of the cloud landscape with one of the longest-running cloud computing podcasts available.
Required Pod Score for this show. PitchCentric checks your profile against host openness, topical fit, and audience signals before you generate a pitch.
Contact path
Verified email
Booking probability
46%
Guest openness
Selective
Sign up to generate a grounded pitch for The Cloud Pod | Weekly AI & Cloud News on AWS, Azure & GCP.
Signup to Generate a PitchThe Cloud Pod | Weekly AI & Cloud News on AWS, Azure & GCP is a technology podcast hosted by Justin Brodley, Jonathan Baker, Ryan Lucas and Matt Kohn | Cloud Computing & AI News, with 349 episodes on record and a Required Pod Score of 80. PitchCentric scores this show on Booking Probability, Listen Score, and live audience signals refreshed every 24 hours.
Justin Brodley, Jonathan Baker, Ryan Lucas and Matt Kohn | Cloud Computing & AI News hosts The Cloud Pod | Weekly AI & Cloud News on AWS, Azure & GCP, a technology show with 349 episodes published.
Our AI reads these to draft pitches. Use them as grounding for a pitch that cites a real guest and a specific topic.
Episode #365
Welcome to episode 364 of The Cloud Pod, where the forecast is always cloudy! Ryan is out trying to find Hotel California, but Justin, Matt, and Jonathan are in the studio today, and they’ve got a lot of news and some great convo – from privacy in the digital age to Nova models (and a lot of employees) getting the ax, there’s a ton of stuff to cover this week, so let’s get started! Titles we almost went with this week Windows Tattletale ID Has No Off Switch Amazon’s Nova Models Enter Witness Protection Program Your PC Has a Secret Name, and Windows Won’t Erase It CloudWatch Watches Your ALB Like a Hawk One Log Group to Trace Them All Duress Code Wipes Phone, Activist Wipes Out Legally Project Perception Sees Vulnerabilities Before You Even Blink Azure DDoS Protection Trades Autopilot for Manual Control Kernel Panic Optional, CVE Overload Mandatory OpenAI’s Keypad: Key Confusion for 230 Dollars China DIYs Its Way Around DUV Export Bans OpenAI Hugged some serious Face Google must pay the EU $1 Billion… that’s a lot of Crepes Amazon apparently doesn’t believe in their AGI A big thanks to this week’s sponsors: We’re sponsorless! Want to get your brand, company, or service in front of a very enthusiastic group of cloud news seekers? You’ve come to the right place! Send us an email or hit us up on our Slack channel for more info. Follow Up 01:10 Linux kernel team publishes 432 CVEs in two days Update: Linux Kernel CVE Volume The Linux kernel team published 432 CVEs in a two-day span , continuing the high-volume vulnerability disclosure approach the kernel security team adopted after taking over CVE assignment duties directly. This follows the kernel team’s earlier decision to assign CVEs to a broad range of bug fixes, including minor or low-severity code changes, rather than reserving CVEs strictly for exploitable security flaws. The practice remains controversial among sysadmins and security teams, since large batches of CVEs can overwhelm vulnerability scanners, patch management systems, and compliance reporting workflows. For cloud operators running custom or long-term-support kernels, this reinforces the need for tooling that can filter and triage kernel CVEs by actual risk rather than treating every entry as an urgent patch target. The recurring pattern suggests this is now standard operating procedure for the kernel team rather than a one-time anomaly, so listeners managing fleets of Linux-based cloud infrastructure should expect similar large CVE batches going forward. 01:46 Justin – “Everyone is doing a lot of patching these days.” 04:42 I tried out OpenAI’s new AI keypad — which will be fun for some coders and slightly mystifying to everyone else OpenAI’s Micro keypad, developed with Work Louder , is now available for hands-on testing, following through on hardware ambitions that were previously overshadowed by legal disputes, including Apple’s trade secret laws...
Episode #364
Welcome to episode 364 of The Cloud Pod, where the forecast is always cloudy! Justin and Matt are in the studio this week to bring you all the latest in cloud and AI news, including (surprise) astronomical AWS bills, Kimi K3 and what it means for Enterprise AI, and lots of security news! All that and so much more, so let’s get started! Titles we almost went with this week Cache Rules Everything Around NFS Now Lambda Says BYOB, Bring Your Own Bucket Henrico’s Power Struggle: Data Centers 37, Schools 0 Cloud Run Fails Over Faster Than Your Excuses 570 Patches, One Registry Hive Nightmare GuardDuty Gets a Detective Agent, No Trench Coat Required Kimi K3 Aims to Moonwalk Past Opus 4.8 Terraform Gets Policy Muscle, Ditches the Rego Diet CloudWatch Watches Your AI Coders Code Watt A Way To Treat A School District Your Cloud Bill… 1 BILLION DOLLARS Not a way I want to wake up rogue cloud bills Skype is EOL … wait I thought I died 3 times already Our newest superhero CODEMENDER!! A big thanks to this week’s sponsors: We’re sponsorless! Want to get your brand, company, or service in front of a very enthusiastic group of cloud news seekers? You’ve come to the right place! Send us an email or hit us up on our Slack channel for more info. General News 00:49 Amazon fixing bug that billed some AWS customers billions of dollars A bug in the AWS billing computation subsystem generated inflated billing estimates for some customers, with one Reddit user reporting a quoted estimate near 2.5 billion dollars for a single month. In contrast, others saw figures ranging from millions to hundreds of millions. The issue began late Thursday, and an initial rollback attempt on Friday morning failed to resolve it, suggesting the root cause was more complex than a recent configuration change. Amazon confirmed the billing estimates do not reflect actual usage or charges, meaning affected customers will not be responsible for the inflated amounts shown in the console. Amazon has not disclosed whether any accounts were suspended or paused due to the billing errors, leaving open questions about operational impact during the incident. The event highlights the importance of billing system reliability for cloud providers, since inaccurate estimates at this scale can cause confusion and concern even when the underlying charges are not real. 01:29 Justin – “Amazon doesn’t bill you in the middle of the month, so it’s a pretty low risk that you were gonna get billed or invoice directly on that date, unless you happen to already be overdue on a payment and you were happening to update your credit card at the same time. I don’t think that’s really a big risk for this particular scenario.” 05:04 County With 37 Data Centers Asks Schools to ‘Conserve Electricity’ Listener note: Paywall article Henrico County, Virginia, home to 37 data centers, with 17 more planned, is asking county employees and schools to conserve electricity after a 25 percent rate increase set to begin July 1, adding an estimated 5 million dollars in costs for the next fiscal year. The sit...
Episode #362
Welcome to episode 362 of The Cloud Pod, where the weather is always cloudy! Justin, Jonathan, and Matt are in the studio, and this week we’ve got slightly less AI, but much more data news – a trend Jonathan is sure will continue. Join us as we explore Kubernetes updates, the end of Amazon Mechanical Turk, and the last of the physical media for game consoles, plus more. There’s a lot to cover, so let’s get started! Titles we almost went with this week Going Cold Turk-ey Kubernetes Rollbacks Let You Ctrl-Z Your Cluster Answer Engine Optimization Is the New SEO Game Turk-ing Point: Amazon Pulls the Plug Stop Chasing Ephemeral IPs in Your EKS Cluster Firewall Rules That Know Your Pods by Name CloudWatch Pipelines Finally Speaks Fluent OpenTelemetry Sony Discs You, Keeps Your Money Forever EKS Upgrades Finally Get an Undo Button Azure Embraces Chaos, Calls It Studio Time Mechanical Turk Turns Off The Lights For Good There Was Never Anyone Inside the Box KV Cache Me If You Can on GKE AWS Security Hub Says Hello to Azure, Finally Amazon Cancels the Internet’s Oldest Side Hustle Amazon Prime’s Next Delivery: A Pink Slip for the Turk Business as Usual – Azure announces Chaos Studio? Hello sunshine, my old Azure A big thanks to this week’s sponsors: We’re sponsorless! Want to get your brand, company, or service in front of a very enthusiastic group of cloud news seekers? You’ve come to the right place! Send us an email or hit us up on our Slack channel for more info. Follow Up 01:36 Amazon’s Mechanical Turk to stop accepting new customers – and not Even AI can save it Amazon is closing Mechanical Turk to new customers, effectively ending the crowdsourced human-labor platform that launched in 2005 and once served as a foundational tool for AI training data labeling. The service predates the current generative AI boom by nearly two decades, originally designed for tasks like image tagging, transcription, and data verification that computers couldn’t handle at the time. Ironically, the rise of AI and large language models has reduced demand for the type of human-in-the-loop micro-tasking Mechanical Turk provided, as automated systems now handle much of that labeling work. Existing customers can reportedly continue using the platform, but the halt on new signups signals that Amazon is deprioritizing the service rather than investing further in it. This closure reflects a broader shift in the AI data pipeline, where synthetic data generation and more sophisticated automated labeling tools are replacing older crowdsourced human-labor marketplaces. 02:14 Justin – “If you ever actually used the service, you’ll know that both the Turks interface that you actually did work, and the setting up the jobs was terrible anyway. It was always very difficult to use, and they never made it easier over the years. So I don’t know if they’ve ever really been investing in it heavily. But it’s definitely been around for a long time.” AI Is Going Great – or How ML Makes Money 04:11 New analytics and cost controls are available for Claude Enterprise
Sponsor detection runs nightly. Check back soon.
Based on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:
Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.
Is this podcast yours and you'd like to remove or correct details? Request removal or email privacy@pitchcentric.com.
FAQs
If you have a concern about deliverability, AI quality, data privacy, or whether this will actually work for your specific situation, it's probably answered below.
Founder Solo gives you 50 AI pitches per month using the credit model (Standard pitches cost 1 credit, Enriched pitches cost 2). Founder Pro raises that to 200 credits per month and adds full Booking Probability access, unlimited Magic Match, Apollo enrichment credits, and data export capabilities. Both plans use the same credit system, so you can stretch your monthly budget further by using Standard-mode drafting.
Agency tiers have no base fee. You pay per managed client and per talent profile. Agency Standard is $199 per client per month; Agency Pro is $399 per client per month. Both add $39 per talent profile per month. Your own team's user seats are always free.
A talent profile represents one person (founder, executive, or spokesperson) you are booking onto podcasts. It includes their bio, topics, headshots, and outreach history. Team plans include 5 profiles; agency plans are pay-as-you-go.
Yes, at any time. Upgrades take effect immediately; downgrades apply at the end of the current billing period. Contact support if you need help migrating between plan families.
Every paid plan includes a 15-day free trial. Your card is saved at signup but you will not be charged until day 16. Cancel any time from your dashboard.
You keep access until the end of your current billing period. No charges after that. Your data is retained for 30 days in case you reactivate.
Yes. Select Annual on the pricing toggle and the discounted price is applied automatically at checkout. The annual price shown is the full year cost.
That is our Enterprise tier. Contact our sales team and we will build a custom plan with volume pricing, a dedicated account manager, and SLA guarantees.
