AWS cloud-map documentation change
Summary
Added JSON section headers and separators in IAM policy examples
Security assessment
Changes involve formatting improvements (adding JSON labels and separators) to existing IAM policy examples. No new security content or vulnerability fixes introduced.
Diff
diff --git a/cloud-map/latest/dg/security_iam_id-based-policy-examples.md b/cloud-map/latest/dg/security_iam_id-based-policy-examples.md index ebe9c3a78..755772f1f 100644 --- a//cloud-map/latest/dg/security_iam_id-based-policy-examples.md +++ b//cloud-map/latest/dg/security_iam_id-based-policy-examples.md @@ -66,0 +67,6 @@ To grant full access to the AWS Cloud Map console, you grant the permissions in +JSON + + +**** + + @@ -156,0 +164,6 @@ The following permissions policy grants the user read-only access to all AWS Clo +JSON + + +**** + + @@ -176,0 +191,6 @@ The following example shows a permissions policy that grants a user permission t +JSON + + +**** + + @@ -209,0 +231,6 @@ When adding a permissions policy to allow an IAM identity to create a AWS Cloud +JSON + + +**** + + @@ -230,0 +259,6 @@ The following permissions policy allows users to create all types of AWS Cloud M +JSON + + +**** + +