IT Brief Canada - Technology news for CIOs & IT decision-makers
Canada
AWS launches Emulator for local testing of API calls

AWS launches Emulator for local testing of API calls

Sun, 22nd Nov 2026 (Today)
Mara Sugue
MARA SUGUE News Editor

AWS has launched AWS Emulator as a generally available local environment for AWS API interactions, aimed at developers who want to test application calls to AWS services on their own machines.

The tool lets developers and coding agents direct the AWS CLI and AWS SDKs to a local HTTPS endpoint while keeping standard SDK calls in place. Emulated operations do not require an AWS account and carry no additional service fee.

AWS Emulator is designed to run alongside code and development tools, letting users create resources, inspect results and retry changes without provisioning cloud resources for each attempt. AWS highlighted a walkthrough in which a coding agent creates an Amazon DynamoDB table, writes an item and reads it back.

Setup options include Linux packages and Docker support for macOS and Windows. AWS has also published the source code on GitHub.

The release adds a local testing option at a time when software teams are trying to shorten development cycles and make greater use of coding agents. It also reflects growing demand for tools that provide rapid feedback during development without repeated deployment into live cloud environments.

Coverage, however, is not uniform across all operations. AWS said support varies, users should check published fidelity results, and unimplemented calls return HTTP 501.

The emulator also does not reproduce IAM and resource-policy enforcement, or cross-account and cross-Region behaviour. That means teams still need to test complete applications and security configurations on AWS before moving systems into production.

Broader updates

The launch was part of a wider set of product updates AWS released across its cloud and developer portfolio.

Among them, AWS introduced Nitro Sandboxes for Amazon EKS pods, Amazon ECS tasks and EC2 workloads. The service gives an EKS pod or ECS task its own virtual machine boundary while sharing an EC2 instance, a design intended for tenant workloads, build jobs and agents executing generated code.

Nitro Sandboxes are available in isolated mode, which separates workloads from neighbouring workloads, and in confidential mode, which adds protection from node operators and cryptographic attestation. There is no additional charge on supported instances, although normal EC2 and applicable EKS Auto Mode or ECS Managed Instances fees still apply.

In identity management, Amazon Cognito now supports OAuth 2.0 token exchange. AWS said this allows a user token to be exchanged for one scoped to a downstream service, with narrower permissions and a single audience.

This could help when an agent calls a backend service on a user's behalf, because it avoids forwarding the original token and makes delegated access more explicit. The feature is available on Cognito Essentials and Plus plans in all Cognito Regions.

AWS also added managed cross-Region disaster recovery to Amazon OpenSearch Service for domains running version 3.7 or later in two Regions within one account. AWS said it specifies recovery objectives of under one minute for data loss and under 20 minutes for recovery time.

Planned switchovers preserve all writes, while unplanned failovers can lose data that has not yet been replicated. Customers still need to keep configurations aligned and redirect application writes after switching roles, and secondary-domain and data-transfer charges still apply.

Search and logs

Amazon ElastiCache Serverless has gained search and aggregation functions for Valkey, allowing vector, full-text and hybrid search with server-side aggregations. AWS said the update requires Valkey 9 and is available in commercial Regions, AWS GovCloud (US) and the AWS European Sovereign Cloud.

Amazon CloudWatch Logs has also added account-level retention policies. Organisations can now set retention rules across all log groups or for groups matching a name prefix, with the longest retention period applying when policies overlap.

The change is likely to matter to platform and security teams seeking broader control over log retention without updating each group separately. It carries no additional charge and is available in commercial Regions except Middle East (Bahrain) and Middle East (UAE).

Elsewhere, the next-generation AgentCore runtime is now the default for new Amazon Bedrock AgentCore runtimes. AWS said agent sessions start in under two seconds, can scale to 8 vCPU and 32 GB, and scale to zero when idle, while each session continues to run in its own isolated microVM.

Across the latest releases, AWS appears to be putting more weight on local development workflows, workload isolation, delegated access controls and resilience for distributed applications, while leaving some production validation and operational work in customers' hands.

AWS said unimplemented AWS Emulator calls return HTTP 501 and that complete application and security testing must still take place on AWS before production.