The AWS News Blog announced that the AWS Emulator is now generally available, letting developers point the AWS CLI or SDKs at a local HTTPS endpoint and perform operations such as creating a Amazon DynamoDB table, writing items, and reading them back without provisioning cloud resources. At the same time, AWS released Nitro Sandboxes, a hardware‑based isolation option for Amazon EKS pods, ECS tasks, and EC2 workloads, and added new capabilities to Amazon Cognito, Bedrock, and ElastiCache Serverless.
AWS Emulator: Local API Execution
The emulator runs as a Docker container on Linux, macOS, or Windows. It mirrors the shape of many AWS services, returning realistic responses for supported calls while returning HTTP 501 for unimplemented operations. No AWS account is required, and there is no service fee for emulated usage. The fidelity documentation notes that IAM and resource‑policy enforcement, cross‑account, and cross‑Region behavior are not reproduced, so a final validation on real AWS is still required.
Practically, this means developers can iterate faster, integrate API‑driven tests into CI pipelines, and give coding agents concrete feedback without incurring cloud costs. The emulator’s source is available on GitHub, allowing teams to inspect implementation details if needed.
Nitro Sandboxes: Hardware Isolation for Shared Compute
Nitro Sandboxes extend the Nitro hypervisor to provide per‑pod or per‑task VM boundaries on a shared EC2 instance. Two modes are offered:
- Isolated mode – separates workloads from neighboring containers, useful for multi‑tenant or untrusted code execution.
- Confidential mode – adds cryptographic attestation and protects data from the node operator.
There is no extra charge beyond the underlying EC2, EKS Auto Mode, or ECS Managed Instance fees. This option is relevant for build jobs, AI agents that generate code, or any scenario where a tenant’s workload must not interfere with others on the same host.
Related Service Updates
Amazon Cognito token exchange now supports OAuth 2.0 token exchange, allowing a downstream service to receive a token with a narrower scope and a single audience. The exchange can include an act claim to identify the intermediary, simplifying delegation without forwarding the original token.
Claude Fable 5.2 on Bedrock is available as a generally available model for technical workloads, including engineering and scientific tasks. Bedrock retains traffic for up to 30 days for abuse detection, with a temporary zero‑retention exception for eligible internal use.
Amazon ElastiCache Serverless now supports combined vector, full‑text, and hybrid search with server‑side aggregations, expanding its use cases beyond pure caching.
Related CloudNinjas coverage: AWS.
What This Means For Practitioners
• Incorporate the emulator into local development and CI to reduce cloud spend and accelerate feedback loops, but retain a final integration test on real AWS to verify IAM and cross‑Region behavior.
• Evaluate Nitro Sandboxes when running untrusted code or multi‑tenant workloads on shared EC2, especially if confidentiality guarantees are required.
• Use Cognito token exchange to limit token scope for service‑to‑service calls, reducing the risk of token leakage.
• Consider Claude Fable 5.2 for heavy‑weight AI tasks, but account for the 30‑day retention policy in data‑handling processes.
• Leverage the new ElastiCache Serverless search capabilities for applications that need low‑latency vector or full‑text queries without managing dedicated search clusters.
Next Steps and Watch‑Points
Monitor the emulator’s fidelity matrix for any newly supported services that are critical to your stack. Track the adoption of Nitro Sandboxes in upcoming EKS and ECS releases to see if additional integrations (e.g., with service mesh or observability tools) become available. Keep an eye on Cognito’s regional rollout status and any policy changes around token lifetimes. Finally, watch for Bedrock’s evolving retention policies and any pricing updates for Claude Fable 5.2 usage.




