AWS Security ChangesHomeSearch

AWS res documentation change

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

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

Summary

Replaced policy template placeholders with concrete values ('amzn-s3-demo-bucket', '111122223333', '{RES_ENVIRONMENT_NAME}', 'us-east-1') in cross-account access documentation

Security assessment

Updates provide specific example values for policy templates but do not modify security recommendations or address vulnerabilities. Enhances documentation clarity without changing security posture.

Diff

diff --git a/res/archive/release-minus-2/ug/S3-buckets-cross-account-access.md b/res/archive/release-minus-2/ug/S3-buckets-cross-account-access.md
index 2841e86c6..b830d8355 100644
--- a//res/archive/release-minus-2/ug/S3-buckets-cross-account-access.md
+++ b//res/archive/release-minus-2/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_ENVIRONMENT_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):