Good Morning!
Amazon is shutting the door on new Mechanical Turk customers, which feels like the end of an era nobody was quite ready to admit had already ended. I loved that service when I was at Expensify ~15 years ago. Mechanical Turk was the honest version of what everyone now calls AI: a bunch of humans doing piecework behind a friendly API that let you pretend the intelligence was artificial. It turns out the market prefers its exploitation to at least look automated, and even the “not even AI can save it” headline writers can’t muster much sympathy for a service that spent two decades renting out human judgment by the penny.
I bring this up partly because it’s a fitting bookend, and partly because I now spend a suspicious amount of my time writing about the AI stuff that supposedly replaced it. If that’s your particular flavor of dread, most of you already know I dumped it into its own newsletter over at Artificialconfidence.com, where I can be cynical about model pricing without cluttering up this space.
Anyway, AWS spent the week bolting security features onto Azure and rebranding GPU markups as savings. Let’s get into it.
Things I Found on the Internet
Ten years of observability work condensed into one honest confession: logs are the worst part, always have been, always will be. Mat Duggan explains why ClickHouse quietly took over by being accidentally perfect for the job. The bit about your first grep ruining you forever is uncomfortably accurate.
Beth Pariseau captures the AgenticOps bind nicely: teams drowning in AI-generated defects are being sold more agents as the fix. Her reporting on the trust gap pairs the survey optimism (28.5% now trust autonomous actions) with the horror stories of agents nuking production databases and their backups. Worth your time.
GitHub offered to mail your public repo on CD-ROM to the first 1,000 askers, then yanked the form after commenters pointed out the obvious: shipping physical media makes sense when your website keeps falling over. A Sony jab that ratioed into a referendum on GitHub’s uptime. The internet remains undefeated.
Predating Fiverr by years, the human-powered crowdsourcing service that lent its name to a chess-playing hoax is quietly closing its doors to new customers July 30th. AWS won’t say why, though workers report accounts vanishing without explanation. Fitting end for a platform whose whole gimmick was people pretending to be machines.
What AWS Has For Us This Time
AWS Security Hub extends unified security management to Microsoft Azure
Watching AWS offer to secure your Azure workloads is like your ex offering relationship advice: technically helpful, Azure is absolutely not going to do it themselves, but I’m deeply suspicious about their motives, JENNIFER.
Amazon EKS Auto Mode reduces GPU management fees by up to 60%
A 60% cut on the management fee for the privilege of running GPUs that already cost more than a starter home. The tax on the tax got cheaper, which matters right up until you see the actual P-series instance bill and remember why you’re crying. Then you, like I, wonder what the point of paying the “Managed Instances” tax in the first place is. They also applied this to ECS and a couple of other Managed Instances stuff I don’t care about because again, why would I use it?
Amazon RDS for Oracle now supports Oracle Database 26ai
Slapping “ai” in the version number is Oracle’s answer to renaming the same database it’s sold since disco. Enterprise Edition only, naturally, because Larry needs another yacht. Bedrock integration means you can now ask Claude to explain your Oracle licensing bill, then weep together in natural language.
AWS Builder Center Now Offers Free Sandbox Environments
A free AWS environment where you can’t rack up surprise charges? This is the one product AWS clearly built by accident. Eight hours a week, auto-cleanup, no credit card, no 3am billing panic. Truly the only way to use AWS without fearing your bill is when Amazon’s paying it.
AWS Security Hub now offers Network Scanning to identify publicly reachable resources
Turns out the most reliable way to find your exposed S3 buckets was AWS scanning them from the internet, same as every attacker already does. At least it’s free, which for AWS security features counts as a minor miracle. Now offering the same view your last breach report gave you.
Amazon Cognito now supports self-service provisioned API rate limits
Buried in paragraph four: “purchase additional limits” and “add-on feature.” So Cognito’s default rate limits are now a self-service upsell you can raise on demand, immediately, with no support ticket. Convenient! The friction they removed was the part where a human might’ve asked why you’re paying extra to log people in.
AWS Security Hub adds impact analysis for exposure findings – Turns out the scariest part of your infrastructure isn’t the exposed resource, it’s every over-permissioned IAM principal it can reach. Security Hub now draws you the attack path graph, which is a polite way of saying it’ll finally visualize how your intern’s leftover admin role becomes an incident. Sobering bedtime reading.
Blazing a Trail: How Peloton Rebuilt the SDLC for the Agentic Era with Amazon Bedrock
A stationary bike company just described its engineers as “sprinting on the problems that demand human judgment,” which is quite a metaphor for a firm whose actual bikes go nowhere. The creator brags he handwrote zero lines of code, and honestly, that tracks with the stock price too. Amusingly, the blog post was taken down prior to publication, but I’d already written the jokes; the link goes to an archived copy.
How United Airlines solved IP exhaustion with Private NAT Gateway
Nothing says “modern cloud” like an airline running out of IP addresses precisely when a snowstorm strands 40,000 people. United sidestepped a multi-week firewall-change bureaucracy by NATing their way out, because actually adopting IPv6 remains a decision roughly as achievable as an on-time departure. I now understand why airfare is so expensive, yet airline margins so thin: NAT Gateways.
Building secure AI agents at scale: Introducing Loom for AWS – A platform to weave together Strands, AgentCore, Bedrock, and a management UI, because the “building blocks” apparently required an entire second platform to become usable. They named it Loom, presumably so your bill can be woven into a tapestry nobody can read. “Opinionated” here means “you’ll pay for our opinions.”
What does it cost to answer one question? Measuring per-request cost in agentic workloads – Turns out that chatty AI agent looping through tool calls resends the entire conversation history every cycle, so three tool calls quietly balloons your token bill tenfold. AWS helpfully documents this after everyone’s already deployed. The per-request cost was there all along; you just couldn’t see it. Neither could your CFO.
Designing for the inevitable: System prompt leakage and mitigations in generative AI applications
An AWS security blog admitting a problem can’t be fully fixed, then selling you Bedrock Guardrails to mitigate it anyway. Refreshingly honest, if you squint. The real version: stop stuffing API keys into your system prompt like it’s a junk drawer, and it stays out of the leak.
The CISO’s guide to post-quantum mandates and migrations
Nothing motivates a multiyear budget line like a threat that doesn’t exist yet. Quantum computers can’t break your crypto today, but the compliance deadlines arrive in 2030 regardless, so start panicking on schedule. The advice here is solid: fix your patching discipline. You were going to ignore that anyway.
AWS is having a rough week around the concept of “secrets you’d prefer strangers not read,” starting with string-concatenated table names in 2026 living inside the very gateway that hands out API keys for your AI agents, because the MCP hype train stops for no one and certainly not for input sanitization, so upgrade to 1.0.13 and rotate whatever that thing was quietly exfiltrating. Then we arrive at a function named GetUserPrivateKey mishandling symlinks, which is the kind of poetry that makes security researchers weep with joy, since Research and Engineering Studio apparently did some research of its own and discovered that symlink attacks exist, generously documenting the finding as a CVE for the rest of us. Patch it before someone else fetches those keys on your behalf, and take comfort that in a year defined by AI agents everywhere, the industry remains reliably, dependably bad at the single job of not handing out the crown jewels.
… and that’s what happened Last Week in AWS.
