AWS res documentation change
Summary
Updated cross-account access policy instructions to remove region from role ARN and use {RES_ENVIRONMENT_NAME} placeholder
Security assessment
This change updates documentation formatting and placeholder usage but doesn't indicate any security issue or vulnerability. It appears to be a documentation improvement for clarity.
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 ba511d9ab..b221cbf36 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 @@ -76 +76 @@ JSON - 3. Paste the following JSON policy (replace ``111122223333`` with the actual account ID of Account A, ``ENVIRONMENT_NAME`` with the environment name of the RES deployment, and ``us-east-1`` with the AWS region RES is deployed to): + 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: @@ -90 +90 @@ JSON - "AWS": "arn:aws:iam::111122223333:role/<ENVIRONMENT_NAME>-custom-credential-broker-lambda-role-us-east-1" + "AWS": "arn:aws:iam::111122223333:role/<ENVIRONMENT_NAME>-vdc-custom-credential-broker-lambda-role"