AWS proton documentation change
Summary
Replaced 'AWS CloudFormation' with 'CloudFormation' in section titles and service role descriptions
Security assessment
Cosmetic update to service naming conventions. No modifications to security permissions or policy guidance.
Diff
diff --git a/proton/latest/userguide/security_iam_service-role-policy-examples.md b/proton/latest/userguide/security_iam_service-role-policy-examples.md index a5c9f58fb..972c42ed9 100644 --- a//proton/latest/userguide/security_iam_service-role-policy-examples.md +++ b//proton/latest/userguide/security_iam_service-role-policy-examples.md @@ -17 +17 @@ You create the service role and its permission policy with the IAM service. For -## AWS Proton service role for provisioning using AWS CloudFormation +## AWS Proton service role for provisioning using CloudFormation @@ -260 +260 @@ To provision service pipelines, AWS Proton needs permissions to make API calls t -When you use the AWS Proton console to update account settings and choose to create a new role for either the AWS CloudFormation or the CodeBuild service roles, the policies that AWS Proton adds to the service roles it creates for you are the same as the policies described in the previous sections, AWS-managed provisioning role and CodeBuild provisioning role. When scoping down permission on this policy, keep in mind that AWS Proton fails on `Access Denied` errors. +When you use the AWS Proton console to update account settings and choose to create a new role for either the CloudFormation or the CodeBuild service roles, the policies that AWS Proton adds to the service roles it creates for you are the same as the policies described in the previous sections, AWS-managed provisioning role and CodeBuild provisioning role. When scoping down permission on this policy, keep in mind that AWS Proton fails on `Access Denied` errors.