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

by Ramesh Ramani

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.