AWS res documentation change
Summary
Updated policy examples with specific values ('amzn-s3-demo-bucket', '111122223333', 'res-env-name', 'us-east-1') for cross-account access configuration
Security assessment
Replaces generic placeholders with concrete examples to improve documentation usability. No security vulnerabilities addressed or new security features documented - maintains existing cross-account access controls.
Diff
diff --git a/res/archive/release-minus-3/ug/S3-buckets-cross-account-access.md b/res/archive/release-minus-3/ug/S3-buckets-cross-account-access.md index 9c248d033..70ee38c5d 100644 --- a//res/archive/release-minus-3/ug/S3-buckets-cross-account-access.md +++ b//res/archive/release-minus-3/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, ``<ENVIRONMENT_NAME>`` with the environment name of the RES deployment, and ``<REGION>`` with the AWS region RES is deployed to): + 3. Paste the following JSON policy (replace ``111122223333`` with the actual account ID of Account A, ``res-env-name`` with the environment name of the RES deployment, and ``us-east-1`` with the AWS region RES is deployed to): @@ -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 `amzn-s3-demo-bucket` with the name of the S3 bucket):