AWS amazondynamodb documentation change
Summary
Updated references from 'S3 Glacier' to 'Amazon Glacier' in data archiving example
Security assessment
The change corrects service naming conventions but doesn't introduce new security information. The discussed TTL deletion pattern relates to data lifecycle management rather than security remediation.
Diff
diff --git a/amazondynamodb/latest/developerguide/data-modeling-blocks.md b/amazondynamodb/latest/developerguide/data-modeling-blocks.md index af03d1f53..bcd5ef71b 100644 --- a//amazondynamodb/latest/developerguide/data-modeling-blocks.md +++ b//amazondynamodb/latest/developerguide/data-modeling-blocks.md @@ -128 +128 @@ While TTL is an effective tool for deleting older data from DynamoDB, many use c -When a TTL delete is done by DynamoDB, it is still pushed into the DynamoDB Stream as a `Delete` event. When DynamoDB TTL is the one who performs the delete though, there is an attribute on the stream record of `principal:dynamodb`. Using a Lambda subscriber to the DynamoDB Stream, we can apply an event-filter for only the DynamoDB principal attribute and know that any records that match that filter are to be pushed to an archival store like S3 Glacier. +When a TTL delete is done by DynamoDB, it is still pushed into the DynamoDB Stream as a `Delete` event. When DynamoDB TTL is the one who performs the delete though, there is an attribute on the stream record of `principal:dynamodb`. Using a Lambda subscriber to the DynamoDB Stream, we can apply an event-filter for only the DynamoDB principal attribute and know that any records that match that filter are to be pushed to an archival store like Amazon Glacier. @@ -132 +132 @@ When a TTL delete is done by DynamoDB, it is still pushed into the DynamoDB Stre - * Once the low-latency reads of DynamoDB are no longer needed for the historical items, migrating them to a colder storage service like S3 Glacier can reduce storage costs significantly while meeting the data compliance needs of your use case + * Once the low-latency reads of DynamoDB are no longer needed for the historical items, migrating them to a colder storage service like Amazon Glacier can reduce storage costs significantly while meeting the data compliance needs of your use case