AWS neptune documentation change
Summary
Added JSON code blocks and section dividers to data access policy examples
Security assessment
Formatting enhancements to existing IAM data access policies without altering security guidance
Diff
diff --git a/neptune/latest/userguide/iam-data-access-examples.md b/neptune/latest/userguide/iam-data-access-examples.md index 162cb73b9..bd5132b7d 100644 --- a//neptune/latest/userguide/iam-data-access-examples.md +++ b//neptune/latest/userguide/iam-data-access-examples.md @@ -14,0 +15,6 @@ The following example policy allows an IAM user to connect to a Neptune DB clust +JSON + + +**** + + @@ -32,0 +40,6 @@ The following policy grants permission for full read-only access to data in a Ne +JSON + + +**** + + @@ -53,0 +68,6 @@ The default IAM action is to deny access to a DB cluster unless an `Allow` _Effe +JSON + + +**** + + @@ -69,0 +91,6 @@ The following policy only grants permission to read from a Neptune DB cluster us +JSON + + +**** + + @@ -85,0 +114,6 @@ The following policy uses the `neptune-db:QueryLanguage` condition key to grant +JSON + + +**** + + @@ -110,0 +146,6 @@ The following policy grants full access to Neptune graph operations except for t +JSON + + +**** + + @@ -142,0 +185,6 @@ This policy grants access to the Neptune ML model-management features: +JSON + + +**** + + @@ -175,0 +225,6 @@ The following policy grants full access to Neptune graph query operations, but n +JSON + + +**** + + @@ -198,0 +255,6 @@ The following policy grants full access to Neptune graph query operations using +JSON + + +**** + + @@ -228,0 +292,6 @@ The following policy grants full access to a Neptune DB cluster except for using +JSON + + +**** + +