AWS evs documentation change
Summary
Fixed JSON policy syntax by moving &TCX5-2025-waiver annotation after commas in multiple policy examples
Security assessment
The changes correct JSON formatting by properly placing annotations outside the policy syntax. While related to security policies, this is a documentation formatting fix rather than a security vulnerability patch or feature addition.
Diff
diff --git a/evs/latest/userguide/security-iam-id-based-policy-examples.md b/evs/latest/userguide/security-iam-id-based-policy-examples.md index 4fd8a9ab4..cd1309395 100644 --- a//evs/latest/userguide/security-iam-id-based-policy-examples.md +++ b//evs/latest/userguide/security-iam-id-based-policy-examples.md @@ -53 +53 @@ To ensure that your IAM principals can still use the Amazon EVS console, create - "Version": "2012-10-17"&TCX5-2025-waiver;, + "Version": "2012-10-17",&TCX5-2025-waiver; @@ -86 +86 @@ This example shows how you might create a policy that allows IAM users to view t - "Version": "2012-10-17"&TCX5-2025-waiver;, + "Version": "2012-10-17",&TCX5-2025-waiver; @@ -126 +126 @@ You can replace the AWS Region with the AWS Region that you want to create an en - "Version": "2012-10-17"&TCX5-2025-waiver;, + "Version": "2012-10-17",&TCX5-2025-waiver; @@ -496 +496 @@ This example policy includes the minimum permissions required for an administrat - "Version": "2012-10-17"&TCX5-2025-waiver;, + "Version": "2012-10-17",&TCX5-2025-waiver;