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
Categories: general:products/aws-govcloud-us,general:products/amazon-dynamodb,marketing:marchitecture/databases
Source: Amazon Web Services
Latest Posts
- (Updated) Microsoft Copilot Analytics: Data export public preview for Copilot metrics in the Copilot dashboard [MC1173208]
- LTS upgrade testing
- Amazon SageMaker HyperPod now supports continuous provisioning for Slurm-orchestrated clusters
- Amazon EC2 I7ie instances now available in additional AWS regions
