AWS prescriptive-guidance documentation change
Summary
Removed DynamoDB IAM policy example with attribute-based access controls
Security assessment
Policy removal eliminates documentation of security controls but doesn't indicate vulnerability remediation
Diff
diff --git a/prescriptive-guidance/latest/privacy-reference-architecture/grant-access-dynamodb-attributes.md b/prescriptive-guidance/latest/privacy-reference-architecture/grant-access-dynamodb-attributes.md index 6ae5ae67c..f9ffee7a8 100644 --- a//prescriptive-guidance/latest/privacy-reference-architecture/grant-access-dynamodb-attributes.md +++ b//prescriptive-guidance/latest/privacy-reference-architecture/grant-access-dynamodb-attributes.md @@ -13,33 +12,0 @@ As your organization discusses strategies to physically and logically separate p - { - "Version":"2012-10-17", - "Statement":[ - { - "Effect":"Allow", - "Action":[ - "dynamodb:GetItem", - "dynamodb:BatchGetItem", - "dynamodb:Query", - "dynamodb:Scan", - "dynamodb:TransactGetItems" - ], - "Resource":[ - "arn:aws:dynamodb:us-west-2:123456789012:dynamodb:table/Users" - ], - "Condition":{ - "ForAllValues:StringEquals":{ - "dynamodb:Attributes":[ - "UserID", - "SignUpTime", - "LastLoggedIn" - ] - }, - "StringEquals":{ - "dynanamodb:Select":[ - "SPECIFIC_ATTRIBUTES" - ] - } - } - } - ] - } -