AWS managedservices documentation change
Summary
Changed 'AWS CloudFormation' to 'CloudFormation' for terminology consistency
Security assessment
The change is purely terminological, removing the 'AWS' prefix from CloudFormation references without altering security implications of IAM role permissions or policies.
Diff
diff --git a/managedservices/latest/accelerate-guide/acc-access-customer.md b/managedservices/latest/accelerate-guide/acc-access-customer.md index 2664f0a95..7bd369c79 100644 --- a//managedservices/latest/accelerate-guide/acc-access-customer.md +++ b//managedservices/latest/accelerate-guide/acc-access-customer.md @@ -7 +7 @@ -To allow your users to read and configure AMS Accelerate capabilities, like accessing the AMS Console or configuring backups, you must grant explicit permissions to their IAM roles to perform those actions. The following AWS CloudFormation template contains the policies required to read and configure services associated with AMS so you can assign them to your IAM roles. They are designed to closely align with common job responsibilities in the IT industry, where Administrator or Read-Only permissions are required; however, if you need to grant different permissions to users, you can edit the policy to include or exclude specific permissions. You can also create your own custom policy. +To allow your users to read and configure AMS Accelerate capabilities, like accessing the AMS Console or configuring backups, you must grant explicit permissions to their IAM roles to perform those actions. The following CloudFormation template contains the policies required to read and configure services associated with AMS so you can assign them to your IAM roles. They are designed to closely align with common job responsibilities in the IT industry, where Administrator or Read-Only permissions are required; however, if you need to grant different permissions to users, you can edit the policy to include or exclude specific permissions. You can also create your own custom policy.