AWS payment-cryptography documentation change
Summary
Added JSON formatting, corrected ListTagsForResource action name, and updated policy syntax
Security assessment
Ensures policy examples use valid action names and syntax for tag management. Improves documentation accuracy but does not resolve a specific security issue.
Diff
diff --git a/payment-cryptography/latest/userguide/tag-permissions.md b/payment-cryptography/latest/userguide/tag-permissions.md index 18d9f9b7b..8991cdd80 100644 --- a//payment-cryptography/latest/userguide/tag-permissions.md +++ b//payment-cryptography/latest/userguide/tag-permissions.md @@ -35,0 +36,6 @@ You can provide tagging permissions in a key policy or IAM policy. For example, +JSON + + +**** + + @@ -49 +55 @@ You can provide tagging permissions in a key policy or IAM policy. For example, - "Sid": "Allow all tagging permissions", + "Sid": "AllowAllTaggingPermissions", @@ -65 +71,2 @@ You can provide tagging permissions in a key policy or IAM policy. For example, - "Principal": {"AWS": [ + "Principal": { + "AWS": [ @@ -68,2 +75,3 @@ You can provide tagging permissions in a key policy or IAM policy. For example, - ]}, - "Action": "payment-cryptography:ListResourceTags", + ] + }, + "Action": "payment-cryptography:ListTagsForResource", @@ -78,0 +88,6 @@ For example, the following IAM policy allows the principals to create keys. It a +JSON + + +**** + + @@ -120,0 +137,6 @@ Because `TagResource` and `UntagResource` requests can include multiple tags, yo +JSON + + +**** + + @@ -134 +156 @@ Because `TagResource` and `UntagResource` requests can include multiple tags, yo - "Action": "payment-cryptography:ListResourceTags", + "Action": "payment-cryptography:ListTagsForResource",