8/12/2026, 12:00:00 AM ~ 8/13/2026, 12:00:00 AM (UTC)
Recent Announcements
AWS Global View now offers an interactive map view for AWS Regions and AWS Local Zones
Today, AWS announces the addition of an interactive map view to AWS Global View in the AWS Management Console, providing a visual way to explore AWS Global Infrastructure.\n Previously, customers had to scan through a list of AWS locations in AWS Global View. With this new capability, customers can toggle between the interactive map view and the existing list view, making it easier to visualize their global AWS infrastructure footprint.
When customers select the map view, they will see all AWS Regions and AWS Local Zones plotted on an interactive map. This capability helps customers make informed infrastructure planning decisions by visualizing already enabled AWS locations and the full range of AWS locations available to them, all in a single glance.
This capability is available across all public AWS Regions. To get started, navigate to the Regions and Zones page in AWS Global View console. For more information, see the AWS Global View documentation.
Amazon EKS now supports advanced Kubernetes control plane configuration parameters
Amazon Elastic Kubernetes Service (Amazon EKS) now supports configuring parameters for Kubernetes control plane components including the scheduler, controller manager, and API server. You can tune pod placement strategies to improve resource utilization, adjust how quickly horizontal pod autoscaling responds to changes in demand, set resource lifecycle parameters such as event retention duration, and more.\n Cluster administrators now have more control over Kubernetes control plane parameters beyond the defaults. For example, you can set the scheduler’s node resource fit strategy parameter to MostAllocated, which packs pods onto nodes that are already well utilized and helps you run the same workloads on fewer nodes. The default LeastAllocated strategy spreads pods across nodes, and you can keep it where headroom matters more than density. You can configure Kubernetes control plane parameters in any AWS Region where Amazon EKS is available. For the full list of configurable parameters and to learn more, see Control plane configuration in the Amazon EKS User Guide.
Amazon Connect Customer supports manual assignment of queued agent-first callbacks
Amazon Connect Customer now lets agents view and self-assign queued agent-first callbacks alongside emails, tasks, and chats. This gives agents the option to prioritize work that needs immediate follow-up or for which they already have relevant context. For example, an agent familiar with a customer’s issue can assign the callback to themselves, avoiding another handoff and helping resolve the issue faster.\n This feature is available in all AWS Regions where Amazon Connect Customer is available. To learn more about how to use queued callbacks, refer to our documentation Access the Worklist app and Set up queued callbacks. For more information about Amazon Connect Customer, visit our product page.
Amazon Quick adds deny by default for custom permissions
Amazon Quick custom permissions now include deny by default, a governance setting that automatically restricts new AI capabilities before they reach users.\n Previously, new AI capabilities were available to all users on release, requiring administrators to react after the fact. With deny by default, administrators restrict the AI capability category in a custom permissions profile and assign it to users, roles, or the entire account. Quick then denies any new AI capability at launch for those users. Restricting a category also restricts existing capabilities in it. Administrators explicitly allow each capability when ready. The restriction applies only to the profile you configure. Configure deny by default in Manage account in Amazon Quick or through the AWS CLI. To learn more, see Custom permissions deny by default. Deny by default is available in all AWS Regions where Amazon Quick is available.
Amazon Quick now supports data loss prevention with Microsoft Purview
Amazon Quick now integrates with Microsoft Purview to enforce data loss prevention (DLP) policies across your Quick environment. Organizations need to ensure that sensitive files aren’t shared outside approved channels. With this integration, IT administrators and security teams can apply their existing Purview sensitivity labels to automatically control how files are handled in Quick capabilities such as chat, spaces, and knowledge bases.\n Administrators can configure enforcement actions (block, warn, or allow) for each sensitivity label, giving organizations granular control over sensitive file sharing across Quick. For example, a financial services company can block files labeled “Highly Confidential” from being uploaded to shared spaces while allowing “Internal” files with a warning notification. With this integration, customers can extend their existing Microsoft Purview governance policies into Quick without additional tools.
This feature is available in all AWS Regions where Amazon Quick agentic capabilities are supported. For more information, see the AWS Region table. To learn more, see Data loss prevention in the Amazon Quick User Guide.
AWS Blogs
AWS Japan Blog (Japanese)
- Introducing the AI agent evaluation pipeline Motorway built with AgentCore and AgentCore
- How Amazon OpenSearch Service builds a 1 billion vector index with GPU acceleration
- 1 year experience. 4.5 billion lines of code. 1.6 million hours saved. And what we’ve learned.
- Turn Amazon CloudWatch alarms into actionable signals
AWS Compute Blog
AWS Contact Center
- Crystal Clear in Chaos: Your Contact Center Didn’t Lose Its Walls. It Lost Its Acoustics.
- Amazon Connect Service Quota Monitor
- Best practices for measuring agent connection time in Amazon Connect Outbound Campaigns
Containers
- Forensic container checkpointing on Amazon Elastic Kubernetes Service (Amazon EKS)
- Introducing advanced Kubernetes control plane configuration in Amazon EKS
AWS Database Blog
- Introducing Oracle Exadata on Exascale for Oracle AI Database@AWS
- Migrate Amazon Aurora PostgreSQL across major versions with active Debezium CDC connectors using native logical replication
AWS DevOps & Developer Productivity Blog
Artificial Intelligence
- Part 2: Amazon Bedrock cost attribution with Amazon Athena and CUDOS
- How OneAdvanced deployed over 50 AI agents on UK-sovereign AWS
- Pay with confidence: How Solv Labs built verifiable, auditable agent payments on Amazon Bedrock AgentCore payments
- Tiered KV cache for large LLMs on Amazon SageMaker HyperPod with Curvine
AWS Messaging Blog
AWS Security Blog
AWS Storage Blog
- Securing backup data against modern threats with AWS Backup
- Hybrid ML inferencing on Amazon EKS with Amazon FSx for NetApp ONTAP and on-premises NetApp