Good Morning!
I lived through my Seattle diving adventure; not a single one of the Amazonians I went with had the Bias for Action needed to chain me to a radiator underwater. This works to my benefit!
From the Community
Shadow Roles: AWS Defaults Can Lead to Service Takeover is worth keeping an eye on, methinks.
My colleague penned a post about RDS Reserved Instances: Where Did All the New Instance Types Go?
Apparently it’s still possible to create unencrypted Redshift clusters.
My lightning talk at SREcon has been published: For the AWS Bill is Dark, and Full of Terrors.
Podcasts
Last Week In AWS: The Art of Amazon Q Developer
Screaming in the Cloud: The Latest on Microsoft Security with Ann Johnson
Choice Cuts
Automated HTTP validated public certificates with Amazon CloudFront – FINALLY. Over a decade of customer requests later, you can now get TLS for a CloudFront distribution by checking a box.
AWS Systems Manager launches just-in-time node access – Neat feature, but I’ve never yet met a shop that was this stringent about removing access from their ops folks at different times of the rotation.
MAP enhancements to accelerate AI customer adoption – AWS keeps making changes to MAP, to the point where it now migrates more than any of the customer workloads it’s supposed to help.
Announcing SaaS Manager for Amazon CloudFront – AWS demonstrates yet again that they don’t actually know what SaaS means.
Announcing second-generation AWS Outposts racks – Time to throw away your old racks of AWS servers and buy a newer generation.
Amazon CloudWatch launches tiered pricing and additional destinations for AWS Lambda logs – They still soak you for 50¢ per GB at the small side, before dropping off to 10% of that at scale.
AWS Launch Wizard automates multi-node SAP NetWeaver deployment on SAP ASE Database – If you’re dealing with that much SAP, you’re gonna need a freaking wizard in your party.
AWS Lambda standardizes billing for INIT Phase – This is how AWS raises prices–not by jacking up hourly charges, but by subtly shifting pricing dimensions. This one is fair; the docs have always said this is how it worked, they just had an implementation bug they got around to closing.
… and that’s what happened Last Week in AWS.
