AWS amazondynamodb: Fix broken documentation links and clarify quota language
Summary
Corrected broken URLs by removing double slashes and rephrased quota explanation for clarity.
Security assessment
The evidence shows URL syntax fixes and minor grammatical rephrasing. No security implications are present; changes are purely documentation improvements.
Evidence
+ * **Account limit throttling events:** [`ReadAccountLimitThrottleEvents`](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html#ReadAccountLimitThrottleEvents) and [`WriteAccountLimitThrottleEvents`](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html#WriteAccountLimitThrottleEvents) track when requests are throttled due to account-level limits. [`ReadThrottleEvents`](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html#ReadThrottleEvents) and [`WriteThrottleEvents`](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html#WriteThrottleEvents) track when any read or write requests exceed the provisioned capacity.
Diff
diff --git a/amazondynamodb/latest/developerguide/throttling-account-limit-exceeded-mitigation.md b/amazondynamodb/latest/developerguide/throttling-account-limit-exceeded-mitigation.md index 884b0b09a..c1e1cfc96 100644 --- a//amazondynamodb/latest/developerguide/throttling-account-limit-exceeded-mitigation.md +++ b//amazondynamodb/latest/developerguide/throttling-account-limit-exceeded-mitigation.md @@ -115 +115 @@ Monitor these key metrics to diagnose account limit throttling: - * **Account limit throttling events:** [`ReadAccountLimitThrottleEvents`](https://docs.aws.amazon.com//amazondynamodb/latest/developerguide/metrics-dimensions.html#ReadAccountLimitThrottleEvents) and [`WriteAccountLimitThrottleEvents`](https://docs.aws.amazon.com//amazondynamodb/latest/developerguide/metrics-dimensions.html#WriteAccountLimitThrottleEvents) track when requests are throttled due to account-level limits. [`ReadThrottleEvents`](https://docs.aws.amazon.com//amazondynamodb/latest/developerguide/metrics-dimensions.html#ReadThrottleEvents) and [`WriteThrottleEvents`](https://docs.aws.amazon.com//amazondynamodb/latest/developerguide/metrics-dimensions.html#WriteThrottleEvents) track when any read or write requests exceed the provisioned capacity. + * **Account limit throttling events:** [`ReadAccountLimitThrottleEvents`](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html#ReadAccountLimitThrottleEvents) and [`WriteAccountLimitThrottleEvents`](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html#WriteAccountLimitThrottleEvents) track when requests are throttled due to account-level limits. [`ReadThrottleEvents`](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html#ReadThrottleEvents) and [`WriteThrottleEvents`](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/metrics-dimensions.html#WriteThrottleEvents) track when any read or write requests exceed the provisioned capacity. @@ -128 +128 @@ Monitor these key metrics to diagnose account limit throttling: -If your applications need to operate beyond the current per-table throughput limits, you should submit a quota increase request using the procedure below. Each DynamoDB table in your AWS account (together with all its associated GSIs) is subject to these throughput quotas within a specific Region. These quotas represent the maximum read or write capacity that any individual table and its GSIs can collectively consume, and they apply independently to each table rather than as an aggregate across all tables in your account. +If your applications need to operate beyond the current per-table throughput limits, you should submit a quota increase request using the procedure below. Each DynamoDB table in your AWS account (together with all its associated GSIs) is subject to these throughput quotas within a specific Region. These quotas represent the maximum read or write capacity that any individual table and its GSIs can collectively consume. They apply independently to each table rather than as an aggregate across all tables in your account. @@ -167 +167 @@ Optimize your Global Secondary Index (GSI) projections and design to reduce capa -If your queries only need to access a few attributes, projecting only those attributes reduces the amount of data written to the GSI when base table items change. For details on projection types, see [Projections for Global Secondary Indexes](https://docs.aws.amazon.com//amazondynamodb/latest/developerguide/GSI.html#GSI.Projections). +If your queries only need to access a few attributes, projecting only those attributes reduces the amount of data written to the GSI when base table items change. For details on projection types, see [Projections for Global Secondary Indexes](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GSI.html#GSI.Projections). @@ -193 +193 @@ Sparse GSIs contain only items that have the indexed attribute, rather than all -For more information about implementing these strategies, see [Best Practices for Using Secondary Indexes in DynamoDB](https://docs.aws.amazon.com//amazondynamodb/latest/developerguide/bp-indexes.html). +For more information about implementing these strategies, see [Best Practices for Using Secondary Indexes in DynamoDB](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-indexes.html).