playnext.fm

Topics / AWS

AWS Podcasts

A guide to how podcasts cover AWS: the shows that reference AWS most, what they focus on, and where to start. 134 episodes across 83 shows in the PlayNext corpus.

Listening guide

AWS podcasts, explained

One week, AWS is a cloud bill that needs translating. The next, it is Kubernetes made conversational, an account under attack, an infrastructure-as-code argument, or the machinery behind a large migration. Podcasts tend to approach it through the work surrounding it: operating systems at scale, controlling costs, preparing for certification, and deciding whether a particular AWS service belongs in the architecture at all.

The liveliest coverage comes from shows willing to test announcements against what engineers actually experience. More structured series offer a different pleasure: careful lessons, implementation walkthroughs, and interviews built around a single organization or project.

The weekly reality check

The Cloud Pod | Weekly AI & Cloud News on AWS, Azure & GCP is the broadest starting point. Its technically fluent panel moves quickly from announcement to consequence, with plenty of skepticism about cost, complexity, and production reality. The headlines signal its attitude. 327: AWS Finally Admits Kubernetes is Hard, Makes Robots Do It Instead and 334: AWS Makes Kubernetes Conversational turn product developments into arguments about whether automation genuinely reduces operational pain.

That same irreverence carries into infrastructure and security. 330: AWS Proves the Internet Really Is a Series of Tubes Under the Ocean tackles the physical side of cloud connectivity, while 342: Eight Minutes to Midnight: When AI Helps Hackers Speed Run Your AWS Account brings the focus back to account exposure. For cost watchers, 319: AWS Cost MCP: Your Billing Data Now Speaks Human and 337: AWS Discovers Prices Can Go Both Ways, Raises GPU Costs 15 Percent make billing part of the editorial beat rather than an afterthought.

Network Break is useful when AWS matters as one item in a wider infrastructure briefing. AWS, Google Link Public Clouds; Trading Data Center Has Zero Chill places it alongside another public-cloud provider and a separate data-center story. Expect a compact news angle, not a long AWS tutorial.

Learn the platform piece by piece

Listeners looking for a syllabus have the clearest route in Tech Exam Prep. Its AWS series separates foundational concepts into manageable subjects: [AWS CCP] 5, Well-Architected Framework Overview, [AWS CCP] 7, AWS Cloud Adoption Framework, and [AWS CCP] 8, Elasticity and Scalability. The sequence then moves into resilience with [AWS CCP] 9, High Availability and Fault Tolerance and the service relationship in [AWS CCP] 10, AWS Support Plans. This is the practical choice when free-ranging cloud conversation feels too diffuse.

Mobycast is more project-shaped. Its paired episodes, Hands On AWS - Massively Scalable Image Hosting Using S3 and CloudFront - Part 1 and Hands On AWS - Massively Scalable Image Hosting Using S3 and CloudFront - Part 2, promise a sustained walkthrough rather than a roundup. Start here when you would rather follow one system across two instalments than hear several services discussed at speed.

Cloud, Coffee & Certs - My Cloud Security Journey with You combines a security topic with specific AWS building blocks in Password Spraying Cyber Attacks | AWS Global Accelerator & Route 53 Basics. It is a narrower doorway, suited to listeners who like lessons that connect a threat with concrete networking services.

Architecture arguments and engineering trade-offs

airhacks.fm podcast with adam bien is the patient, technically dense option. Its interview style allows a guest to begin with a tool or project and work outward into architecture and history. AWS Infrastructure as Code: CloudFormation Origins, CDK Stacks, and Terraform Trade-offs is especially well framed for listeners comparing approaches rather than looking for a single prescribed answer. Lighter AWS Lambda Power Tools For Java narrows the discussion to Java and Lambda tooling.

Dev Interrupted connects AWS topics to the way engineering teams build and operate software. The show’s conversational duo tends to explain an idea, reach for a practical analogy, and then widen the question to organizational consequences. The 12 Scenarios of Failure: Applying Chaos Engineering to SAP at AWS is the reliability-focused entry. Amazon Q and The Future of Autonomous Development | AWS' Adnan Ijaz shifts toward developer tooling and autonomous development.

The AWS Podcast is calmer and more explicitly practitioner-oriented. Its host gives guests room for long technical answers, then restates the important point in plainer language. #752: Modernizing SAP with AWS is the obvious companion to Dev Interrupted’s chaos-engineering episode: one approaches SAP through modernization, the other through failure. For an AI-focused listen, #737: Accelerate your GenAI innovation journey on AWS with Innovation Sandbox solution centers the Innovation Sandbox solution.

There is also a useful dissenting route. Semaphore Uncut asks what building away from AWS might look like in Mathias Buus Madsen on Building Apps Without AWS Using Peer-to-Peer and Pear Runtime. It stands apart from the service tutorials and adoption stories because the architectural premise begins with avoidance.

AWS through customers, partners, and events

Innovation Ambassadors builds its AWS coverage around named organizations. The run from Episode 59: AWS Innovation with Greenway Health through Episode 60: AWS Innovation with Hitachi Construction Machinery, Episode 61: AWS Innovation with TransUnion, Episode 62: AWS Innovation with Inovalon, and Episode 63: AWS Innovation with PhysicsX makes the show a good browsing shelf: choose the organization that interests you and listen for how “innovation” changes from one conversation to another.

Cloud Engineering Archives - Software Engineering Daily uses re:Invent as its organizing frame. AWS re:Invent Special: The AWS Cloud Institute with Kevin Kelly points toward education, while AWS re:Invent Special: PartyRock Generative AI Apps with Mike Miller turns to generative-AI applications. AWS re:Invent Special: CircleCI with Rob Zuber brings an outside engineering platform into the event coverage. These are focused interviews for listeners who prefer one guest and one subject over a week-in-review panel.

DevCast offers a retrospective event entry in Revolutionary Tech and Insights from AWS re:Invent 2025. HashiCast pairs the same event with a specific infrastructure tool in CHANGELOG - AWS re:Invent & Terraform 1.14. The distinction is useful: DevCast promises a broader sweep of re:Invent, while HashiCast gives Terraform users a more targeted reason to listen.

Where to start

For a current, opinionated tour, begin with The Cloud Pod | Weekly AI & Cloud News on AWS, Azure & GCP and 334: AWS Makes Kubernetes Conversational. For fundamentals, use Tech Exam Prep’s [AWS CCP] 5, Well-Architected Framework Overview. Engineers weighing infrastructure-as-code choices should go directly to airhacks.fm podcast with adam bien and AWS Infrastructure as Code: CloudFormation Origins, CDK Stacks, and Terraform Trade-offs. For a concrete build spread across two episodes, queue both parts of Mobycast’s Hands On AWS - Massively Scalable Image Hosting Using S3 and CloudFront.

Featured shows below are part of the PlayNext catalog. Updated weekly.