Issue #274
Monday · August 17, 2026
🥖 Palate Cleanser
I work for a cloud security company. I've seen some things but this is special. I hope it's just a poorly written announcement or I'm too dumb to parse it correctly. Please someone tell me if it's me and I'll apologize.
AWS shipped IAM Role Manager, which creates IAM roles for you while you are clicking through a service console. The console calls a new AcquireRole API, it finds a matching AWS-managed template (?), and it provisions the role or reuses (wat?) one that already matches. The pitch is that nobody should have to design permissions before they can get started, and this clicky clicky interface makes it easy.
I mean, this would have been perfect if it were 2016 and not 2026. Maybe I'm super out of touch with what new customers need, but don't most people now just ask their AI to make their role for them? Regardless, that's not even the issue. Someone needed a promo and this got it for them. Congrats.
Nah, even my AI, which is blessed with toaster-level intelligence, spotted the real issue and quipped at me, "Which is fine right up until the template is for running your own code." That's because AWS cannot divine pre-defined permissions for running your code. So it does the thing we've been telling every engineer not to do for decades: it attaches an overly permissive PowerUserAccess policy, ON PURPOSE, like a cave dweller. And then they tell us, "When you’re ready, you can disable role manager and get IAM Access Analyzer unused access analysis," like we don't have infinite evidence that telling people to do least privilege after the fact doesn't work. Humans WILL NOT scope-down permissions voluntarily once things are working.
My dudes and dudettes, you've done such good work over the last couple of years pulling everyone back to secure defaults after the mistakes of the past. Please no.
This issue is also available to share online. Got feedback? Tell us here.
📋 Chef's selections
A few notes on AWS Nitro Enclaves: KMS integration
by Paweł Płatek
This one is a couple of weeks old and it should have been in the last issue. My bad. A Nitro Enclave is a stripped-down VM carved out of an EC2 instance to hold your most sensitive code, and AWS lets you lock a KMS key to one exact build of it, proven by a signed attestation document the enclave sends to KMS. The document proves the code and nothing else, and it is not tied to the request it travels with, so for the five minutes it stays valid the untrusted machine underneath can reuse it to call KMS itself, or to change which key and which ciphertext your enclave ends up working on. "Only my enclave can use this key" is a weaker promise than it sounds, and the rest of the post is a checklist of everywhere the integration bites.
TrailTool 1.0: Identity-First Sessions for CloudTrail
by Alex Smolen
TrailTool is Alex's open-source tool for turning raw CloudTrail into sessions, so you can ask what one identity actually did instead of scrolling a firehose of individual events. Working out where a CLI session started and stopped used to be guesswork from timestamps, but when AWS added OAuth to its MCP server, CloudTrail began carrying a real sign-in session ID for agent activity, and 1.0 is a rebuild around reading that field instead of approximating. The payoff is being able to answer which agent did this, rather than which role did this.
A closed network path is not a closed execution path
Nothing profound here, but a nice reminder that event driven architectures in the cloud require a different lens than classic apps. Ramesh wired two accounts together with no network route between them. A message lands on an SQS queue in dev, an event source mapping invokes a Lambda in staging, the staging execution role does the work and answers on a second queue. Then he built the nastier version, where a cross-account EventBridge policy lets an outside account post the event, and the Lambda hands it to an EKS application that reads the message and deletes whichever security group it names. The application was simply acting on input it should not have trusted, but it sat behind security groups, NetworkPolicies and a service mesh, so nothing in the network picture said it was reachable from outside.
💸 Sponsor shoutout
Most code shipped today is AI-generated and the triage queue grew to match. Pleri AI works out which findings are actually exploitable and submits the fix. See the platform and get a free assessment.
🥗 AWS security blogs
- 📢 AWS Certificate Manager supports switching from e-mail to DNS validation
- 📢 AWS IAM now provides role manager to set up IAM roles automatically
- 📢 Amazon Quick agentic AI capabilities are now available in AWS GovCloud (US-West)
- 📢 NVIDIA Nemotron 3.5 Lightning model is now available on Amazon SageMaker JumpStart
- 📢 AWS Marketplace now supports category-based notification subscriptions and multi-channel delivery for buyers
- 📢 AWS Identity and Access Management streamlines assignment of IAM roles to workforce users with account access manager
- Securing the AI development lifecycle with Aikido and Kiro by Len Gomes
- How to authenticate customers during chat with Amazon Connect Customer by Naga Bhargav
- Zero-trust networking for agentic AI with Amazon VPC Lattice by Jason Stinson
- Architecting HIPAA-compliant AI agents to safeguard health data with AWS by Ray Chang
- Run SAP workloads at DoD Impact Level 5 with SAP NS2 on AWS GovCloud (US) by Raj Marpu
- AWS Certificate Manager will discontinue email validation to prove domain validation for certificates by Adam Aboudi
- How AWS IAM role manager rethinks the starting point for IAM roles by Zach Jiang
- Landing Zone Accelerator Independent Assessment Report for C5:2020 now available on AWS Artifact by Kevin Donohue
- Summer 2026 SOC 1 report is now available with 185 services in scope by Baj Bajwa
- AWS successfully completed its 2025-26 NHS DSPT assessment by Tariro Dongo
- AWS completes the 2026 Police-Assured Secure Facilities (PASF) audit in Europe (London) by Tariro Dongo
- 2026 AWS CyberVadis report now available for due diligence on third-party suppliers by Tariro Dongo
🍛 Reddit threads on r/aws
🤖 Dessert
Every machine-tracked change this week. Nobody else assembles this.
🧁 IAM permission changes
No changes this week.
🍪 API changes
🍹 IAM managed policy changes
☕ CloudFormation resource changes
🎮 Amazon Linux vulnerabilities
📺 AWS security bulletins
- CVE-2026-19642 & CVE-2026-19643 - Memory-safety issues in the Base64 decoder in the AWS SDK for C++
- CVE-2026-19311- Missing Authorization in OpenSearch Alerting Plugin
- CVE-2026-18428 - OpenSearch SQL Plugin - Async Query Validation Bypass
- CVE-2026-18952 - Missing Input Validation in OpenSearch Security Analytics Plugin