AWS AWSEC2 documentation change
Summary
Added JSON code block placeholders in multiple IAM policy examples
Security assessment
Changes only add structural formatting markers (JSON/****) without modifying actual policy content or security context. No evidence of addressing vulnerabilities or changing security guidance.
Diff
diff --git a/AWSEC2/latest/UserGuide/iam-policies-ec2-console.md b/AWSEC2/latest/UserGuide/iam-policies-ec2-console.md index fd1ce7d1c..d87a2d35d 100644 --- a//AWSEC2/latest/UserGuide/iam-policies-ec2-console.md +++ b//AWSEC2/latest/UserGuide/iam-policies-ec2-console.md @@ -39,0 +40,6 @@ Alternatively, you can provide read-only access to a subset of resources. To do +JSON + + +**** + + @@ -63,0 +71,6 @@ The following policy allows users to view instances in the Amazon EC2 console, a +JSON + + +**** + + @@ -107,0 +122,6 @@ To complete a launch successfully, users must be given permission to use the `ec +JSON + + +**** + + @@ -162,0 +184,6 @@ The first statement grants users permission to view the options in the launch in +JSON + + +**** + + @@ -224,0 +253,6 @@ The first statement grants users the permission to view Systems Manager paramete +JSON + + +**** + + @@ -252,0 +288,6 @@ In the first statement, the `ec2:DescribeTags` action allows users to view tags +JSON + + +**** + + @@ -331,0 +374,6 @@ The following policy grants users permission to use the **Create Security Group* +JSON + + +**** + + @@ -381,0 +431,6 @@ The following policy allows users to view, allocate, and associate Elastic IP ad +JSON + + +**** + + @@ -404,0 +461,6 @@ This policy allows users to view all the Reserved Instances, as well as On-Deman +JSON + + +**** + +