AWS AWSEC2 documentation change
Summary
Removed JSON formatting examples and section dividers from multiple IAM policy examples
Security assessment
Purely structural changes to documentation formatting. No security policy alterations.
Diff
diff --git a/AWSEC2/latest/UserGuide/iam-policies-ec2-console.md b/AWSEC2/latest/UserGuide/iam-policies-ec2-console.md index 4d99fd24e..23a2b8c73 100644 --- a//AWSEC2/latest/UserGuide/iam-policies-ec2-console.md +++ b//AWSEC2/latest/UserGuide/iam-policies-ec2-console.md @@ -40,6 +39,0 @@ Alternatively, you can provide read-only access to a subset of resources. To do -JSON - - -**** - - @@ -71,6 +63,0 @@ The following policy allows users to view instances in the Amazon EC2 console, a -JSON - - -**** - - @@ -122,6 +107,0 @@ To complete a launch successfully, users must be given permission to use the `ec -JSON - - -**** - - @@ -184,6 +162,0 @@ The first statement grants users permission to view the options in the launch in -JSON - - -**** - - @@ -253,6 +224,0 @@ The first statement grants users the permission to view Systems Manager paramete -JSON - - -**** - - @@ -288,6 +252,0 @@ In the first statement, the `ec2:DescribeTags` action allows users to view tags -JSON - - -**** - - @@ -374,6 +331,0 @@ The following policy grants users permission to use the **Create Security Group* -JSON - - -**** - - @@ -431,6 +381,0 @@ The following policy allows users to view, allocate, and associate Elastic IP ad -JSON - - -**** - - @@ -461,6 +404,0 @@ This policy allows users to view all the Reserved Instances, as well as On-Deman -JSON - - -**** - -