AWS amazondynamodb documentation change
Summary
Added guidance for analyzing custom latency percentiles, connection reuse strategies, and eventually consistent reads. Updated global tables explanation.
Security assessment
Changes focus on performance optimization and latency troubleshooting. While HTTPS connections are mentioned, this is standard practice rather than addressing a specific security vulnerability.
Diff
diff --git a/amazondynamodb/latest/developerguide/TroubleshootingLatency.md b/amazondynamodb/latest/developerguide/TroubleshootingLatency.md index 5d42b171e..7f56210ed 100644 --- a//amazondynamodb/latest/developerguide/TroubleshootingLatency.md +++ b//amazondynamodb/latest/developerguide/TroubleshootingLatency.md @@ -21,0 +22,4 @@ High p99 values with normal p50 values might indicate sporadic issues affecting +###### Note + +To analyze custom percentile values (such as p99.9), you can manually enter the desired percentile (e.g., p99.9) in the CloudWatch metric statistic field. This allows you to evaluate latency distributions beyond the default percentiles listed in the dropdown. + @@ -33,0 +38,4 @@ Consider one or more of the following strategies to reduce latency: + * **Reuse connections:** DynamoDB requests are made via an authenticated session which defaults to HTTPS. Initiating the connection takes time so the latency of the first request is higher than typical. Requests over an already initialized connection deliver DynamoDB's consistent low latency. For this reason, you may wish to make a "keep-alive" `GetItem` request every 30 seconds if no other requests are made, to avoid the latency of establishing a new connection. + + * **Use eventually consistent reads:** If your application doesn't require strongly consistent reads, consider using the default eventually consistent reads. Eventually consistent reads are lower cost and are also less likely to experience transient increases in latency. For more information, see [DynamoDB read consistency](./HowItWorks.ReadConsistency.html). + @@ -38 +46 @@ Consider one or more of the following strategies to reduce latency: - * **Reduce the distance between the client and DynamoDB endpoint:** If you have globally dispersed users, consider using [Global tables - multi-Region replication for DynamoDB](./GlobalTables.html). With global tables, you can specify the AWS Regions where you want the table to be available. Reading data from a local global tables replica can significantly reduce latency for your users. Also, consider using a DynamoDB [gateway endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-ddb.html) to keep your client traffic within your VPC. + * **Reduce the distance between the client and DynamoDB endpoint:** If you have globally dispersed users, consider using [Global tables - multi-Region replication for DynamoDB](./GlobalTables.html). With global tables, you can replicate your table to specified AWS Regions where you want the table to be available. When a request is initiated in a Region without a local replica, network latency contributes to the majority of the request processing time. Reading from a local replica can reduce latency for your users. @@ -42,4 +49,0 @@ Consider one or more of the following strategies to reduce latency: - * **Reuse connections:** DynamoDB requests are made via an authenticated session which defaults to HTTPS. Initiating the connection takes time so the latency of the first request is higher than typical. Requests over an already initialized connection deliver DynamoDB's consistent low latency. For this reason, you may wish to make a "keep-alive" `GetItem` request every 30 seconds if no other requests are made, to avoid the latency of establishing a new connection. - - * **Use eventually consistent reads:** If your application doesn't require strongly consistent reads, consider using the default eventually consistent reads. Eventually consistent reads are lower cost and are also less likely to experience transient increases in latency. For more information, see [DynamoDB read consistency](./HowItWorks.ReadConsistency.html). -