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.  

Today, AWS announced the ability for Amazon VPC IP Address Manager (IPAM) to distribute IPAM costs to AWS Organizations member accounts. This allows you to easily allocate costs to your internal teams for their IPAM usage.

VPC IPAM makes it easier for you to plan, track, and monitor IP addresses for your AWS workloads. When you enable IPAM for your AWS Organization, IPAM aggregates the organization-wide IP address usage, and charges the AWS account in which IPAM is created. With this launch, you can allocate the charges directly to AWS Organizations member accounts, for their individual usage. For example, you may have IPAM enabled in a central AWS account that runs multiple networking services, and want to allocate the IPAM charges across your internal teams, which you can do easily using this feature.

This feature is now available in all AWS Regions where Amazon VPC IPAM is supported, including AWS China Regions, and AWS GovCloud (US) Regions.

To learn more about IPAM, view the IPAM documentation. For details on pricing, refer to the IPAM tab on the Amazon VPC Pricing Page.

 

​Today, AWS announced the ability for Amazon VPC IP Address Manager (IPAM) to distribute IPAM costs to AWS Organizations member accounts. This allows you to easily allocate costs to your internal teams for their IPAM usage. VPC IPAM makes it easier for you to plan, track, and monitor IP addresses for your AWS workloads. When you enable IPAM for your AWS Organization, IPAM aggregates the organization-wide IP address usage, and charges the AWS account in which IPAM is created. With this launch, you can allocate the charges directly to AWS Organizations member accounts, for their individual usage. For example, you may have IPAM enabled in a central AWS account that runs multiple networking services, and want to allocate the IPAM charges across your internal teams, which you can do easily using this feature. This feature is now available in all AWS Regions where Amazon VPC IPAM is supported, including AWS China Regions, and AWS GovCloud (US) Regions. To learn more about IPAM, view the IPAM documentation. For details on pricing, refer to the IPAM tab on the Amazon VPC Pricing Page.  

AWS Launch Wizard now supports deployment of multi-node SAP NetWeaver applications on SAP ASE database, allowing you to deploy multiple applications servers at the time of deployment. With this deployment pattern, you deploy SAP application and ASE database components on different EC2 instances to meet your application performance requirements. This launch expands on existing Launch Wizard capability that allows you to automate deployment of SAP systems on SAP ASE database in single-node pattern.

AWS Launch Wizard offers a guided way of sizing, configuring, deploying, and scaling AWS resources for third party applications, such as Microsoft SQL Server and SAP systems, without the need to manually identify and provision individual AWS resources. This launch brings parity in supported deployment patterns of SAP NetWeaver on HANA database stack and SAP NetWeaver on ASE database stack.

To learn more about AWS Launch Wizard, visit the Launch Wizard Page.

 

​AWS Launch Wizard now supports deployment of multi-node SAP NetWeaver applications on SAP ASE database, allowing you to deploy multiple applications servers at the time of deployment. With this deployment pattern, you deploy SAP application and ASE database components on different EC2 instances to meet your application performance requirements. This launch expands on existing Launch Wizard capability that allows you to automate deployment of SAP systems on SAP ASE database in single-node pattern. AWS Launch Wizard offers a guided way of sizing, configuring, deploying, and scaling AWS resources for third party applications, such as Microsoft SQL Server and SAP systems, without the need to manually identify and provision individual AWS resources. This launch brings parity in supported deployment patterns of SAP NetWeaver on HANA database stack and SAP NetWeaver on ASE database stack. To learn more about AWS Launch Wizard, visit the Launch Wizard Page.  

Amazon Relational Database Service (Amazon RDS) for MySQL now supports MySQL minor versions 8.0.42 and 8.4.5, the latest minors released by the MySQL community. We recommend upgrading to the newer minor versions to fix known security vulnerabilities in prior versions of MySQL and to benefit from bug fixes, performance improvements, and new functionality added by the MySQL community. Learn more about the enhancements in RDS for MySQL 8.0.42 and 8.4.5 in the Amazon RDS user guide.

You can leverage automatic minor version upgrades to automatically upgrade your databases to more recent minor versions during scheduled maintenance windows. You can also leverage Amazon RDS Managed Blue/Green deployments for safer, simpler, and faster updates to your MySQL instances. Learn more about upgrading your database instances, including automatic minor version upgrades and Blue/Green Deployments, in the Amazon RDS User Guide.

Amazon RDS for MySQL makes it simple to set up, operate, and scale MySQL deployments in the cloud. Learn more about pricing details and regional availability at Amazon RDS for MySQL. Create or update a fully managed Amazon RDS for MySQL database in the Amazon RDS Management Console.

 

​Amazon Relational Database Service (Amazon RDS) for MySQL now supports MySQL minor versions 8.0.42 and 8.4.5, the latest minors released by the MySQL community. We recommend upgrading to the newer minor versions to fix known security vulnerabilities in prior versions of MySQL and to benefit from bug fixes, performance improvements, and new functionality added by the MySQL community. Learn more about the enhancements in RDS for MySQL 8.0.42 and 8.4.5 in the Amazon RDS user guide. You can leverage automatic minor version upgrades to automatically upgrade your databases to more recent minor versions during scheduled maintenance windows. You can also leverage Amazon RDS Managed Blue/Green deployments for safer, simpler, and faster updates to your MySQL instances. Learn more about upgrading your database instances, including automatic minor version upgrades and Blue/Green Deployments, in the Amazon RDS User Guide. Amazon RDS for MySQL makes it simple to set up, operate, and scale MySQL deployments in the cloud. Learn more about pricing details and regional availability at Amazon RDS for MySQL. Create or update a fully managed Amazon RDS for MySQL database in the Amazon RDS Management Console.  

Today, Amazon CloudWatch launched volume tiered pricing for AWS Lambda logs and support for additional delivery destinations. The new tiered pricing is effective immediately on Lambda function logs, requiring no code or configuration changes. For example in US East (N. Virginia), Lambda logs to CloudWatch pricing starts at $0.50 per GB tiering down to $0.05 per GB.

Additionally, CloudWatch now supports Amazon S3 and Amazon Data Firehose as Lambda log delivery destinations. These new destinations provide additional flexibility in Lambda log management, and are also available at volume tiered pricing. Again in US East (N. Virginia), pricing starts at $0.25 per GB tiering down to $0.05 per GB.

CloudWatch Logs volume tiered pricing is available in all AWS Regions where CloudWatch Logs and Lambda are available.

To learn more about these launches, visit the documentation, launch blog post, and the CloudWatch Logs pricing page.

 

​Today, Amazon CloudWatch launched volume tiered pricing for AWS Lambda logs and support for additional delivery destinations. The new tiered pricing is effective immediately on Lambda function logs, requiring no code or configuration changes. For example in US East (N. Virginia), Lambda logs to CloudWatch pricing starts at $0.50 per GB tiering down to $0.05 per GB. Additionally, CloudWatch now supports Amazon S3 and Amazon Data Firehose as Lambda log delivery destinations. These new destinations provide additional flexibility in Lambda log management, and are also available at volume tiered pricing. Again in US East (N. Virginia), pricing starts at $0.25 per GB tiering down to $0.05 per GB. CloudWatch Logs volume tiered pricing is available in all AWS Regions where CloudWatch Logs and Lambda are available. To learn more about these launches, visit the documentation, launch blog post, and the CloudWatch Logs pricing page.