Screaming in the Cloud - Lambda Slowly Becomes EC2, One Feature at a Time

Starting point is 00:00:00 Hello and welcome to last week in AWS. I'm Corey Quinn. Let's see what they have for us this week. Amazon API Gateway now supports one megabyte execution logs with configurable delivery destinations. At one megabyte log that gets spat out per event, that is not telemetry, my friends. That is a new database. Speaking of databases, S3 object lock now supports variable retention with event holds, which is great, just as long as I get to prank my coworkers still by requiring a century retention on the big scratch bucket. Lambda's slow motion reinvention of EC2 is clearly here. It's serverless, but it's starting to look and be priced an awful lot like a server.

Starting point is 00:00:42 They announced a 90-minute ceiling on managed instances for async and event source mapping's indications with synchronous calls still cut off at 15. You can also handpick C9G over M9G via capacity providers. Everyone who rebuilt around 15 minutes and step functions gets to feel just great about that. EC2 now supports specifying compatible instance types on AMIs. At last, AMI owners can declare supported and or unsupported instance types. Non-permitted launches get blocked at the API. This is a free guardrail that turns a confusing kernel panic into a confusing API error instead.

Starting point is 00:01:19 Announcing second-generation single rack outposts. Still X-86 only, it seems that Graviton still isn't allowed to leave the AWS buildings. The names are BMNSF2E, BMN CX2, and BMN CX3A, which is a pretty clear indicator. The naming committee has just stopped showing up for work at all these days. How AWS thinks about FinOps automation and trust. Another agent? Yes, but hear us out is what it says. This is refreshingly self-aware of AWS, given the frankly insane levels of agent fatigue

Starting point is 00:01:52 experienced by the entire industry these days. Introducing EBS volume clones across AWS accounts. When misconfigured, this is a terrific new opportunity for your data to get exfiltrated. So don't do that. How to migrate from cloud search to open search serverless. Note how it's not actually canceling cloud search, but the embedded video in the page prominently features a decades-old AWS logo. Yeah, I'm serious, pull it up in the marketing site.

Starting point is 00:02:19 It's right there staring at you. Introducing PizzaBot, an open-source inbox for AI. agents that work in the background. I don't actually hate this. I have a pending PR against it as of this recording. Let's see if they merge it in for me. And finally, three CVEs this week in AWS authored code. First off, the security agent plug-in that AWS docs nag you about in every S3 hardening guide winds up screwing it up twice here, once in the agent and once in the MCP server, because agentic tooling has become a CVE delivery pipeline with better branding. Deep Java library contributes an interflow, overflow, in tensor buffer,

Starting point is 00:02:58 proving that Java's memory safety story might not be totally comprehensive. Then there's the SSM agent, the thing that you installed specifically so you could retire your bastion hosts, which will now cheerfully forward a port somewhere you never asked it to. None of these come with anything like a console-side patch button? No, you find out via RSS, and the remediation is a version bump you schedule yourself on your weekend for code you didn't write because customer obsession.

Starting point is 00:03:23 And that's what happened last week in AWS. I'm Corey Quinn. Stay salty.

Screaming in the Cloud - Lambda Slowly Becomes EC2, One Feature at a Time

There aren't comments yet for this episode. Click on any sentence in the transcript to leave a comment.