Issue #270
Monday · July 20, 2026
🥖 Palate Cleanser
Maybe AWS' AI capex is much bigger than they are letting on... For a few hours on July 16, AWS told customers they owed them many many monies. One Redditor whose real spend was $0.19 got an estimate near $2.5 billion, and the numbers climbed as high as $2.5 trillion, comfortably more than most countries' GDP. On its status page AWS insisted only estimated billing data was affected and real invoices were never touched, blaming "an issue with unit pricing within the estimated billing computation subsystem." Translation: a recent change dropped in a wrong unit price and multiplied everyone's usage into Monopoly money. The first fix flopped, and corrected numbers didn't land until noon Pacific on Saturday. Just a display bug, but the fake numbers fired budget alarms into finance and security teams, and a cost anomaly looks exactly like a compromise until someone opens CloudTrail.
Less fun but more useful, on July 14 AWS pushed GuardDuty AI Protection to general availability, extending threat detection to AI workloads on Amazon Bedrock and SageMaker. Like the rest of GuardDuty it reads CloudTrail management and data events, flagging anomalous model invocations, "cost harvesting" attacks where stolen credentials fire expensive inputs to burn your tokens and GPU time, and direct prompt injection caught through Amazon Bedrock Guardrails, an integration available only for Bedrock. It arrives as part of a broader Security Hub retooling for AI and multicloud threats, and echoes June's investigations preview that auto-triages findings with confidence scores and MITRE ATT&CK mapping, the same "point a reasoning agent at your telemetry" bet Victor's ClickOps Sentinel makes in this week's Chef's Selection.
This issue is also available to share online. Got feedback? Tell us here.
📋 Chef's selections
OIDC tokens can now restrict which AWS roles they assume
by Aidan Steele
Aidan (self-proclaimed squirrel on meth) went digging into a barely-documented new STS condition key, sts:RoleAuthorizedByIdp, and reverse-engineered how it actually works. An OIDC token can now carry a https://aws.amazon.com/roles claim listing one or more role ARNs it is permitted to assume, and AssumeRoleWithWebIdentity checks that allow-list before it even looks at the role's trust policy. Put role X's ARN in the token, ask for role Y, and STS rejects you with InvalidIdentityToken regardless of what Y's trust policy allows. It's near-useless today unless you run your own IdP (matches must be literal ARNs, no wildcards, and CloudTrail only logs the field when it's present), but it hands identity providers a real veto over role selection that a misconfigured trust policy can't undo.
Introducing ClickOps Sentinel: AI Context for AWS Console Changes
by Victor Grenu
Even in shops that live by IaC, someone eventually opens the console and clicks stuff. Victor's open-source ClickOps Sentinel catches those moments off the CloudTrail sessionCredentialFromConsole flag, which AWS sets server-side for every console-session API call. Each triggered detection is handed to a Claude agent on Bedrock that retraces the whole console session via LookupEvents, checks adjacent activity from the same IP, and emits a reasoned verdict (manual-change-confirmed / likely-sanctioned-activity / suspicious) with security and FinOps implications. I'm not sure how good this will be in a large environment but seems better than another "someone changed a security group" ping.
Investigating Persistence Mechanisms in AWS
by Jan Blažek
Jan walks the four persistence techniques that can survive long after you think an incident is closed. 1. backdoor IAM users, 2. iam:UpdateAssumeRolePolicy to whitelist an external account, 3. malicious Lambda code, and 4. sts:GetFederationToken sessions. He pairs each with queries (over ingested CloudTrail data, not native CloudTrail) to hunt them, including pivoting from a federated session back to the source IAM user. It's a reference guide rather than novel research, but it's a clean, AWS-native investigation playbook worth keeping around.
💸 Sponsor shoutout
Meet Pleri: your AI security engineer. She’s not a chatbot. Pleri proactively finds meaningful security work and fixes issues before they become problems. Learn more about Pleri and see her in action.
🥗 AWS security blogs
- 📢 Amazon GameLift Streams now supports IAM role credentials for stream sessions
- 📢 Amazon CloudWatch Logs announces intelligent tiering for storage
- 📢 Amazon Cognito now supports importing users with password hashes
- 📢 Amazon CloudWatch announces lookup processor for log enrichment
- 📢 AWS IAM Identity Center achieves FedRAMP Class C Certification
- 📢 Introducing Amazon GuardDuty AI Protection for AWS AI workloads
- 📢 AWS Security Hub now provides AI inventory for organization-wide visibility of AI assets
- 📢 Amazon WorkSpaces Personal simplifies bulk PCoIP to DCV protocol migration
- 📢 OpenAI GPT-5.6 Sol, Terra, and Luna now generally available on Amazon Bedrock
- AWS Weekly Roundup: AWS Builder Center at 1 year, Network Scanning in Security Hub, Loom for AWS, and more (July 13, 2026) by Esra Kayabali
- Integrate Amazon Connect with AWS Managed AD via IAM Identity Center by Makendran Gunasekaran
- Fine-grained Amazon Route 53 access with IAM condition keys (Part 3) by Daniel Yu
- ICYMI: June 2026 @AWS Security by Rodolfo Brenes
- Security Hub adds AI workload protection and multicloud support for Microsoft Azure by Michael Fuller
- Authenticate legitimate AI agent traffic with AWS WAF Bot Control by Harith Gaddamanugu
- New compliance guidance available: HITRUST i1 on AWS by Abdul Javid
🍛 Reddit threads on r/aws
🤖 Dessert
Every machine-tracked change this week. Nobody else assembles this.
🧁 IAM permission changes
🍪 API changes
🍹 IAM managed policy changes
☕ CloudFormation resource changes
No resource updates this week.