DynamoDB now supports more granular throttling exceptions along with their corresponding Amazon CloudWatch metrics. The additional fields in the new throttling exceptions identify the specific resources and reasons for throttling events, making it easier to understand and diagnose throttling-related issues.

You can see the new Amazon CloudWatch metrics immediately, and upon upgrading your SDK to the newest version, you will also see the new granular throttling exceptions. Every throttling exception now contains a list of reasons why the request was throttled, as well as the Amazon Resource Name (ARN) of the table or index that was throttled. These new throttle exception reasons help you understand why you were throttled and enable you to take corrective actions like adjusting your configured throughput, switching your table to on-demand capacity mode, or optimizing data access patterns.

The more granular throttling exceptions and their respective metrics are available in all commercial AWS Regions, the AWS GovCloud (US) Regions, and the China Regions.

To get started see the following list of resources:

• Diagnosing throttling issues in the DynamoDB developer guide
• Enhanced throttling observability in Amazon DynamoDB blog post
• Troubleshooting throttling in the DynamoDB developer guide

 

​DynamoDB now supports more granular throttling exceptions along with their corresponding Amazon CloudWatch metrics. The additional fields in the new throttling exceptions identify the specific resources and reasons for throttling events, making it easier to understand and diagnose throttling-related issues. You can see the new Amazon CloudWatch metrics immediately, and upon upgrading your SDK to the newest version, you will also see the new granular throttling exceptions. Every throttling exception now contains a list of reasons why the request was throttled, as well as the Amazon Resource Name (ARN) of the table or index that was throttled. These new throttle exception reasons help you understand why you were throttled and enable you to take corrective actions like adjusting your configured throughput, switching your table to on-demand capacity mode, or optimizing data access patterns. The more granular throttling exceptions and their respective metrics are available in all commercial AWS Regions, the AWS GovCloud (US) Regions, and the China Regions. To get started see the following list of resources:

Diagnosing throttling issues in the DynamoDB developer guide
Enhanced throttling observability in Amazon DynamoDB blog post
Troubleshooting throttling in the DynamoDB developer guide  

DynamoDB now supports the ability to selectively emit events for throttled keys to CloudWatch Contributor Insights, enabling you to monitor throttled keys without emitting events for all accessed keys. By emitting events for throttled keys exclusively, you no longer need to pay for all of your successful request events.

Cloudwatch Contributor Insights for DynamoDB can help you understand your traffic patterns by providing information about your most accessed and throttled keys in a table or global secondary index. This information can be used to understand your application usage patterns or diagnose throttling-related issues. By choosing to only emit events for throttled keys, you can reduce the amount you spend to receive these insights.

The new mode to exclusively emit throttled key events to CloudWatch Contributor Insights is available in all commercial AWS Regions, the AWS GovCloud (US) Regions, and the China Regions.

To get started, see the following list of resources:

• CloudWatch Contributor Insights for DynamoDB in the DynamoDB developer guide
• Enhanced throttling observability in Amazon DynamoDB blog post
• Troubleshooting throttling in the DynamoDB developer guide

 

​DynamoDB now supports the ability to selectively emit events for throttled keys to CloudWatch Contributor Insights, enabling you to monitor throttled keys without emitting events for all accessed keys. By emitting events for throttled keys exclusively, you no longer need to pay for all of your successful request events. Cloudwatch Contributor Insights for DynamoDB can help you understand your traffic patterns by providing information about your most accessed and throttled keys in a table or global secondary index. This information can be used to understand your application usage patterns or diagnose throttling-related issues. By choosing to only emit events for throttled keys, you can reduce the amount you spend to receive these insights. The new mode to exclusively emit throttled key events to CloudWatch Contributor Insights is available in all commercial AWS Regions, the AWS GovCloud (US) Regions, and the China Regions. To get started, see the following list of resources:

CloudWatch Contributor Insights for DynamoDB in the DynamoDB developer guide
Enhanced throttling observability in Amazon DynamoDB blog post
Troubleshooting throttling in the DynamoDB developer guide  

AWS Certificate Manager (ACM) now supports AWS PrivateLink so that you can access ACM APIs from your Amazon Virtual Private Cloud (VPC) without traversing the public internet. This feature can help you meet compliance requirements by allowing you to access and use ACM APIs entirely within the AWS network.

ACM simplifies the process of provisioning and managing public and private TLS certificates, wherever you need to securely terminate traffic; Whether it’s with integrated AWS services such as Amazon CloudFront, Load Balancing or with hybrid workloads. You can now create interface endpoints in AWS Private Link to connect your VPC to ACM. Communication between your VPC and ACM is then conducted entirely within the AWS network, providing a secure pathway for your data.

To get started, you can create an AWS PrivateLink to connect to ACM using the AWS Management Console or AWS Command Line Interface (AWS CLI) commands or AWS CloudFormation. This new feature is available in all AWS Regions including AWS GovCloud (US) and China Regions where AWS Certificate Manager Service and AWS PrivateLink are available. For more information, please refer to the AWS PrivateLink documentation.

 

​AWS Certificate Manager (ACM) now supports AWS PrivateLink so that you can access ACM APIs from your Amazon Virtual Private Cloud (VPC) without traversing the public internet. This feature can help you meet compliance requirements by allowing you to access and use ACM APIs entirely within the AWS network. ACM simplifies the process of provisioning and managing public and private TLS certificates, wherever you need to securely terminate traffic; Whether it’s with integrated AWS services such as Amazon CloudFront, Load Balancing or with hybrid workloads. You can now create interface endpoints in AWS Private Link to connect your VPC to ACM. Communication between your VPC and ACM is then conducted entirely within the AWS network, providing a secure pathway for your data. To get started, you can create an AWS PrivateLink to connect to ACM using the AWS Management Console or AWS Command Line Interface (AWS CLI) commands or AWS CloudFormation. This new feature is available in all AWS Regions including AWS GovCloud (US) and China Regions where AWS Certificate Manager Service and AWS PrivateLink are available. For more information, please refer to the AWS PrivateLink documentation.  

Amazon Relational Database Service (RDS) for Db2 now supports cross-region automated backups for encrypted databases, providing customers with an additional layer of data protection while safeguarding their mission critical Db2 workloads against regional outages.

Customers can now securely copy encrypted database snapshots to regions outside of their primary AWS region for improved disaster recovery. The feature can be enabled by simply turning on encryption for RDS for Db2 instances, and configuring backup replication to the desired AWS region.

To learn more about Amazon RDS for Db2 cross-region automated backups and the supported destination regions, visit the documentation page. Amazon RDS for Db2 makes it simple to set up, operate, and scale Db2 deployments in the cloud. See Amazon RDS for Db2 Pricing for up-to-date pricing of instances, storage, backup, data transfer, and regional availability.

 

​Amazon Relational Database Service (RDS) for Db2 now supports cross-region automated backups for encrypted databases, providing customers with an additional layer of data protection while safeguarding their mission critical Db2 workloads against regional outages. Customers can now securely copy encrypted database snapshots to regions outside of their primary AWS region for improved disaster recovery. The feature can be enabled by simply turning on encryption for RDS for Db2 instances, and configuring backup replication to the desired AWS region. To learn more about Amazon RDS for Db2 cross-region automated backups and the supported destination regions, visit the documentation page. Amazon RDS for Db2 makes it simple to set up, operate, and scale Db2 deployments in the cloud. See Amazon RDS for Db2 Pricing for up-to-date pricing of instances, storage, backup, data transfer, and regional availability.  

Starting today, Amazon Elastic Compute Cloud (Amazon EC2) R8g instances are available in AWS Asia Pacific (Jakarta)region. These instances are powered by AWS Graviton4 processors and deliver up to 30% better performance compared to AWS Graviton3-based instances. Amazon EC2 R8g instances are ideal for memory-intensive workloads such as databases, in-memory caches, and real-time big data analytics. These instances are built on the AWS Nitro System, which offloads CPU virtualization, storage, and networking functions to dedicated hardware and software to enhance the performance and security of your workloads.

AWS Graviton4-based Amazon EC2 instances deliver the best performance and energy efficiency for a broad range of workloads running on Amazon EC2. AWS Graviton4-based R8g instances offer larger instance sizes with up to 3x more vCPU (up to 48xlarge) and memory (up to 1.5TB) than Graviton3-based R7g instances. These instances are up to 30% faster for web applications, 40% faster for databases, and 45% faster for large Java applications compared to AWS Graviton3-based R7g instances. R8g instances are available in 12 different instance sizes, including two bare metal sizes. They offer up to 50 Gbps enhanced networking bandwidth and up to 40 Gbps of bandwidth to the Amazon Elastic Block Store (Amazon EBS).

To learn more, see Amazon EC2 R8g Instances. To explore how to migrate your workloads to Graviton-based instances, see AWS Graviton Fast Start program and Porting Advisor for Graviton. To get started, see the AWS Management Console.

 

​Starting today, Amazon Elastic Compute Cloud (Amazon EC2) R8g instances are available in AWS Asia Pacific (Jakarta)region. These instances are powered by AWS Graviton4 processors and deliver up to 30% better performance compared to AWS Graviton3-based instances. Amazon EC2 R8g instances are ideal for memory-intensive workloads such as databases, in-memory caches, and real-time big data analytics. These instances are built on the AWS Nitro System, which offloads CPU virtualization, storage, and networking functions to dedicated hardware and software to enhance the performance and security of your workloads. AWS Graviton4-based Amazon EC2 instances deliver the best performance and energy efficiency for a broad range of workloads running on Amazon EC2. AWS Graviton4-based R8g instances offer larger instance sizes with up to 3x more vCPU (up to 48xlarge) and memory (up to 1.5TB) than Graviton3-based R7g instances. These instances are up to 30% faster for web applications, 40% faster for databases, and 45% faster for large Java applications compared to AWS Graviton3-based R7g instances. R8g instances are available in 12 different instance sizes, including two bare metal sizes. They offer up to 50 Gbps enhanced networking bandwidth and up to 40 Gbps of bandwidth to the Amazon Elastic Block Store (Amazon EBS). To learn more, see Amazon EC2 R8g Instances. To explore how to migrate your workloads to Graviton-based instances, see AWS Graviton Fast Start program and Porting Advisor for Graviton. To get started, see the AWS Management Console.  

AWS has increased the account sharing limits for AWS Managed Microsoft AD directory sharing, allowing customers to share their directories with significantly more AWS accounts. The Standard Edition limit has increased from 5 to 25 accounts, while the Enterprise Edition limit has expanded from 125 to 500 accounts. These enhanced limits remove previous technical constraints and enable organizations to scale their directory infrastructure more effectively across their AWS environments.

The increased limits help enterprise customers consolidate their Active Directory infrastructure and reduce operational complexity by supporting larger AWS account footprints from a single managed directory. Organizations can now centralize authentication and management across hundreds of AWS accounts, which in turn helps eliminate the need for complex workarounds with multiple directory deployments.

This feature enhancement is available in all AWS Regions where AWS Managed Microsoft AD is currently supported.

To learn more about AWS Managed Microsoft AD directory sharing, see the AWS Directory Service documentation . For detailed information about directory sharing capabilities and setup, visit the AWS Managed Microsoft AD directory sharing page . For regional availability, see the AWS Region table.

 

​AWS has increased the account sharing limits for AWS Managed Microsoft AD directory sharing, allowing customers to share their directories with significantly more AWS accounts. The Standard Edition limit has increased from 5 to 25 accounts, while the Enterprise Edition limit has expanded from 125 to 500 accounts. These enhanced limits remove previous technical constraints and enable organizations to scale their directory infrastructure more effectively across their AWS environments. The increased limits help enterprise customers consolidate their Active Directory infrastructure and reduce operational complexity by supporting larger AWS account footprints from a single managed directory. Organizations can now centralize authentication and management across hundreds of AWS accounts, which in turn helps eliminate the need for complex workarounds with multiple directory deployments. This feature enhancement is available in all AWS Regions where AWS Managed Microsoft AD is currently supported. To learn more about AWS Managed Microsoft AD directory sharing, see the AWS Directory Service documentation . For detailed information about directory sharing capabilities and setup, visit the AWS Managed Microsoft AD directory sharing page . For regional availability, see the AWS Region table.  

Amazon VPC now allows customers to route inbound internet traffic destined for large pools of public IP addresses, to a single elastic network interface (ENI) within a VPC.

Prior to this enhancement, internet gateways only accepted traffic destined to public IP addresses that were associated with network interfaces in the VPC. There are limits to the number of IP addresses that can be associated with network interfaces. These limits depend on the instance type and can be found in our documentation. There are use cases in Telco, Internet of Things (IoT) and other industries that require customers to route inbound traffic destined for public IP pools, larger than the allowed limits, to a single network interface. Customers would earlier perform address translation to consolidate traffic for such large number of IP addresses. This enhancement removes the need to perform address translation on inbound internet connections for these Telco and IoT use cases. Customers can bring their own public IP pools (BYOIP documentation) and configure their VPC Internet Gateway to accept traffic belonging to this BYOIP pool and route it to a network interface. They can also use this feature with VPC Route Server and dynamically update their routes in events of failure. Refer to our public documentation for details on VPC Route Server.

This enhancement is now available across all AWS commercial, AWS China and GovCloud regions. To learn more about this feature, please refer to our documentation.

 

​Amazon VPC now allows customers to route inbound internet traffic destined for large pools of public IP addresses, to a single elastic network interface (ENI) within a VPC. Prior to this enhancement, internet gateways only accepted traffic destined to public IP addresses that were associated with network interfaces in the VPC. There are limits to the number of IP addresses that can be associated with network interfaces. These limits depend on the instance type and can be found in our documentation. There are use cases in Telco, Internet of Things (IoT) and other industries that require customers to route inbound traffic destined for public IP pools, larger than the allowed limits, to a single network interface. Customers would earlier perform address translation to consolidate traffic for such large number of IP addresses. This enhancement removes the need to perform address translation on inbound internet connections for these Telco and IoT use cases. Customers can bring their own public IP pools (BYOIP documentation) and configure their VPC Internet Gateway to accept traffic belonging to this BYOIP pool and route it to a network interface. They can also use this feature with VPC Route Server and dynamically update their routes in events of failure. Refer to our public documentation for details on VPC Route Server. This enhancement is now available across all AWS commercial, AWS China and GovCloud regions. To learn more about this feature, please refer to our documentation.  

Today, we’re announcing the integration of Amazon Neptune Analytics with Cognee, a leading agentic memory framework designed to help AI agents structure, retrieve, and reason over information. With this launch, customers can use Neptune as the graph store behind Cognee’s memory layer, enabling long-term memory and reasoning capabilities for agentic AI applications.

This integration allows Cognee users to store and query memory graphs at scale, unlocking advanced use cases where AI agents become more personalized and effective over time by learning from ongoing interactions. Neptune supports multi-hop graph reasoning and hybrid retrieval across graph, vector, and keyword modalities—helping Cognee deliver richer, more context-aware AI experiences.

Cognee enables a self-improving memory system that helps developers build cost-efficient, personalized generative AI applications. To learn more about the Neptune–Cognee integration, visit the User Guide and the sample notebook.

 

​Today, we’re announcing the integration of Amazon Neptune Analytics with Cognee, a leading agentic memory framework designed to help AI agents structure, retrieve, and reason over information. With this launch, customers can use Neptune as the graph store behind Cognee’s memory layer, enabling long-term memory and reasoning capabilities for agentic AI applications. This integration allows Cognee users to store and query memory graphs at scale, unlocking advanced use cases where AI agents become more personalized and effective over time by learning from ongoing interactions. Neptune supports multi-hop graph reasoning and hybrid retrieval across graph, vector, and keyword modalities—helping Cognee deliver richer, more context-aware AI experiences. Cognee enables a self-improving memory system that helps developers build cost-efficient, personalized generative AI applications. To learn more about the Neptune–Cognee integration, visit the User Guide and the sample notebook.  

Amazon Relational Database Service (Amazon RDS) for MariaDB now supports community MariaDB minor versions 11.4.8, 10.11.14 and 10.6.23. We recommend that you upgrade to the latest minor versions to fix known security vulnerabilities in prior versions of MariaDB, and to benefit from the bug fixes, performance improvements, and new functionality added by the MariaDB community.

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 MariaDB 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 MariaDB makes it straightforward to set up, operate, and scale MariaDB deployments in the cloud. Learn more about pricing details and regional availability at Amazon RDS for MariaDB. Create or update a fully managed Amazon RDS database in the Amazon RDS Management Console.

 

​Amazon Relational Database Service (Amazon RDS) for MariaDB now supports community MariaDB minor versions 11.4.8, 10.11.14 and 10.6.23. We recommend that you upgrade to the latest minor versions to fix known security vulnerabilities in prior versions of MariaDB, and to benefit from the bug fixes, performance improvements, and new functionality added by the MariaDB community. 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 MariaDB 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 MariaDB makes it straightforward to set up, operate, and scale MariaDB deployments in the cloud. Learn more about pricing details and regional availability at Amazon RDS for MariaDB. Create or update a fully managed Amazon RDS database in the Amazon RDS Management Console.  

Amazon Web Services (AWS) announces the availability of Amazon EC2 I7ie instances in the AWS Europe (Stockholm), Asia Pacific (Jakarta), and US West (N. California) regions. Designed for large storage I/O intensive workloads, these new instances are powered by 5th generation Intel Xeon Scalable processors with an all-core turbo frequency of 3.2 GHz, offering up to 40% better compute performance and 20% better price performance over previous generation I3en instances.

I7ie instances offer up to 120TB local NVMe storage density—the highest available in the cloud for storage optimized instances—and deliver up to twice as many vCPUs and memory compared to prior generation instances. Powered by 3rd generation AWS Nitro SSDs, these instances achieve up to 65% better real-time storage performance, up to 50% lower storage I/O latency, and 65% lower storage I/O latency variability compared to I3en instances. Additionally, torn write prevention feature support up to 16KB block sizes, enables customers to eliminate performance bottlenecks for database workloads.

I7ie instances are high-density storage-optimized instances, for workloads that demand rapid local storage with high random read/write performance and consistently low latency for accessing large data sets. These instances are offered in eleven different sizes including 2 metal sizes, providing flexibility for customers computational needs. They deliver up to 100 Gbps of network performance bandwidth, and 60 Gbps of dedicated bandwidth for Amazon Elastic Block Store (EBS), ensuring fast and efficient data transfer for applications.

To learn more, visit the I7ie instances page.

 

​Amazon Web Services (AWS) announces the availability of Amazon EC2 I7ie instances in the AWS Europe (Stockholm), Asia Pacific (Jakarta), and US West (N. California) regions. Designed for large storage I/O intensive workloads, these new instances are powered by 5th generation Intel Xeon Scalable processors with an all-core turbo frequency of 3.2 GHz, offering up to 40% better compute performance and 20% better price performance over previous generation I3en instances. I7ie instances offer up to 120TB local NVMe storage density—the highest available in the cloud for storage optimized instances—and deliver up to twice as many vCPUs and memory compared to prior generation instances. Powered by 3rd generation AWS Nitro SSDs, these instances achieve up to 65% better real-time storage performance, up to 50% lower storage I/O latency, and 65% lower storage I/O latency variability compared to I3en instances. Additionally, torn write prevention feature support up to 16KB block sizes, enables customers to eliminate performance bottlenecks for database workloads. I7ie instances are high-density storage-optimized instances, for workloads that demand rapid local storage with high random read/write performance and consistently low latency for accessing large data sets. These instances are offered in eleven different sizes including 2 metal sizes, providing flexibility for customers computational needs. They deliver up to 100 Gbps of network performance bandwidth, and 60 Gbps of dedicated bandwidth for Amazon Elastic Block Store (EBS), ensuring fast and efficient data transfer for applications. To learn more, visit the I7ie instances page.