Amazon Aurora with MySQL compatibility and PostgreSQL compatibility now supports R7i database instances in AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions. R7i database instances are powered by custom 4th Generation Intel Xeon Scalable processors. R7i instances offer larger instance sizes, up to 48xlarge and features an 8:1 ratio of memory to vCPU, and the latest DDR5 memory.

You can launch R7i database instances in the Amazon RDS Management Console or using the AWS CLI. Upgrading a database instance to R7i instance family requires a simple instance type modification. For more details, refer to the Aurora documentation.

Amazon Aurora is designed for unparalleled high performance and availability at global scale with PostgreSQL compatibility. It provides built-in security, continuous backups, serverless compute, up to 15 read replicas, automated multi-Region replication, and integrations with other AWS services. To get started with Amazon Aurora, take a look at our getting started page.
 

 

​Amazon Aurora with MySQL compatibility and PostgreSQL compatibility now supports R7i database instances in AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions. R7i database instances are powered by custom 4th Generation Intel Xeon Scalable processors. R7i instances offer larger instance sizes, up to 48xlarge and features an 8:1 ratio of memory to vCPU, and the latest DDR5 memory. You can launch R7i database instances in the Amazon RDS Management Console or using the AWS CLI. Upgrading a database instance to R7i instance family requires a simple instance type modification. For more details, refer to the Aurora documentation. Amazon Aurora is designed for unparalleled high performance and availability at global scale with PostgreSQL compatibility. It provides built-in security, continuous backups, serverless compute, up to 15 read replicas, automated multi-Region replication, and integrations with other AWS services. To get started with Amazon Aurora, take a look at our getting started page.    

Amazon Relational Database Service (Amazon RDS) for PostgreSQL, MySQL, and MariaDB now supports M7i database (DB) instances in Asia Pacific (Jakarta), South America (Sao Paulo), AWS GovCloud (US-East) and AWS GovCloud (US-West) regions. R7i DB instances are now supported in South America (Sao Paulo), AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions. M7i and R7i are the latest Intel based offering and are available with a new maximum instance size of 48xlarge, which brings 50% more vCPU and memory than the maximum size of M6i and R6i instance types.

M7i and R7i DB instances are available for Amazon RDS for PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher. M7i and R7i DB instances are also available for Amazon RDS for MySQL version 8.0.32 and higher, and Amazon RDS for MariaDB version 11.4, 10.11, 10.6, 10.5, and 10.4.

For complete information on pricing and regional availability, please refer to the Amazon RDS pricing page. Get started by creating any of these fully managed database instance using the Amazon RDS Management Console. For more details, refer to the Amazon RDS User Guide.
 

 

​Amazon Relational Database Service (Amazon RDS) for PostgreSQL, MySQL, and MariaDB now supports M7i database (DB) instances in Asia Pacific (Jakarta), South America (Sao Paulo), AWS GovCloud (US-East) and AWS GovCloud (US-West) regions. R7i DB instances are now supported in South America (Sao Paulo), AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions. M7i and R7i are the latest Intel based offering and are available with a new maximum instance size of 48xlarge, which brings 50% more vCPU and memory than the maximum size of M6i and R6i instance types. M7i and R7i DB instances are available for Amazon RDS for PostgreSQL version 17.1 and higher, 16.1 and higher, 15.4 and higher, 14.9 and higher, and 13.11 and higher. M7i and R7i DB instances are also available for Amazon RDS for MySQL version 8.0.32 and higher, and Amazon RDS for MariaDB version 11.4, 10.11, 10.6, 10.5, and 10.4. For complete information on pricing and regional availability, please refer to the Amazon RDS pricing page. Get started by creating any of these fully managed database instance using the Amazon RDS Management Console. For more details, refer to the Amazon RDS User Guide.    

AWS Graviton3-based R7g database instances are now generally available for Amazon Aurora with PostgreSQL compatibility and Amazon Aurora with MySQL compatibility in Middle East (Bahrain) and AWS GovCloud (US-West) Regions. Graviton3 instances provide up to 30% performance improvement over Graviton2 instances for Aurora depending on database engine, version, and workload.

Graviton3 processors offer several improvements over Graviton2 processors. Graviton3-based R7g are the first AWS database instances to feature the latest DDR5 memory, which provides 50% more memory bandwidth compared to DDR4, enabling high-speed access to data in memory. R7g database instances offer up to 30Gbps enhanced networking bandwidth and up to 20 Gbps of bandwidth to the Amazon Elastic Block Store (Amazon EBS).

You can launch Graviton3 R7g database instances in the Amazon RDS Management Console or using the AWS CLI. Graviton3 is supported by Aurora MySQL version 3.03.1 and higher, and Aurora PostgreSQL version 13.10 and higher, Aurora PostgreSQL 14.7 and higher, and Aurora PostgreSQL 15.2 and higher. Upgrading a database instance to Graviton3 requires a simple instance type modification. For more details, refer to the Aurora documentation.

Amazon Aurora is designed for unparalleled high performance and availability at global scale with full MySQL and PostgreSQL compatibility. It provides built-in security, continuous backups, serverless compute, up to 15 read replicas, automated multi-Region replication, and integrations with other AWS services. To get started with Amazon Aurora, take a look at our getting started page.
 

 

​AWS Graviton3-based R7g database instances are now generally available for Amazon Aurora with PostgreSQL compatibility and Amazon Aurora with MySQL compatibility in Middle East (Bahrain) and AWS GovCloud (US-West) Regions. Graviton3 instances provide up to 30% performance improvement over Graviton2 instances for Aurora depending on database engine, version, and workload. Graviton3 processors offer several improvements over Graviton2 processors. Graviton3-based R7g are the first AWS database instances to feature the latest DDR5 memory, which provides 50% more memory bandwidth compared to DDR4, enabling high-speed access to data in memory. R7g database instances offer up to 30Gbps enhanced networking bandwidth and up to 20 Gbps of bandwidth to the Amazon Elastic Block Store (Amazon EBS). You can launch Graviton3 R7g database instances in the Amazon RDS Management Console or using the AWS CLI. Graviton3 is supported by Aurora MySQL version 3.03.1 and higher, and Aurora PostgreSQL version 13.10 and higher, Aurora PostgreSQL 14.7 and higher, and Aurora PostgreSQL 15.2 and higher. Upgrading a database instance to Graviton3 requires a simple instance type modification. For more details, refer to the Aurora documentation. Amazon Aurora is designed for unparalleled high performance and availability at global scale with full MySQL and PostgreSQL compatibility. It provides built-in security, continuous backups, serverless compute, up to 15 read replicas, automated multi-Region replication, and integrations with other AWS services. To get started with Amazon Aurora, take a look at our getting started page.    

Amazon Relational Database Service (Amazon RDS) for PostgreSQL, MySQL, and MariaDB now supports AWS Graviton2-based T4g database instances in Asia Pacific (Malaysia) region. T4g database instances provide a baseline level of CPU performance, with the ability to burst CPU usage at any time for as long as required. For complete information on pricing and regional availability, please refer to the Amazon RDS pricing page.

T4g database instances are available on Amazon RDS for All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions. T4g database instances are available on Amazon RDS for MySQL versions 8.4 and 8.0, and Amazon RDS for MariaDB versions11.4, 10.11, 10.6, 10.5, and 10.4. You can upgrade to T4g by modifying the database instance type to T4g using the AWS Management Console or AWS CLI. For more details, refer to the Amazon RDS User Guide.
 

 

​Amazon Relational Database Service (Amazon RDS) for PostgreSQL, MySQL, and MariaDB now supports AWS Graviton2-based T4g database instances in Asia Pacific (Malaysia) region. T4g database instances provide a baseline level of CPU performance, with the ability to burst CPU usage at any time for as long as required. For complete information on pricing and regional availability, please refer to the Amazon RDS pricing page. T4g database instances are available on Amazon RDS for All PostgreSQL 17, 16, 15, 14, and 13 versions; and 12.7 and higher 12 versions. T4g database instances are available on Amazon RDS for MySQL versions 8.4 and 8.0, and Amazon RDS for MariaDB versions11.4, 10.11, 10.6, 10.5, and 10.4. You can upgrade to T4g by modifying the database instance type to T4g using the AWS Management Console or AWS CLI. For more details, refer to the Amazon RDS User Guide.    

AWS Graviton4-based R8g database instances are now generally available for Amazon Aurora with PostgreSQL compatibility and Amazon Aurora with MySQL compatibility in the AWS GovCloud (US-West) Region. R8g instances offer larger instance sizes, up to 48xlarge and features an 8:1 ratio of memory to vCPU, and the latest DDR5 memory. Graviton4-based instances provide up to a 40% performance improvement and up to 29% price/performance improvement for on-demand pricing over Graviton3-based instances of equivalent sizes on Amazon Aurora databases, depending on database engine, version, and workload.

AWS Graviton4 processors are the latest generation of custom-designed AWS Graviton processors built on the AWS Nitro System. R8g DB instances are available with new 24xlarge and 48xlarge sizes. With these new sizes, R8g DB instances offer up to 192 vCPU, up to 50Gbps enhanced networking bandwidth, and up to 40Gbps of bandwidth to the Amazon Elastic Block Store (Amazon EBS).

You can launch Gravitona4 R8g database instances in the Amazon RDS Management Console or using the AWS CLI. Upgrading a database instance to Graviton4 requires a simple instance type modification. For more details, refer to the Aurora documentation.

Amazon Aurora is designed for unparalleled high performance and availability at global scale with full MySQL and PostgreSQL compatibility. It provides built-in security, continuous backups, serverless compute, up to 15 read replicas, automated multi-Region replication, and integrations with other AWS services. To get started with Amazon Aurora, take a look at our getting started page.
 

 

​AWS Graviton4-based R8g database instances are now generally available for Amazon Aurora with PostgreSQL compatibility and Amazon Aurora with MySQL compatibility in the AWS GovCloud (US-West) Region. R8g instances offer larger instance sizes, up to 48xlarge and features an 8:1 ratio of memory to vCPU, and the latest DDR5 memory. Graviton4-based instances provide up to a 40% performance improvement and up to 29% price/performance improvement for on-demand pricing over Graviton3-based instances of equivalent sizes on Amazon Aurora databases, depending on database engine, version, and workload. AWS Graviton4 processors are the latest generation of custom-designed AWS Graviton processors built on the AWS Nitro System. R8g DB instances are available with new 24xlarge and 48xlarge sizes. With these new sizes, R8g DB instances offer up to 192 vCPU, up to 50Gbps enhanced networking bandwidth, and up to 40Gbps of bandwidth to the Amazon Elastic Block Store (Amazon EBS). You can launch Gravitona4 R8g database instances in the Amazon RDS Management Console or using the AWS CLI. Upgrading a database instance to Graviton4 requires a simple instance type modification. For more details, refer to the Aurora documentation. Amazon Aurora is designed for unparalleled high performance and availability at global scale with full MySQL and PostgreSQL compatibility. It provides built-in security, continuous backups, serverless compute, up to 15 read replicas, automated multi-Region replication, and integrations with other AWS services. To get started with Amazon Aurora, take a look at our getting started page.    

Amazon Elastic Container Registry (ECR) announces IPv6 support for API and Docker/OCI endpoints for both ECR and ECR Public. This makes it easier to standardize on IPv6 and remove IP address scalability limitations for your container build, deployment, and orchestration infrastructure.

With today’s launch, you can pull your private or public ECR images via the AWS SDK or Docker/OCI CLI using ECR’s new dual-stack endpoints which support both IPv4 and IPv6. When you make a request to an ECR dual-stack endpoint, the endpoint resolves to an IPv4 or an IPv6 address, depending on the protocol used by your network and client. This helps you meet IPv6 compliance requirements, and modernize your applications without expensive network address translation between IPv4 and IPv6 addresses.

ECR’s new dual-stack endpoints are generally available in all AWS commercial and AWS GovCloud (US) regions at no additional cost. Currently, ECR’s dual-stack endpoints do not serve AWS PrivateLink traffic originating from your Amazon Virtual Private Cloud (VPC). To get started with ECR IPv6, visit ECR documentation or ECR Public documentation.

 

​Amazon Elastic Container Registry (ECR) announces IPv6 support for API and Docker/OCI endpoints for both ECR and ECR Public. This makes it easier to standardize on IPv6 and remove IP address scalability limitations for your container build, deployment, and orchestration infrastructure. With today’s launch, you can pull your private or public ECR images via the AWS SDK or Docker/OCI CLI using ECR’s new dual-stack endpoints which support both IPv4 and IPv6. When you make a request to an ECR dual-stack endpoint, the endpoint resolves to an IPv4 or an IPv6 address, depending on the protocol used by your network and client. This helps you meet IPv6 compliance requirements, and modernize your applications without expensive network address translation between IPv4 and IPv6 addresses. ECR’s new dual-stack endpoints are generally available in all AWS commercial and AWS GovCloud (US) regions at no additional cost. Currently, ECR’s dual-stack endpoints do not serve AWS PrivateLink traffic originating from your Amazon Virtual Private Cloud (VPC). To get started with ECR IPv6, visit ECR documentation or ECR Public documentation.  

Amazon Relational Database Service (RDS) for PostgreSQL, MySQL, and MariaDB now supports AWS Graviton4-based M8g database instances in Europe (Ireland) Region and R8g database instances in AWS GovCloud (US-West) Region. For complete information on pricing and regional availability, please refer to the Amazon RDS pricing page.

Graviton4-based instances provide up to a 40% performance improvement and up to 29% price/performance improvement for on-demand pricing over Graviton3-based instances of equivalent sizes on Amazon RDS open source databases, depending on database engine, version, and workload.

M8g and R8g database instances are available on Amazon RDS for PostgreSQL version 17.1 and higher, 16.1 and higher, 15.2 and higher, 14.5 and higher, and 13.8 and higher. M8g and R8g database instances are available on Amazon RDS for MySQL version 8.0.32 and higher, and Amazon RDS for MariaDB version 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher. For more details on these instances and supported versions for each region, refer to the Amazon RDS User Guide. Get started by creating a fully managed M8g or R8g database instance using the Amazon RDS Management Console.

For complete information on pricing and regional availability, please refer to the Amazon RDS pricing page. For information on specific engine versions that support these DB instance types, please see the Amazon RDS documentation.
 

 

​Amazon Relational Database Service (RDS) for PostgreSQL, MySQL, and MariaDB now supports AWS Graviton4-based M8g database instances in Europe (Ireland) Region and R8g database instances in AWS GovCloud (US-West) Region. For complete information on pricing and regional availability, please refer to the Amazon RDS pricing page. Graviton4-based instances provide up to a 40% performance improvement and up to 29% price/performance improvement for on-demand pricing over Graviton3-based instances of equivalent sizes on Amazon RDS open source databases, depending on database engine, version, and workload. M8g and R8g database instances are available on Amazon RDS for PostgreSQL version 17.1 and higher, 16.1 and higher, 15.2 and higher, 14.5 and higher, and 13.8 and higher. M8g and R8g database instances are available on Amazon RDS for MySQL version 8.0.32 and higher, and Amazon RDS for MariaDB version 11.4.3 and higher, 10.11.7 and higher, 10.6.13 and higher, 10.5.20 and higher, and 10.4.29 and higher. For more details on these instances and supported versions for each region, refer to the Amazon RDS User Guide. Get started by creating a fully managed M8g or R8g database instance using the Amazon RDS Management Console. For complete information on pricing and regional availability, please refer to the Amazon RDS pricing page. For information on specific engine versions that support these DB instance types, please see the Amazon RDS documentation.    

An AI search flow builder is now available on Amazon OpenSearch Service when you launch OpenSearch 2.19+ domains. This new feature allows you to design and run AI search flows through a low-code experience free from custom middleware. It provides a low-code designer accessible through the AI search flows section of OpenSearch dashboards.

Using the builder, you can create sophisticated search flows enhanced by AWS and third-party AI services, and simply run then with a single query. Previously, you had develop custom code to integrate AI into advanced workflows and manage them on custom middleware. Now, you can use the low-code designer and automation APIs to run and customize search flows on OpenSearch for various use cases, such as retrieval augmented generation (RAG), dynamic query rewriting, reranking, semantic and multi-modal encoding, and more.

The AI search flow builder is available in all regions that support OpenSearch 2.19+ on the Amazon OpenSearch Service.

You can learn more from the documentation, and tutorials, including how to integrate various AI models from Amazon Bedrock, Amazon SageMaker, and other AWS and third-party AI services.

 

​An AI search flow builder is now available on Amazon OpenSearch Service when you launch OpenSearch 2.19+ domains. This new feature allows you to design and run AI search flows through a low-code experience free from custom middleware. It provides a low-code designer accessible through the AI search flows section of OpenSearch dashboards. Using the builder, you can create sophisticated search flows enhanced by AWS and third-party AI services, and simply run then with a single query. Previously, you had develop custom code to integrate AI into advanced workflows and manage them on custom middleware. Now, you can use the low-code designer and automation APIs to run and customize search flows on OpenSearch for various use cases, such as retrieval augmented generation (RAG), dynamic query rewriting, reranking, semantic and multi-modal encoding, and more. The AI search flow builder is available in all regions that support OpenSearch 2.19+ on the Amazon OpenSearch Service. You can learn more from the documentation, and tutorials, including how to integrate various AI models from Amazon Bedrock, Amazon SageMaker, and other AWS and third-party AI services.  

Amazon Connect now publishes a new contact completion event in the Contact Event Stream (via Amazon EventBridge), delivering real-time insights into when a contact has fully concluded, including the completion of any after-contact work (ACW). This new event empowers contact centers with full-lifecycle visibility into customer and agent interactions, enabling smarter, faster downstream actions. For example, if you were to automatically create a follow-up ticket once an agent finishes their wrap-up work, this event gives you a precise, real-time signal to trigger that workflow, ensuring your systems stay in sync and your customer service stays responsive.

To learn more, refer to the Contact events – Amazon Connect. This new event is available in all AWS regions where Amazon Connect is available. Amazon Connect contact events do not incur additional Amazon Connect charges. You may incur charges for Amazon EventBridge usage. Please see Amazon EventBridge Pricing for more information. To learn more about Amazon Connect, the easy-to-use cloud contact center, visit the Amazon Connect website.

 

​Amazon Connect now publishes a new contact completion event in the Contact Event Stream (via Amazon EventBridge), delivering real-time insights into when a contact has fully concluded, including the completion of any after-contact work (ACW). This new event empowers contact centers with full-lifecycle visibility into customer and agent interactions, enabling smarter, faster downstream actions. For example, if you were to automatically create a follow-up ticket once an agent finishes their wrap-up work, this event gives you a precise, real-time signal to trigger that workflow, ensuring your systems stay in sync and your customer service stays responsive. To learn more, refer to the Contact events – Amazon Connect. This new event is available in all AWS regions where Amazon Connect is available. Amazon Connect contact events do not incur additional Amazon Connect charges. You may incur charges for Amazon EventBridge usage. Please see Amazon EventBridge Pricing for more information. To learn more about Amazon Connect, the easy-to-use cloud contact center, visit the Amazon Connect website.  

Amazon Connect now provides richer contact information through the DescribeContact API, enabling your contact center to take smarter, faster action during and after customer interactions. This update surfaces key insights such as disconnect reasons, recording status, after-contact work time, and custom contact attributes, all in a single API response, helping to reduce complexity and improve performance. For example, a customer chat session might disconnect due to a network issue on the agent’s end. With the new DisconnectReason field in the DescribeContact API, you can now programmatically detect this and re-queue the chat for follow-up, ensuring the customer gets help without having to restart the conversation.

To learn more, refer to our public documentation. This new feature is available in all AWS regions where Amazon Connect is available. To learn more about Amazon Connect, the AWS contact center as a service solution on the cloud, please visit the Amazon Connect website.

 

​Amazon Connect now provides richer contact information through the DescribeContact API, enabling your contact center to take smarter, faster action during and after customer interactions. This update surfaces key insights such as disconnect reasons, recording status, after-contact work time, and custom contact attributes, all in a single API response, helping to reduce complexity and improve performance. For example, a customer chat session might disconnect due to a network issue on the agent’s end. With the new DisconnectReason field in the DescribeContact API, you can now programmatically detect this and re-queue the chat for follow-up, ensuring the customer gets help without having to restart the conversation. To learn more, refer to our public documentation. This new feature is available in all AWS regions where Amazon Connect is available. To learn more about Amazon Connect, the AWS contact center as a service solution on the cloud, please visit the Amazon Connect website.