AWS kms documentation change

Service: kms · 2025-07-25 · Documentation low

File: kms/latest/developerguide/cmks-in-iam-policies.md

Summary

Added JSON formatting markers, updated example key ARN, and structural improvements

Security assessment

Example key ARN change appears to be placeholder standardization rather than security-related. Formatting changes don't impact security content

Diff

diff --git a/kms/latest/developerguide/cmks-in-iam-policies.md b/kms/latest/developerguide/cmks-in-iam-policies.md
index 63524c604..0f57a4e08 100644
--- a//kms/latest/developerguide/cmks-in-iam-policies.md
+++ b//kms/latest/developerguide/cmks-in-iam-policies.md
@@ -29,0 +30,6 @@ For example, the following IAM policy statement allows the principal to call the
+JSON
+    
+
+****
+    
+    
@@ -42 +48 @@ For example, the following IAM policy statement allows the principal to call the
-          "arn:aws:kms:us-west-2:111122223333:key/0987dcba-09fe-87dc-65ba-ab0987654321"
+         "arn:aws:kms:us-west-2:111122223333:key/01234abcd-12ab-34cd-56ef-1234567890ab"
@@ -48,0 +56,6 @@ To apply the permission to all KMS keys in a particular trusted AWS account, you
+JSON
+    
+
+****
+    
+    
@@ -69,0 +84,6 @@ For example, the following policy statement uses a `Deny` effect to prohibit the
+JSON
+    
+
+****
+    
+    
@@ -86,0 +108,6 @@ The following policy statement uses a wildcard character alone to represent all
+JSON
+    
+
+****
+    
+