AWS res documentation change

Service: res · 2025-08-19 · Documentation low

File: res/archive/release-minus-1/ug/S3-buckets-cross-account-access.md

Summary

Updated example values in cross-account access policy templates (replaced placeholders with concrete values like 'amzn-s3-demo-bucket', '111122223333', 'res-env-name', and 'us-east-1')

Security assessment

Changes only replace placeholder values with specific examples for clarity. No evidence of addressing a security vulnerability or weakness. The modifications improve documentation accuracy but do not introduce new security controls or address explicit security flaws.

Diff

diff --git a/res/archive/release-minus-1/ug/S3-buckets-cross-account-access.md b/res/archive/release-minus-1/ug/S3-buckets-cross-account-access.md
index 2d6eac6f1..f1b8ae37d 100644
--- a//res/archive/release-minus-1/ug/S3-buckets-cross-account-access.md
+++ b//res/archive/release-minus-1/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 ```` 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):