AWS prescriptive-guidance documentation change
Summary
Updated DynamoDB operation names from snake_case to hyphenated format (e.g., 'get_item' to 'get-item')
Security assessment
Changes only correct command naming conventions to match AWS CLI syntax. The caching strategy logic (avoiding strong/transactional reads) remains unchanged with no security implications. No vulnerabilities or security features are discussed.
Diff
diff --git a/prescriptive-guidance/latest/dynamodb-elasticache-integration/cache-read.md b/prescriptive-guidance/latest/dynamodb-elasticache-integration/cache-read.md index 7c56e9558..dd94d8717 100644 --- a//prescriptive-guidance/latest/dynamodb-elasticache-integration/cache-read.md +++ b//prescriptive-guidance/latest/dynamodb-elasticache-integration/cache-read.md @@ -9 +9 @@ -The shim should cache only eventually consistent read calls made to DynamoDB. This includes `get_item`, `batch_get_item`, `query`, and `scan`. It should not cache strongly consistent reads calls or transactional read calls, because those calls inherently don't want to see a cached version of the data. +The shim should cache only eventually consistent read calls made to DynamoDB. This includes `get-item`, `batch-get-item`, `query`, and `scan`. It should not cache strongly consistent reads calls or transactional read calls, because those calls inherently don't want to see a cached version of the data. @@ -60 +60 @@ There's one more step. It's important for item caching to keep a mapping between -Operation | ElastiCache key calculation | ElastiCache value +Operation| ElastiCache key | ElastiCache value