AWS amazondynamodb documentation change
Summary
Restructured Contributor Insights documentation to clarify throttled keys mode vs. accessed+throttled mode. Added cost-effectiveness details, reordered sections, and emphasized throttling-focused monitoring strategies.
Security assessment
Changes focus on operational monitoring improvements and cost optimization for performance analysis. No security vulnerabilities or security features are mentioned - updates relate to throttling visibility and monitoring efficiency rather than access control, encryption, or security policies.
Diff
diff --git a/amazondynamodb/latest/developerguide/contributorinsights_HowItWorks.md b/amazondynamodb/latest/developerguide/contributorinsights_HowItWorks.md index aa0c520b8..f7d72f4bd 100644 --- a//amazondynamodb/latest/developerguide/contributorinsights_HowItWorks.md +++ b//amazondynamodb/latest/developerguide/contributorinsights_HowItWorks.md @@ -36,3 +36 @@ CloudWatch Contributor Insights for DynamoDB offers two distinct modes to meet d -### Accessed and throttled keys mode - -This mode provides comprehensive monitoring of both accessed and throttled items. In this mode, DynamoDB tracks: +### Throttled keys mode @@ -40 +38 @@ This mode provides comprehensive monitoring of both accessed and throttled items - * **Most accessed items** — Items that consume the most read and write capacity +This mode focuses exclusively on throttled requests by only processing events when throttling occurs. It delivers insights about performance issues without the overhead of tracking all access patterns. In this mode, DynamoDB tracks only the: @@ -47 +45 @@ This mode provides comprehensive monitoring of both accessed and throttled items -This mode is ideal when you need complete visibility into your table's access patterns and want to understand both high-traffic items and throttling issues. +This mode is ideal when: @@ -49 +47 @@ This mode is ideal when you need complete visibility into your table's access pa -### Throttled keys mode + * Your primary concern is identifying and resolving throttling problems @@ -51 +49 @@ This mode is ideal when you need complete visibility into your table's access pa -This mode focuses exclusively on throttled requests by only processing events when throttling occurs. It delivers critical insights about performance issues. In this mode, DynamoDB tracks only: + * You want to keep Contributor Insights enabled continuously for real-time throttling detection @@ -53 +51 @@ This mode focuses exclusively on throttled requests by only processing events wh - * **Most throttled items** — Items that experience the most throttling events + * You want a cost-optimized approach to monitor throttling issues @@ -58 +56 @@ This mode focuses exclusively on throttled requests by only processing events wh -This mode is ideal when: +###### Note @@ -60 +58 @@ This mode is ideal when: - * Your primary concern is identifying and resolving throttling problems + _Throttled keys mode_ processes events only when throttling occurs, making it cost-effective for continuous monitoring. This targeted approach allows you to leave the feature enabled permanently with minimal cost impact, while still providing immediate visibility into throttling issues as they happen. @@ -62 +60 @@ This mode is ideal when: - * You want to keep Contributor Insights enabled continuously for real-time throttling detection +If your table experiences no throttling, you won't see any data in the Contributor Insights graphs, which indicates healthy performance. When throttling is detected, the generated graphs help you identify specific access patterns causing performance issues. This information can help you implement strategies to address non-uniform access patterns. @@ -63,0 +62 @@ This mode is ideal when: +For comprehensive monitoring strategies, you can integrate these throttling insights with other CloudWatch metrics to create unified dashboards that correlate throttling events with overall table performance. @@ -64,0 +64 @@ This mode is ideal when: +### Accessed and throttled keys mode @@ -65,0 +66 @@ This mode is ideal when: +This mode provides comprehensive monitoring of both accessed and throttled items. In this mode, DynamoDB tracks the: @@ -67 +68 @@ This mode is ideal when: -###### Note + * **Most accessed items** — Items that consume the most read and write capacity @@ -69 +70,6 @@ This mode is ideal when: -Throttled keys mode only generates graphs and metrics when throttling actually occurs. If your table experiences no throttling, you won't see any data in the Contributor Insights graphs, which indicates healthy performance. + * **Most throttled items** — Items that experience the most throttling events + + + + +This mode is ideal when you need complete visibility into your table's access patterns and want to understand both high-traffic items and throttling issues.