AWS proton documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' for consistency in terminology
Security assessment
The changes are purely terminological, replacing 'AWS CloudFormation' with 'CloudFormation' for consistency. There is no indication of addressing security vulnerabilities or modifying security-related content.
Diff
diff --git a/proton/latest/userguide/ag-works-prov-methods.md b/proton/latest/userguide/ag-works-prov-methods.md index 09cfdab7e..eb9a51c3f 100644 --- a//proton/latest/userguide/ag-works-prov-methods.md +++ b//proton/latest/userguide/ag-works-prov-methods.md @@ -13 +13 @@ AWS Proton can provision infrastructure in one of several ways: - * AWS-managed provisioning – AWS Proton calls the provisioning engine on your behalf. This method supports only AWS CloudFormation template bundles. For more information, see [AWS CloudFormation IaC files](./ag-infrastructure-tmp-files-cloudformation.html). + * AWS-managed provisioning – AWS Proton calls the provisioning engine on your behalf. This method supports only AWS CloudFormation template bundles. For more information, see [CloudFormation IaC files](./ag-infrastructure-tmp-files-cloudformation.html). @@ -48 +48 @@ When an environment or a service uses AWS-managed provisioning, infrastructure i - 2. AWS Proton renders a complete AWS CloudFormation template for provisioning the resource. + 2. AWS Proton renders a complete CloudFormation template for provisioning the resource. @@ -50 +50 @@ When an environment or a service uses AWS-managed provisioning, infrastructure i - 3. AWS Proton calls AWS CloudFormation to start provisioning using the rendered template. + 3. AWS Proton calls CloudFormation to start provisioning using the rendered template. @@ -52 +52 @@ When an environment or a service uses AWS-managed provisioning, infrastructure i - 4. AWS Proton continuously monitors the AWS CloudFormation deployment. + 4. AWS Proton continuously monitors the CloudFormation deployment. @@ -65 +65 @@ The following diagram shows that AWS Proton takes care of most of these steps di - * _Infrastructure provisioning role_ – When an environment or any of the service instances running in it might use AWS-managed provisioning, an administrator needs to configure an IAM role (either directly or as part of an AWS Proton environment account connection). AWS Proton uses this role to provision the infrastructure of these AWS-managed provisioning resources. The role should have permissions to use AWS CloudFormation to create all the resources that the templates of these resources include. + * _Infrastructure provisioning role_ – When an environment or any of the service instances running in it might use AWS-managed provisioning, an administrator needs to configure an IAM role (either directly or as part of an AWS Proton environment account connection). AWS Proton uses this role to provision the infrastructure of these AWS-managed provisioning resources. The role should have permissions to use CloudFormation to create all the resources that the templates of these resources include. @@ -71 +71 @@ For more information, see [IAM Roles](./ag-environment-roles.html) and [AWS Prot - * _Service with pipeline_ – A service template that uses AWS-managed provisioning may include a pipeline definition written in the AWS CloudFormation YAML schema. AWS Proton also creates the pipeline by calling AWS CloudFormation. The role that AWS Proton uses to create a pipeline is separate from the role for each individual environment. This role is provided to AWS Proton separately, only once at the AWS account level, and it's used to provision and manage all AWS-managed pipelines. This role should have permissions to create pipelines and other resources that your pipelines need. + * _Service with pipeline_ – A service template that uses AWS-managed provisioning may include a pipeline definition written in the CloudFormation YAML schema. AWS Proton also creates the pipeline by calling CloudFormation. The role that AWS Proton uses to create a pipeline is separate from the role for each individual environment. This role is provided to AWS Proton separately, only once at the AWS account level, and it's used to provision and manage all AWS-managed pipelines. This role should have permissions to create pipelines and other resources that your pipelines need.