AWS Recent Announcements Note

AWS Recent Announcements

AWS (Amazon Web Services) provides various services under its umbrella including compute, storage, security, and application services. Here are some recent announcements and updates: 1. AWS Outposts: AWS Outposts is a fully managed service that offers infrastructure consisting of compute, storage, and database capabilities. The latest update includes launch of Outposts in various countries. 2. AWS Lambda: Provides a compute service on-demand resource. Recent updates include enhancements for concurrency control and integration with Amazon API Gateway. 3. Amazon S3: Offers durable storage. Recent updates include the launch of the application migration API and encryption for snapshots. 4. AWS Billing: Allows you to view detailed billing information, and recent updates include improvements in billing details. 5. AWS Config: Provides resource monitoring, reporting, and auto-remediation for AWS resources. Recent updates include a notification action and AWS Step Functions. 6. AWS Multi-Region Access Point for Amazon S3: Multi-Region Access Points for S3 provide a global namespace to deliver a fast, secure, and resilient storage service. 7. Amazon Route 53: Provides domain registration and DNS service. Recent updates include support for multi-Region Access Points for S3. 8. AWS Lake Formation: A data engineering, data transformation and data governance service. Recent updates include creation of workflows and database credentials connection using JDBC drivers. 9. Amazon EMR: A big data processing service used for data processing, analytics, machine learning (ML) etc. Recent updates include cluster versioning and bug fixes. 10. AWS Step Functions: A service for coordinating the components of distributed applications and microservice-oriented architectures. Recent updates include enhanced task token input handling and auto-replace.

Thread Of Notes

AWS Secrets Manager now supports managed external secrets for Auth0, Okta, and Palo Alto Networks. Long-lived credentials that are not rotated increase the risk of unauthorized access if exposed. Rotating a third-party credential requires coordinated updates to the external service and every application that uses it. You set a rotation schedule from the AWS Management Console or API. Secrets Manager rotates the credential and stores the current value without a custom rotation Lambda function. Secrets Manager offers self-rotation and administrator-assisted rotation for Auth0 credentials. With self-rotation, the target application replaces its own secret. With administrator-assisted rotation, a separate Auth0 application with Management API permissions replaces the target application's secret. For Okta, Secrets Manager offers administrator-assisted rotation with a separate administrator JSON Web Token (JWT) key and validates the replacement before deactivating the old secret. For Palo Alto Networks, Secrets Manager offers self-rotation, in which the current API key authorizes its replacement. Applications that already retrieve credentials from Secrets Manager receive the rotated value without a code change or deployment. These integrations join existing managed external secrets support for BigID, Cisco Security Platform, Confluent Cloud, Databricks, Datadog, GitLab, Jenkins, MongoDB Atlas, Netskope, Paddle, Salesforce, Snowflake, SonarQube, and Twilio. Auth0, Okta, and Palo Alto Networks managed external secrets are available in all AWS Regions where AWS Secrets Manager managed external secrets is supported. To learn more, visit the  AWS Secrets Manager managed external secrets documentation .
Amazon Virtual Private Cloud (VPC) now supports Networking Flexible Cost Allocation (FCA), which splits shared networking costs by the resources that actually drive them, so you can see what each team or application used. Until now, AWS Cost and Usage Report (CUR), including CUR 2.0 in AWS Data Exports, showed networking usage as a single item, and most customers split it across teams with custom scripts and manual estimates. FCA splits this line item by the resources that generated it. It supports NAT gateway data processing and data transfer, including traffic to the internet, and in-Region Amazon Elastic Compute Cloud (Amazon EC2) and VPC peering data transfer.Today, when several teams share a resource such as a NAT gateway, the account that owns it pays the full cost and can't see which team or application drove it. To work around this, some customers built custom scripts to analyze VPC Flow Logs, which takes ongoing engineering effort. Others used fixed-percentage splits, which overcharge some teams and undercharge others. FCA breaks down usage based on traffic sources, helping you accurately track financial metrics based on applications and teams. To get started, attach a cost allocation policy to a NAT gateway, VPC peering connection, or Amazon EC2 instance, then select Networking flexible cost allocation under split cost allocation data in the AWS Billing and Cost Management console. Allocated line items appear in your CUR within 24 hours. FCA changes only how costs are shown in your reports. Your bill and total charges stay the same.FCA is available at no additional charge. It's supported in all AWS commercial Regions except Middle East (Bahrain) and Middle East (UAE). It's also available in the China Regions. It is not available in the AWS GovCloud (US) Regions. To learn more, visit the Networking FCA product page.
AWS IAM Identity Center now supports interface VPC endpoints powered by AWS PrivateLink and network access controls, enabling you to keep IAM Identity Center traffic private and restrict which networks can reach your IAM Identity Center services. Previously, IAM Identity Center rejected traffic arriving through VPC endpoints, requiring all sign-in and API traffic to use public endpoints. With this launch, you can create interface VPC endpoints for AWS access portal and service APIs to route traffic over the AWS private network. IAM Identity Center sign-in traffic flows through the AWS Sign-in VPC endpoint. You can attach VPC endpoint policies to each endpoint to scope which AWS organizations, accounts and resources are reachable through your private connection. Network access controls add a second layer of enforcement at the IAM Identity Center instance level. When enabled, you can require that all access arrive through a VPC endpoint, allow specific IP address ranges or VPCs as trusted sources, and exclude individual applications from enforcement to accommodate services that connect from outside your VPC. SCIM provisioning traffic from your external identity provider can be independently restricted to known IP address ranges. Network access controls are configured through the IAM Identity Center API and are disabled by default. This capability is available in all commercial AWS Regions and the AWS GovCloud (US) Regions at no additional cost. To learn more, see Interface VPC endpoints in the IAM Identity Center User Guide. For more information, visit the IAM Identity Center product page.
AWS IAM Identity Center now gives you the option to require workforce users to re-authenticate with your external identity provider (IdP) each time their user interactive session expires. By default, when a user's session expires, IAM Identity Center renews it through the user's existing IdP session, and the user isn't prompted to sign in again. For organizations with strict security or compliance requirements that mandate explicit user verification at regular intervals, this automatic renewal may not meet policy requirements. When you set user re-authentication to Required and a user's user interactive session expires, IAM Identity Center prompts the user to re-authenticate with your external IdP. This helps you enforce stronger sign-in controls for regulated workloads. IAM Identity Center implements this by adding the SAML 2.0 ForceAuthn attribute to the SAML request sent to your IdP. You can configure user re-authentication for any IAM Identity Center instance (organization or account) that's connected to an external IdP as its identity source. The setting applies only to service provider initiated sign-ins, where users sign in through your AWS access portal URL. Changes to the user re-authentication setting are logged in AWS CloudTrail, so you can audit when it was turned on or off. User re-authentication is available in all AWS Regions where IAM Identity Center is available at no additional cost. To learn more, see Require user re-authentication in the AWS IAM Identity Center User Guide.
AWS WAF advanced rate-based rules are now available in the Asia Pacific (Thailand), Mexico (Central), AWS GovCloud (US-East), and AWS GovCloud (US-West) Regions. Customers in these Regions can now aggregate requests using custom keys and choose a 1 or 2 minute evaluation window in addition to the existing 5 and 10 minute options, the same capabilities already available in other AWS Regions.A rate-based rule counts requests and applies an action, such as Block or CAPTCHA, when the request rate exceeds a limit you set. Previously, rate-based rules in these Regions could aggregate requests only by IP address and used a 5 or 10 minute evaluation window. Now you can aggregate by request components such as HTTP headers, cookies, query strings, URI paths, HTTP methods, and label namespaces, and combine up to five of them into a composite key. For example, you can limit login attempts per IP address and User-Agent pair, or per session cookie, which helps against attacks spread across many IP addresses. A shorter evaluation window detects request floods sooner, and a longer window catches slower, sustained attacks.You can configure these options in the AWS WAF console, the AWS CLI and SDKs, and AWS CloudFormation. There is no additional charge for these capabilities, and standard AWS WAF pricing applies. Advanced rate-based rules are now available in all commercial AWS Regions where AWS WAF is available and in the AWS GovCloud (US) Regions. To learn more, see Using rate-based rule statements in the AWS WAF Developer Guide.
Amazon SageMaker AI now supports KV cache-aware routing for real-time inference endpoints, enabling you to reduce time to first token for LLM workloads with long or repeated prompts. Serving engines such as vLLM store the computed key-value (KV) cache for repeated prompt starts such as shared system prompts, documents, and conversation history, to skip repeated work. Across several instances, a request that lands where the cache is missing recomputes it. Under high load, instances also evict cached blocks to free GPU memory, including shared prompts and earlier conversation turns.KV cache-aware routing sends each request to the instance that holds the longest matching part of its prompt in cache. The vLLM container reports the cache blocks it stores and evicts, and SageMaker routes with that live view. If the lookup is slow or finds no match, the endpoint falls back to load-aware routing, so the request is still served. Prefix-aware routing suits stable shared prompts, short prompts, or moderate load. KV cache-aware routing suits long prompts, high load, and limited GPU memory.Customers can now enable this feature by setting RoutingStrategy to KV_AWARE on a production variant and adding one environment variable so the container reports cache events. Customer can invoke the endpoint with the same APIs and OpenAI-compatible payloads. It supports single-model endpoints and inference components, including LoRA adapters, on GPU instances. It requires the AWS vLLM Deep Learning Container version 0.33.0 or later with at least two instances or inference component copies. Detailed observability metrics show KV cache hit rate. There is no additional charge for KV cache-aware routing.KV cache-aware routing is available today in all AWS Regions where Amazon SageMaker AI is available. To get started, update to the latest AWS SDK or CLI. To learn more, visit the Amazon SageMaker AI inference page and see the API documentation.
AWS Backup logically air-gapped vault now supports Amazon Relational Database Service (Amazon RDS) DB instances. Logically air-gapped vaults are a type of AWS Backup vault that stores immutable, isolated backups, which are locked by default with AWS Backup Vault Lock in compliance mode. Secure sharing across accounts and AWS Organizations enables direct restore, reducing recovery time from a data loss event. You can now protect your Amazon RDS DB instances in logically air-gapped vaults. A logically air-gapped vault stores immutable backups that are locked by default, and isolated with encryption using AWS owned keys or customer-managed keys. This helps reduce the risk of downtime, ensure business continuity, and meet compliance requirements. To get started, use the AWS Backup console, AWS Command Line Interface (CLI), or AWS SDKs. Assign your RDS DB instances to a backup plan and specify a logically air-gapped vault in the same AWS Region as the copy destination. Share the vault for recovery or restore testing with other accounts using AWS Resource Access Manager (RAM), or safeguard vault access during account compromise using Multi-party approval. Once shared, you can initiate direct restore jobs from that account. This support is available in most AWS Regions where both logically air-gapped vault and Amazon RDS are available. For more information and detailed regional availability, visit the AWS Backup documentation. To learn more about logically air-gapped vaults for RDS, read the launch blog and visit the feature documentation and pricing page.
Amazon SageMaker Unified Studio now supports layout customization, a new capability that gives domain administrators control over which tools and left navigation items project members see based on their designation. Organizations with data engineering, analytics, and machine learning teams on a single platform can configure a layout within each designation definition, and that layout applies across every project in the domain without per-project configuration. Previously, all project members saw the same interface regardless of their role, creating confusion and potential governance issues. With layout customization, administrators define a layout as part of a designation that specifies which left navigation items are visible for project members assigned to that designation. When a project member opens a project, SageMaker Unified Studio resolves the member's designation and renders only the tools included in their designation's layout. For example, a SQL analyst designation can be configured to show only the Query Editor, while an ML engineer designation shows notebooks, training jobs, and model endpoints. Navigation items are configurable across categories including Data Analytics, artificial intelligence and machine learning (AI/ML), Generative AI, and IDEs. If a project member navigates directly to a hidden page, they see an access-denied page. For members with multiple designations, visible tools are the union of all their designations' layouts. New navigation items added to SageMaker Unified Studio remain hidden for designations with a configured layout until an administrator adds them. This feature is available in all AWS Regions where Amazon SageMaker Unified Studio is available. To learn more, visit the Designations documentation.
AWS Security Hub CSPM now supports AWS Organizations declarative policies. You can use them to enable Security Hub CSPM across all accounts and Regions in your organization and to define which security standards and controls are enabled.Policies can apply broadly to every account and Region, or target specific account and Region combinations. Declarative policies help keep each account's configuration aligned with its attached policy, which helps prevent configuration drift. You can also apply them automatically to new accounts, so each account starts with a baseline configuration as soon as it's created.Declarative policies are now the recommended way to manage Security Hub CSPM across an organization. They align with how other security services, such as Amazon GuardDuty, Amazon Inspector, and AWS Security Hub allow customers to manage configuration of the service. They also provide more flexibility, such as configuring Region-specific settings. You can continue to use central configuration until you're ready to migrate. When you are, use the migration process in the Security Hub CSPM console. It converts your existing central configuration policies into declarative policies and applies them to the appropriate accounts and regions.Declarative policies for Security Hub CSPM are available in all commercial, AWS GovCloud (US), and China Regions. To get started, see Migrating central configuration policies. To learn more, see Declarative policies in the AWS Security Hub CSPM User Guide and Security Hub CSPM policies in the AWS Organizations User Guide. To receive notifications about new Security Hub CSPM features and controls, subscribe to the Security Hub SNS topic. You can also try Security Hub CSPM at no cost for 30 days with the AWS Free Tier offering.
AWS Systems Manager Cloud Connector now extends simplified multicloud onboarding support to Google Cloud, making it easy to connect your existing Google Cloud VMs to Systems Manager for centralized management alongside AWS, on-premises, and Azure resources without manual agent installation. Previously, managing virtual machines across multiple cloud providers often required coordinating and setting up configurations separately in each environment. With Cloud Connector for Google Cloud, you can automatically deploy the SSM Agent to Google Cloud VMs at scale. Once connected, Google Cloud VMs appear alongside EC2 instances, on-premises servers, and other multicloud resources in a unified view, enabling you to use Session Manager, Automation runbooks, Run Command, State Manager, Patch Manager, and Inventory across AWS, on-premises, Azure, and Google Cloud from a single workflow. This simplifies operations for teams managing infrastructure across multiple clouds, enabling them to standardize management practices and reduce operational complexity. Cloud Connector for Google Cloud is available in Africa (Cape Town), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, New Zealand, Osaka, Seoul, Singapore, Sydney, Taipei, Thailand, Tokyo), Canada (Central, Calgary), Europe (Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm, Zurich), Israel (Tel Aviv), Mexico (Central), South America (Sao Paulo), US East (N. Virginia, Ohio), and US West (N. California, Oregon). To learn more, visit the AWS Systems Manager documentation.
Amazon Relational Database Service (Amazon RDS) for Oracle now reduces downtime for automatic minor version upgrades, as well as minor version upgrades and operating system updates scheduled for your maintenance window. Shorter maintenance makes it easier to stay current on the latest Oracle minor versions and operating system updates with less disruption to your applications. If you turned on automatic minor version upgrade, your DB instances benefit automatically. To apply these upgrades and updates, RDS has to set up new resources as part of the maintenance. Previously, RDS set up these resources after the maintenance started, which made your downtime longer. Now, RDS prepares them up to 30 minutes before your maintenance window, while your DB instance keeps serving your workload. When the maintenance window opens, your DB instance is offline for less time because resources required for the maintenance are already prepared. This applies to both Enterprise Edition and Standard Edition 2 DB instances. The preparation never blocks or delays your own operations, and your DB instance stays available while RDS prepares. If a change that you make conflicts with the preparation, RDS rolls back the staged resources, and your change goes ahead. If the preparation can't finish, RDS still applies the maintenance in your window, without the preparation. New RDS events tell you when the preparation starts, when it finishes, and when it can't finish. RDS for Oracle will continue to introduce improvements that further reduce maintenance downtime. This capability is available at no additional cost in all commercial AWS Regions and the AWS GovCloud (US) Regions where Amazon RDS for Oracle is available. To learn more, see Maintenance preparation, Amazon RDS event categories and event messages, and Maintaining a DB instance in the Amazon RDS User Guide.
Amazon Route 53 now supports record set protection, which helps DNS administrators prevent accidental changes to critical DNS records in their hosted zones. This feature allows you to protect records such as those at the zone apex, MX records, and production endpoints directly in the hosted zone. Any change to a protected record is blocked until the protection is removed by an authorized user.Previously, to lock specific records, you had to write record-level conditions into the IAM policies of every user and role that could change your hosted zones. When those policies blocked a change, the caller had no indication of whether the record was protected or why. Now you can protect records by name and type directly in the hosted zone. A single protection covers all records with that name and type, including records with different set identifiers; weighted, latency, and other routing policy records are protected together. You can also create a protection proactively before the record exists, preventing records from being created for that name and type. Each protection can include an optional comment of up to 256 characters, allowing you to indicate the reason for the protection. You can manage protections using the Route 53 console, AWS CLI, or AWS SDKs through the CreateResourceRecordSetProtections, DeleteResourceRecordSetProtections, and ListResourceRecordSetProtections API actions. To control who can remove protections, restrict the DeleteResourceRecordSetProtections permission in IAM policies.Record set protection is available in all AWS commercial Regions where public and private hosted zones are available today. To learn more, see Protecting records from changes in the Amazon Route 53 Developer Guide.
Amazon Relational Database Service (Amazon RDS) for SQL Server now supports M8id and R8id instances. These instances are powered by custom Intel Xeon 6 processors, available only on AWS, and include local NVMe SSD storage. They scale up to 384 vCPUs, 3 TiB of memory, and 22.8 TB of local NVMe SSD storage. That's 4x the vCPUs and memory and more than 6x the local storage of M5d and R5d instances. When you create or modify a DB instance to use M8id or R8id, RDS for SQL Server automatically places the tempdb data and log files on the local NVMe instance store. This gives tempdb lower read and write latency than Amazon EBS storage. Your database data and log files stay on Amazon EBS. Because snapshots don't include tempdb files on the instance store, your snapshots are smaller and use less of your free backup storage. To learn more, see Instance store support for the tempdb database on Amazon RDS for SQL Server. To use the new M8id and R8id instances, you can modify your existing RDS database instance or create a new RDS database instance from the RDS Management Console, or using the AWS SDK or CLI. M8id and R8id instances are available in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), Europe (Ireland), Europe (London), Europe (Frankfurt), Europe (Stockholm), Europe (Spain), Asia Pacific (Tokyo), Asia Pacific (Mumbai), Asia Pacific (Sydney), and Asia Pacific (Malaysia). For pricing details, see Amazon RDS for SQL Server Pricing.
AWS Glue introduces automatic version upgrades, a capability that keeps your Apache Spark jobs current on the latest AWS Glue runtime without manual coordination. Staying current on supported runtimes gives your jobs the latest security patches, performance improvements, and support for evolving table formats such as Apache Iceberg. Auto upgrades include multiple levels of validations including assessing jobs for compatibility with the upgraded runtime, obtaining your consent before executing jobs on a newer version, and validating upgraded job runs against each job's established output profile, so your jobs upgrade with the right guardrails in place.By setting a job's version to "Auto", upgrades that once required weeks of planning and execution now happen automatically. Platform teams can standardize runtime versions across large fleets without chasing individual job owners, and business units without a central upgrade team can keep their jobs current hands-free. Each job is validated against its established output schema, data volume, latency, and format before it upgrades, so you can advance with confidence. Jobs that need code changes keep running safely on their current version, and AWS Glue provides an upgrade analysis with specific fixes you can apply directly or with the Apache Spark upgrade agent.Auto upgrades for AWS Glue are available in all AWS Commercial Regions.To get started, select "Auto" as the AWS Glue version when creating or updating an Apache Spark job using the AWS Glue Studio or AWS CLI, API, and SDKs. Alternatively, you can update multiple jobs at once using the AWS Glue skill to manage your jobs. To learn more, visit the AWS Glue documentation.
Starting today, new runtimes in Amazon Bedrock AgentCore use the next generation of AgentCore runtime by default. The new runtime restores each session from a snapshot of your initialized agent, scales compute and memory with the work, and scales idle agents to zero. Every session still runs in its own hardware-isolated Firecracker microVM. Your agents can run heavy work like compiling a large codebase, driving a browser, or loading a local model inside the session.  Sessions scale to 8 vCPU and 32 GB of memory and support container images up to 10 GB. On a 2 GB image, sessions start in under 2 seconds at P75, down from 29.7 seconds on the previous generation. Idle agents scale to zero, and memory is reclaimed within minutes of release. For multi-turn agents, that means up to 68% less billed memory per session. Existing runtimes stay on the current version until you move them. To move an existing runtime, or to use the next generation in a Region where it isn't the default yet, set platformVersion to V2 when you create or update a runtime. To keep a new runtime on the current version, set platformVersion to V1. The new AgentCore Runtime is now the default runtime in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), South America (São Paulo), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Milan), Europe (Paris), Europe (Spain), Europe (Stockholm), Asia Pacific (Malaysia), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Thailand), and Asia Pacific (Tokyo).  To learn more, visit the AgentCore runtime documentation or the AWS Blog. For pricing details, visit AgentCore pricing.
Amazon OpenSearch Serverless now features intelligent ingestion for time series collections. This allows users to import logs and event data from Amazon S3 without needing an ingestion pipeline. Setup is streamlined, requiring just a few clicks in the AWS Management Console or a single API call.Intelligent ingestion automatically detects data types, parses records, and indexes them into the collection. It supports observability logs in JSON, NDJSON, and JSON array formats. Users can choose between one-time ingestion jobs or continuous ingestion streams to keep collections updated.Source S3 buckets can reside in the same or different AWS accounts as the collection. Capacity scales automatically with the workload, and users only pay for active processing. Once ingested, data benefits from existing time series collection features.The collection automatically handles ingestion spikes and stores recent data in a hot tier for quick querying. Older data transitions to a lower-cost warm tier based on user-defined retention policies. Each document must contain a valid timestamp field for successful ingestion.Missing or invalid timestamps will result in document rejection. Alerting and anomaly detection can be performed directly on the ingested logs and events. This simplifies leveraging large S3 log archives for analytics, monitoring, and IoT telemetry.Intelligent ingestion is currently available in seven AWS regions, including US East (N. Virginia), US East (Ohio), and Europe (Ireland). To begin, navigate to the Ingestion tab within your time series collection in the Amazon OpenSearch Service console. Further details are available in the intelligent ingestion and OpenSearch Serverless documentation. Pricing information can be found on the Amazon OpenSearch Service pricing page.
AWS Cloud WAN now supports VPC Flow Logs, giving you central visibility into IP traffic across your global network. Flow Logs capture detailed information for each flow, so you can understand how traffic moves across your core network without leaving your AWS Cloud WAN account. Until now, network administrators had to stitch together VPC Flow Logs from many VPCs, accounts, and Regions to see traffic across their global network. They often depended on other teams for access to those logs. Cloud WAN Flow Logs give core network owners one consolidated view of traffic between VPCs, Regions, and on-premises networks connected over AWS Direct Connect, AWS Site-to-Site VPN, or SD-WAN. You can use this data to troubleshoot connectivity and performance problems, plan capacity from historical bandwidth trends, find unusual traffic patterns, and keep records for security and compliance. Flow log records include IP addresses, ports, protocol, traffic volume, and packet-loss counters, along with Cloud WAN metadata such as segment, Region, service insertion hops and attachment details. You can turn on Flow Logs for an entire core network, a single core network edge, or individual attachments. You can publish them to Amazon CloudWatch Logs, Amazon Simple Storage Service (Amazon S3), or Amazon Data Firehose. Cloud WAN adds no charge for Flow Logs. Standard charges apply for each destination. Cloud WAN Flow Logs are available in all AWS Regions where AWS Cloud WAN is available. You can get started with the AWS Management Console, AWS CLI, or API. To learn more, see AWS Cloud WAN Flow Logs user guide.
AWS Lambda MicroVMs now supports the x86 CPU architecture, so you can run your existing x86 applications, tools, and software dependencies without recompiling or porting them. When you create a MicroVM image, you can now choose between x86 and Arm (AWS Graviton) to give each user or job an isolated MicroVM on the architecture your workload uses. Lambda MicroVMs is a serverless compute primitive that provides VM-level isolation, near-instant launch and resume, and state preservation for running user or AI-generated code, in applications such as AI coding assistants, CI/CD runners, interactive development environments, and vulnerability scanners. Today’s launch enables you to run x86-based workloads on Lambda MicroVMs as-is. For workloads that run on Arm, you can continue using AWS Graviton processors which is the default CPU architecture option. To start building x86 workloads on Lambda MicroVMs, choose the x86 architecture when you create a MicroVM image from your Dockerfile, then launch MicroVMs from that image. You can use MicroVMs through the AWS Lambda console, AWS CloudFormation, AWS Cloud Development Kit, or with your preferred agentic development tools using the Agent Toolkit for AWS. Support for the x86 CPU architecture is available in all AWS Regions where Lambda MicroVMs is available, except Asia Pacific (Hong Kong), Asia Pacific (Malaysia), Asia Pacific (Thailand), and Europe (Spain). To learn more, visit the AWS Lambda MicroVMs developer guide. For information on pricing, see Lambda MicroVMs pricing.