AWS res documentation change
Summary
Updated placeholder values in cross-account access policies including bucket name and account ID examples
Security assessment
Standard documentation improvements for policy examples without security implications
Diff
diff --git a/res/latest/ug/S3-buckets-cross-account-access.md b/res/latest/ug/S3-buckets-cross-account-access.md index d3636d5a1..911adfe9c 100644 --- a//res/latest/ug/S3-buckets-cross-account-access.md +++ b//res/latest/ug/S3-buckets-cross-account-access.md @@ -25 +25 @@ RES has the ability to mount buckets from other AWS accounts, provided these buc - 3. Paste the following JSON policy (replace ``<BUCKET-NAME>`` with the name of the S3 bucket located in Account B): + 3. Paste the following JSON policy (replace ``amzn-s3-demo-bucket`` with the name of the S3 bucket located in Account B): @@ -76 +76 @@ JSON - 3. Paste the following JSON policy (replace ``<ACCOUNT_ID>`` with the actual account ID of Account A, and ``<ENVIRONMENT_NAME>`` with the environment name of the RES deployment: + 3. Paste the following JSON policy (replace ``111122223333`` with the actual account ID of Account A, and ``{RES_ENVIRONMENT_NAME}`` with the environment name of the RES deployment: @@ -151 +151 @@ JSON - 2. Add the following policy to grant the IAM role from Account A access to the bucket (replace `<AccountA_ID>` with the actual account ID of Account A and `<BUCKET-NAME>` with the name of the S3 bucket): + 2. Add the following policy to grant the IAM role from Account A access to the bucket (replace `111122223333` with the actual account ID of Account A and `` with the name of the S3 bucket):