11/11/2026, 12:00:00 AM ~ 11/12/2026, 12:00:00 AM (UTC)

Recent Announcements

AWS Lambda MicroVMs now supports the x86 CPU architecture

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.\n 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.

Amazon EKS Auto Mode now supports security groups for Pods

Amazon EKS Auto Mode now supports security groups for Pods, letting you apply dedicated Amazon EC2 security group rules to individual Pods. Different workloads on the same node can carry different security groups, giving your Pods network-level segmentation without creating separate node pools for each application.\n Security groups for Pods extends your existing AWS network controls to the Pod level, so your Pods can reach resources such as Amazon RDS and Amazon ElastiCache databases that authorize connections by security group under the same rules the rest of your VPC uses. You define which Pods receive which security groups with a SecurityGroupPolicy resource, and Pods not matched by a policy keep using their node’s security groups.

Security groups for Pods is included as part of EKS Auto Mode at no additional charge and is available on clusters running Kubernetes version 1.36 or later, in all AWS Regions where EKS Auto Mode is supported. To learn more, see Security groups for Pods in the Amazon EKS User Guide and the Amazon EKS Auto Mode product page.

AWS Quick apps are now available in Asia Pacific (Singapore)

The AWS Quick desktop app for macOS and Windows and the Quick mobile app for iOS and Android are now available in the Asia Pacific (Singapore) Region. This launch builds on the recent availability of Quick in Singapore.\n The desktop app works with your local files and connects to your calendar, email, and business apps. The mobile app lets you chat with Quick, review your activity feed, and open dashboards. Your conversations, context, and agents stay in sync across web, desktop, and mobile, so you can start an agent on your desktop, check on it from your phone, and let it keep running after you close your computer. 

To get started, download the desktop app from the AWS Quick download page or the mobile app from the Apple App Store or Google Play. To learn more, see AWS Quick on mobile in the AWS Quick User Guide and the AWS Quick product page.

Amazon SES now supports higher limits for email identities, tenants, and configuration sets

Amazon Simple Email Service (Amazon SES) now supports higher limits for email identities, tenants, and configuration sets. You can view your current usage against each limit and request increases in the AWS Service Quotas console. A single account can now keep pace with your growth, so you no longer need to split email workloads across several accounts to stay within per-account limits.\n Customers running multi-tenant workloads often create a separate email identity, tenant, or configuration set for each customer, brand, or AI agent they serve. As you add more customers, brands, and AI agents, these resources can multiply quickly, and higher limits let all of these workloads grow in one account. To help you manage larger accounts, you can now also search these resources by name or status.

Higher limits for email identities, tenants, and configuration sets are available in all AWS Regions where Amazon SES is available.

To learn more, see Service quotas in Amazon SES in the Amazon SES Developer Guide and the Amazon SES product page.

AWS Blogs

AWS Japan Blog (Japanese)

AWS News Blog

AWS Cloud Financial Management

AWS Big Data Blog

AWS Compute Blog

AWS Database Blog

AWS for Industries

Artificial Intelligence

AWS for M&E Blog

AWS Messaging Blog

AWS Security Blog

AWS Storage Blog

Open Source Project

AWS CLI

Amazon EKS Anywhere