AWS res documentation change
Summary
Replaced 'AWS CloudFormation' with 'CloudFormation' in permission boundaries context
Security assessment
Terminology update in existing security documentation. No modification to permission boundary implementation or security requirements.
Diff
diff --git a/res/archive/release-minus-1/ug/permission-boundaries.md b/res/archive/release-minus-1/ug/permission-boundaries.md index 8789c3959..1bce6b864 100644 --- a//res/archive/release-minus-1/ug/permission-boundaries.md +++ b//res/archive/release-minus-1/ug/permission-boundaries.md @@ -7 +7 @@ -As of 2024.04, you can optionally modify roles created by RES by attaching custom permission boundaries. A custom permission boundary may be defined as part of the RES AWS CloudFormation installation by supplying the permission boundary’s ARN as part of the IAMPermissionBoundary parameter. No permission boundary is set on any RES roles if this parameter is left empty. Below is the list of actions that RES roles require to operate. Make sure that any permission boundary that you plan to use explicitly allows for the following actions: +As of 2024.04, you can optionally modify roles created by RES by attaching custom permission boundaries. A custom permission boundary may be defined as part of the RES CloudFormation installation by supplying the permission boundary’s ARN as part of the IAMPermissionBoundary parameter. No permission boundary is set on any RES roles if this parameter is left empty. Below is the list of actions that RES roles require to operate. Make sure that any permission boundary that you plan to use explicitly allows for the following actions: