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

Recent Announcements

Amazon Redshift now supports multi-statement transactions, conflict resolution, and time travel for Apache Iceberg

Amazon Redshift now supports multi-statement transactions, automatic write-conflict resolution, and time travel for Apache Iceberg tables. You can run multi-step, concurrent transformation pipelines directly on Iceberg tables and audit the results, with the transaction semantics you expect from a data warehouse. This helps anyone writing to Iceberg tables at production scale. Batch jobs get all-or-nothing commits across multiple steps. Streaming and scheduled jobs can write to the same tables at the same time. Analysts, auditors, and AI agents can query a table as it existed at any point in time.\n With multi-statement transactions, you group several statements in a single BEGIN…COMMIT statement and publish them as one atomic Iceberg snapshot. This means a multi-step load such as a MERGE followed by a DELETE, can be commited together as one atomic operation, are never queryable in a half-applied state, and roll back cleanly if there’s a failure. Automatic conflict resolution lets concurrent writes, such as streaming inserts alongside scheduled deletes, write to the same table and commit together when their changes don’t overlap, instead of failing and retrying. Time travel lets you query a table as it existed at a past point in time with AS OF TIMESTAMP. You can use it to reproduce reports, audit changes, or recover from a bad write without keeping extra copies. These capabilities are available in all AWS commercial Regions for Amazon Redshift’s provisioned RG or serverless clusters that are writing to or querying Iceberg tables.. To get started, see the following list of resources:

1/ Resolving concurrent writes for Apache Iceberg tables using Amazon Redshift

2/ Multi-statement transactions for Apache Iceberg tables in Amazon Redshift

3/ Time travel support for Apache Iceberg

AWS DevOps Agent is now available in AWS GovCloud (US-West)

Now available in AWS GovCloud (US-West), AWS DevOps Agent is your always-available operations teammate that resolves and proactively prevents incidents, optimizes application reliability and performance, and handles on-demand SRE tasks across AWS, multicloud, and on-prem environments.\n DevOps Agent investigates incidents and identifies operational improvements as an experienced teammate would: by learning your applications and their relationships, working with your observability tools, runbooks, code repositories, and CI/CD pipelines, and correlating telemetry, code, and deployment data. It autonomously triages incidents and guides teams to rapid resolution, reducing mean time to resolution (MTTR) from hours to minutes, while analyzing patterns across historical incidents to deliver actionable recommendations that prevent future outages. For the full list of AWS Regions where AWS DevOps Agent is available, visit the Regions list. Pricing details are available on the AWS DevOps Agent pricing page. AWS Support customers receive monthly DevOps Agent credits based on the prior month’s AWS Support charge: 100% for Unified Operations, 75% for Enterprise Support, or 30% for Business Support+. For many customers, this significantly reduces or eliminates DevOps Agent costs. For details, visit the support compare page. To learn more, read the launch blog and see getting started.

Set up, connect, and govern AI agents faster with Amazon WorkSpaces

Building AI agents has become essential. Across your organization, teams want agents to handle ERP transactions, work through a claims queue, and operate the same applications your people use every day. But how do you move from experiments to production? Before an agent touches real systems and real data, you need to verify who it acted on behalf of, what it did, and whether it stayed within the limits you set. Without that visibility, the agent stays stuck in testing, and the value is never realized.\n Earlier this year, we launched Amazon WorkSpaces for AI agents, extending the power and security of a cloud work environment to agents, not just people. Today, we’re excited to announce new capabilities that make it even easier to operate agents confidently across your enterprise and move them from proof of concept to governed production in fewer steps.  You can set up new agents or connect the ones your builders have already built, run them under your own identity providers and policies, and keep a record of everything they do. You don’t need to stitch together new tools or build custom monitoring.

Setup used to mean configuring the machine by hand. Now, you can just describe what your agent needs to your AI coding assistant such as Claude Code, Codex, and Kiro. Guided by AWS MCP skills, the assistant builds the WorkSpace from defaults you can adjust. If your teams build on Amazon Bedrock AgentCore, you can connect an agent directly with your AWS credentials and skip writing any agent code. New tools also reduce agent costs and increase accuracy by letting an agent carry out a series of actions in a single call and use the computer-use actions its model already knows.

But an agent that can work is not necessarily an agent you can trust with mission-critical work and sensitive data. This release gives you the same oversight over an agent that you have over the employees you manage. First, agents can now sign in through any identity provider (IdP) that supports OIDC, in addition to the existing SAML support. Administrators can send sign-in straight to their IdP, so users authenticate with their usual corporate credentials, and you don’t build custom authentication. Second, with on-behalf-of (OBO) sign-in, an agent works as the signed-in user, with that user’s existing directory identity, permissions, and Group Policies on the desktop. 

WorkSpaces now offers session replay, giving you a reviewable record of what your agent did. Session replay turns session screenshots into a video and pairs it with a plain-language transcript of the agent’s actions. Both are stored in your own Amazon S3 bucket and encrypted with your own keys. Your security team can see what the agent saw, and your compliance team gets evidence to support audits.

Together, these updates help move agents out of pilots and into real production scale. Your teams can keep working the way they do today, with agents working alongside them in familiar and trusted cloud work environments. And every one of those agents is held to the same identity, policy, and audit standards as the rest of your workforce. With WorkSpaces, you can bring AI agents into your business without rebuilding decades of software or needing a separate environment to govern them.

To get started operating AI agents on WorkSpaces, visit our documentation page.

AWS WAF advanced rate-based rules are now available in AWS GovCloud (US), Thailand, and Mexico

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

AWS Backup adds logically air-gapped vault support for Amazon RDS

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

AgentCore runtime instances are now available in six more AWS Regions

Amazon Bedrock AgentCore runtime instances are now available in six additional AWS Regions: US West (N. California), Canada (Central), Europe (London), Europe (Paris), Europe (Stockholm), and Asia Pacific (Seoul). Runtime instances run your agents on Amazon EC2 instances while AgentCore handles provisioning, patching, scaling, and lifecycle management.\n By expanding to these AWS Regions, more teams can use runtime instance capabilities such as GPU-accelerated, memory-optimized, or compute-optimized instance types, and long-running agent sessions of up to 14 days. You can run your agents closer to your users to reduce invocation latency, and keep agent instances, storage volumes, and session data in the Region that your data residency requirements call for.

With this expansion, you can use runtime instances in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), and Asia Pacific (Tokyo). You are charged for managing the provisioned compute, in addition to your Amazon EC2 costs.

To get started, see the following resources:

Supported AWS Regions in the Amazon Bedrock AgentCore Developer Guide

AgentCore pricing

Runtime instances and capacity providers in the Amazon Bedrock AgentCore Developer Guide

AWS Blogs

AWS Japan Blog (Japanese)

AWS News Blog

AWS Architecture Blog

AWS Cloud Operations Blog

AWS Big Data Blog

Containers

AWS Database Blog

Desktop and Application Streaming

AWS DevOps & Developer Productivity Blog

AWS for Industries

Artificial Intelligence

Networking & Content Delivery

AWS Storage Blog

Open Source Project

AWS CLI