AWS neptune documentation change
Summary
Added JSON code block formatting and section dividers (****) to IAM policy examples
Security assessment
Changes are purely formatting improvements for existing IAM policy examples without altering security content or addressing vulnerabilities
Diff
diff --git a/neptune/latest/userguide/iam-admin-policy-examples.md b/neptune/latest/userguide/iam-admin-policy-examples.md index 3f91b3fa9..85fc20e7a 100644 --- a//neptune/latest/userguide/iam-admin-policy-examples.md +++ b//neptune/latest/userguide/iam-admin-policy-examples.md @@ -16,0 +17,6 @@ The following is an example policy that prevents an IAM user from deleting a spe +JSON + + +**** + + @@ -33,0 +41,6 @@ The following is an example policy that allows an IAM user to create DB instance +JSON + + +**** + + @@ -50,0 +65,6 @@ The following is an example policy that allows an IAM user to create DB instance +JSON + + +**** + + @@ -91,0 +113,6 @@ The policy below allows use of the `ModifyDBInstance`, `CreateDBInstance` or `De +JSON + + +**** + + @@ -120,0 +149,6 @@ This policy uses a `Condition` key to allow a tag that has the key `env` and a v +JSON + + +**** + + @@ -149,0 +185,6 @@ The following policy is similar to the first example above, but uses the `aws:Re +JSON + + +**** + +