AWS Emulator lets developers test AWS APIs on local machines
AWS has introduced a local emulator for AWS API calls, alongside new Nitro Sandboxes for workload isolation and a set of service updates. The emulator is aimed at faster development loops but does not replace full cloud testing.

Key takeaways
- AWS Emulator lets developers run AWS API calls locally without an AWS account or an extra emulator charge.
- It does not reproduce IAM, resource-policy, cross-account or cross-Region behaviour, so full testing on AWS is still required.
- AWS Nitro Sandboxes give EKS pods and ECS tasks their own VM boundary on shared EC2 instances.
- Other updates include Cognito token exchange, Claude Fable 5.2 on Bedrock, ElastiCache search and OpenSearch disaster recovery.
In this article
How AWS Emulator works

AWS has released AWS Emulator, a tool that lets developers and coding agents exercise AWS API calls on their own machines, according to the AWS News Blog's weekly roundup published on 16 November 2026. The service is intended to shorten feedback loops during development by providing a local HTTPS endpoint for the AWS CLI and SDKs. The same roundup also covers AWS Nitro Sandboxes and changes across Amazon Cognito, Amazon Bedrock, Amazon ElastiCache, Amazon OpenSearch Service and Amazon CloudWatch.
Developers can configure the AWS CLI or AWS SDKs to send requests to the emulator's local HTTPS address, so application code keeps its usual SDK calls. A walkthrough in the post shows a coding agent creating an Amazon DynamoDB table, adding an item and reading it back. Emulated operations do not require an AWS account, and AWS says there is no extra charge for the emulator itself.
Installation options include Linux packages and Docker images for macOS and Windows, with support for agent-assisted setup. The source code is available on GitHub. AWS says coverage varies by operation, and calls that are not implemented return HTTP 501.
Important limits apply. The emulator does not reproduce IAM or resource-policy enforcement, nor cross-account and cross-Region behaviour. AWS recommends running the full application and its security settings on its cloud before production.
Nitro Sandboxes add VM-level isolation
AWS Nitro Sandboxes give an Amazon EKS pod or Amazon ECS task a separate virtual machine boundary, even when the underlying Amazon EC2 instance is shared. The feature is aimed at tenant workloads, build jobs and agents that run generated code. AWS describes two modes: in isolated mode, one workload is kept apart from the others, while confidential mode also shields workloads from node operators and provides cryptographic attestation.
AWS says supported instances carry no extra Nitro Sandboxes fee. Normal EC2 charges remain, as do any relevant EKS Auto Mode or ECS Managed Instances costs.
Service updates across the portfolio
Amazon Cognito now supports OAuth 2.0 token exchange. It allows a user token to be replaced by a token for a downstream service, with fewer permissions and one audience. The new token has no refresh token, and an actor token can name the intermediary through an act claim. Essentials and Plus customers can use it in every Cognito Region.
Claude Fable 5.2 is available through Amazon Bedrock or Claude Platform on AWS. Anthropic calls it the most capable model it has released for general use in technical fields such as long engineering projects, scientific research and quantitative finance. On Bedrock, Fable 5.2 traffic can be kept for as long as 30 days to detect abuse. Eligible internal use can receive a temporary exception with no retention.
Amazon ElastiCache Serverless now offers search that combines vector, full-text and hybrid methods, plus aggregations processed on the server, for Valkey. The feature needs Valkey 9. AWS lists commercial Regions, AWS GovCloud (US) and the AWS European Sovereign Cloud as supported.
Amazon OpenSearch Service has added managed cross-Region disaster recovery. Customers can link domains on version 3.7 or newer in two Regions within a single account. AWS sets a target of less than one minute of data loss and less than 20 minutes to recover. A planned switch keeps every write. An unplanned failover may drop data that had not been copied. Teams must still keep settings in step, send writes to the new primary after a role change, and budget for secondary-domain and data-transfer costs.
Amazon CloudWatch Logs now supports account-level retention policies. A policy can target every log group or those with a chosen name prefix. It can also apply to current groups or only to groups created later. When policies overlap, the longest retention period wins. AWS charges nothing extra. Commercial Regions are supported except Middle East (Bahrain) and Middle East (UAE).
Amazon Bedrock AgentCore's next-generation runtime is now the default for new runtimes. AWS says a session begins in less than two seconds, can grow to 8 vCPU and 32 GB, drops to zero when idle and costs as much as 68% less for memory. Every session remains inside a separate microVM.
Why the changes matter
The emulator and Nitro Sandboxes address two different parts of the development cycle. The emulator reduces the need to provision cloud resources for every test, while Nitro Sandboxes provide stronger separation for workloads that share hardware. Both are relevant to teams building agent-based tools, where generated code and repeated API calls can be hard to test safely.
The service updates also show where AWS is focusing: delegated access in Cognito, model access and retention rules in Bedrock, search in ElastiCache, resilience in OpenSearch and simpler retention management in CloudWatch. Teams should check regional availability and pricing details before relying on any of them in production.
AWS re:Invent is scheduled for Las Vegas from 30 November to 4 December. The event lists over 2,200 sessions and offers a free livestream. The roundup also points to Zillow's account of sending 100 million notifications a day with AWS Step Functions Express Workflows, and to guidance on measuring agent costs on Amazon Bedrock. The cost figures in that guidance are illustrative, so teams should use their own workload data and reconcile estimates with billing records.
Sources
Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.



