1/23/2026, 12:00:00 AM ~ 1/26/2026, 12:00:00 AM (UTC)
Recent Announcements
Amazon Route 53 Domains adds support for .ai, and other top-level domains
Amazon Route 53 Domains now supports registration and management of ten new top-level domains (TLDs): .ai, .nz, .shop, .bot, .moi, .spot, .free, .deal, .now, and .hot. This expansion enhances Route 53’s capabilities as a domain registration and DNS management service, offering customers more options to establish their online presence. With these additions, businesses and individuals can now leverage domain names tailored to specific industries, regions, or purposes directly through Amazon Web Services (AWS).\n The new TLDs cater to various use cases. To name a few, the .ai domain, originally for Anguilla, has become popular among artificial intelligence companies. E-commerce sites can utilize .shop for their online storefronts. The .bot domain suits chatbot and AI-related services. The .now domain works well for time-sensitive services and instant delivery platforms. Users can register these domains through the Route 53 console, AWS CLI, or SDKs, enjoying integrated DNS management and automatic renewal features. This seamless integration allows for efficient domain administration alongside existing Route 53 hosted zones and DNS records. To learn more about Amazon Route 53 Domains and start registering new domains, visit the Amazon Route 53 page. Domain registration pricing varies by TLD. Visit the pricing page for detailed pricing information.
EC2 Auto Scaling Introduces New Mechanisms for Group Deletion Protection
EC2 Auto Scaling is introducing a new policy condition key autoscaling:ForceDelete. This condition key is used with the DeleteAutoScalingGroup action to control whether the ForceDelete parameter can be used during deletion, which determines if an Auto Scaling group (ASG) can be deleted while it still contains running instances. You can use this condition key in IAM policies to restrict deletion permissions. This provides a safety measure to prevent accidental deletion of ASGs that still have running instances.\n Furthermore, EC2 Auto Scaling now offers deletion protection at the group level. The new deletion-protection configuration can be set either when you create your ASGs or update them. This new feature lets you set enhanced controls based on your workload’s criticality, with multiple protection levels available to safeguard against accidental deletions and help maintain application availability. Combining the autoscaling:ForceDelete condition key with deletion protection at the group level provides a layered defense against unwanted ASG termination by allowing you to both restrict IAM permissions for force-delete operations and set enhanced protection controls directly on critical ASGs. The features now available in all AWS Regions and AWS GovCloud (US) Regions. To get started, visit the EC2 Auto Scaling console or refer to our technical documentation for deletion protection and policy condition keys for Amazon EC2 Auto Scaling.
Amazon EVS now supports multiple VMware NSX Edge Gateways
Today, we’re announcing that Amazon Elastic VMware Service (Amazon EVS) now supports the ability to deploy multiple VMware NSX Tier-0 Gateways within VMware Software-Defined Data Centers (SDDC), enabling enhanced network segmentation and more flexible routing configurations.\n Multiple NSX Tier-0 Gateways allow for better performance and scale by distributing network traffic across multiple NSX Edge Clusters. This latest enhancement enables improved network segmentation, allowing you to isolate different workload environments and maintain distinct security policies for each gateway. You can also use multiple gateways to create separate test environments for validating network configurations and performing gateway upgrades with minimal impact to production workloads. This architecture flexibility helps you align your network topology with specific business requirements while maintaining operational efficiency in running your VMware workloads on AWS with Amazon EVS. To learn more about this newest enhancement, read this re:Post article that walks you through the process of deploying multiple NSX Edge Clusters within your EVS environment. To get started with Amazon EVS, visit the product detail page and user guide.
Announcing general availability of Amazon EC2 M4 Max Mac instances
Amazon Web Services announces general availability of Amazon EC2 M4 Max Mac instances, powered by the latest Mac Studio hardware. Amazon EC2 M4 Max Mac instances are the next-generation EC2 Mac instances, that enable Apple developers to migrate their most demanding build and test workloads onto AWS. These instances are ideal for building and testing applications for Apple platforms such as iOS, macOS, iPadOS, tvOS, watchOS, visionOS, and Safari.\n Amazon EC2 M4 Max Mac instances offer up to 25% better application build performance compared to Amazon EC2 M1 Ultra Mac instances. M4 Max Mac instances are powered by the AWS Nitro System, providing up to 10 Gbps network bandwidth and 8 Gbps of Amazon Elastic Block Store (Amazon EBS) storage bandwidth. These instances are built on Apple M4 Max Mac Studio computers featuring a 16-core CPU, 40-core GPU, 16-core Neural Engine, and 128GB of unified memory.
Amazon EC2 M4 Max Mac instances are available in US East (N. Virginia) and US West (Oregon). To learn more about Amazon EC2 M4 Max Mac instances, visit the Amazon EC2 Mac page.
Amazon RDS for Oracle now supports replicas in Oracle multi-tenant configuration
Amazon RDS for Oracle now supports database replicas for instances set up in Oracle multi-tenant configuration. Oracle multi-tenant configuration allows customers to host multiple, isolated pluggable databases in a single container database, which allows for cost reduction through consolidation and easier management. With support for replicas in Oracle multi-tenant configuration, customers can now distribute read workloads to a replica to scale workloads, or setup cross-Region replicas. In disaster recovery situations, customers can promote replicas to serve as a new standalone database, or execute a switchover to reverse roles between the primary database and the replica for a quick recovery.\n To set up replicas in Oracle multi-tenant configuration, customers can create a replica in either mounted or read-only mode using the AWS management console, AWS CLI, or AWS SDK. Once a replica is set up, Amazon RDS for Oracle manages asynchronous physical replication between primary and replica database instances using Oracle Data Guard.
Amazon RDS for Oracle read replicas use Oracle Data Guard. Using mounted mode replicas require an Oracle Database Enterprise Edition (EE) license, and using read-only mode replicas require additional Oracle Active Data Guard licenses. We recommend customers to consult their Oracle licensing expert to determine Oracle licensing requirements. Refer to RDS for Oracle User Guide for more information, and Amazon RDS for Oracle pricing for available instance configurations, pricing, and region availability.
Amazon Connect adds conditional logic and real-time updates to Step-by-Step Guides
Amazon Connect Step-by-Step Guides now enables managers to build more dynamic and responsive guided experiences. Managers can create conditional user interfaces that adapt based on user interactions, making workflows more efficient. For example, managers can configure dropdown menus to show or hide fields, change default values, or adjust required fields based on the input in prior fields, creating tailored experiences for different scenarios.\n In addition, Step-by-Step Guides can now automatically refresh data from Connect resources such as flow modules at specified intervals, ensuring agents always work with the most current information. Amazon Connect Step-by-Step Guides is available in the following AWS regions: US East (N. Virginia), US West (Oregon), Canada (Central), Africa (Cape Town), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (London), and the AWS GovCloud (US-West) Region. To learn more and get started, visit the Amazon Connect webpage and documentation.
AWS Blogs
AWS Japan Blog (Japanese)
- Kiro CLI 1.24.0: Skills, custom diff tools, improved code intelligence, and conversation compression
- Build durable AI agents with LangGraph and Amazon DynamoDB
- Introducing Amazon EC2 G7e instances accelerated with NVIDIA RTX PRO 6000 Blackwell Server Edition GPUs
- Response to “Guidelines on Procurement and Utilization of Generative AI for Government Evolution and Innovation” — AWS Sample Response to Procurement Check Sheet Requirements
- Amazon EKS’s zero operator access design has been confirmed by an independent third party
- Zero operator access in Amazon Bedrock’s next-generation inference engine Mantle
Containers
AWS for Industries
- Bridging the Knowledge Gap: Using Generative AI on AWS to Preserve Critical Expertise
- How to outrank, outsell, and outperform in AI search with Pattern’s GEO Scorecard
Artificial Intelligence
- Build AI agents with Amazon Bedrock AgentCore using AWS CloudFormation
- How the Amazon.com Catalog Team built self-learning generative AI at scale with Amazon Bedrock
AWS for M&E Blog
AWS Security Blog
- Updated PCI PIN compliance package for AWS Payment Cryptography now available
- AWS achieves 2025 C5 Type 2 attestation report with 183 services in scope
- AWS renews the GSMA SAS-SM certification for two AWS Regions and expands to cover four new Regions
- Exploring common centralized and decentralized approaches to secrets management
AWS Storage Blog
- Monitoring Amazon EFS KPIs using Amazon CloudWatch metrics
- Applying Amazon S3 Object Lock at scale for petabytes of existing data