AWS whitepapers documentation change
Summary
Updated terminology from 'AWS CloudFormation' to 'CloudFormation' throughout the document for consistency, while maintaining all technical content and references unchanged.
Security assessment
Changes are purely branding/terminology updates without modifying security-related content. References to security components (IAM roles, security groups, S3 bucket policies) remain unchanged. No vulnerability fixes or security enhancements were introduced.
Diff
diff --git a/whitepapers/latest/overview-deployment-options/aws-cloudformation.md b/whitepapers/latest/overview-deployment-options/aws-cloudformation.md index 14caa349c..6c913c11e 100644 --- a//whitepapers/latest/overview-deployment-options/aws-cloudformation.md +++ b//whitepapers/latest/overview-deployment-options/aws-cloudformation.md @@ -7 +7 @@ -[AWS CloudFormation](https://aws.amazon.com/cloudformation/) is a service that enables customers to provision and manage almost any AWS resource using a custom template language expressed in YAML or JSON. An AWS CloudFormation template creates infrastructure resources in a group called a _stack_ , and allows you to define and customize all components needed to operate your application while retaining full control of these resources. Using templates introduces the ability to implement version control on your infrastructure, and the ability to quickly and reliably replicate your infrastructure. +[AWS CloudFormation](https://aws.amazon.com/cloudformation/) is a service that enables customers to provision and manage almost any AWS resource using a custom template language expressed in YAML or JSON. An CloudFormation template creates infrastructure resources in a group called a _stack_ , and allows you to define and customize all components needed to operate your application while retaining full control of these resources. Using templates introduces the ability to implement version control on your infrastructure, and the ability to quickly and reliably replicate your infrastructure. @@ -9 +9 @@ -AWS CloudFormation offers granular control over the provisioning and management of all application infrastructure components, from low-level components such as route tables or subnet configurations, to high-level components such as CloudFront distributions. AWS CloudFormation is commonly used with other AWS deployment services or third-party tools, combining AWS CloudFormation with more specialized deployment services to manage deployments of application code onto infrastructure components. +CloudFormation offers granular control over the provisioning and management of all application infrastructure components, from low-level components such as route tables or subnet configurations, to high-level components such as CloudFront distributions. CloudFormation is commonly used with other AWS deployment services or third-party tools, combining CloudFormation with more specialized deployment services to manage deployments of application code onto infrastructure components. @@ -24,5 +24,5 @@ Capability | Description -Provision | CloudFormation will automatically create and update infrastructure components that are defined in a template. Refer to [AWS CloudFormation Best Practices](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/best-practices.html) for more details on creating infrastructure using AWS CloudFormation templates. -Configure | AWS CloudFormation templates offer extensive flexibility to customize and update all infrastructure components. Refer to [AWS CloudFormation Template Anatomy](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-anatomy.html) for more details on customizing templates. -Deploy | Update your AWS CloudFormation templates to alter the resources in a stack. Depending on your application architecture, you might need an additional deployment service to update the application version running on your infrastructure. Refer to [Deploying Applications on Amazon EC2 with AWS CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/deploying.applications.html) for more details on how AWS CloudFormation can be used as a deployment solution. -Scale | AWS CloudFormation will not automatically handle infrastructure scaling on your behalf; however, you can configure auto scaling policies for your resources in a AWS CloudFormation template. -Monitor | AWS CloudFormation provides native monitoring of the success or failure of updates to infrastructure defined in a template, as well as _drift detection_ to monitor when resources defined in a template do not meet specifications. Additional monitoring solutions will need to be in place for application-level monitoring and metrics. Refer to [Monitoring the Progress of a Stack Update](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-monitor-stack.html) for more details on how AWS CloudFormation monitors infrastructure updates. +Provision | CloudFormation will automatically create and update infrastructure components that are defined in a template. Refer to [AWS CloudFormation Best Practices](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/best-practices.html) for more details on creating infrastructure using CloudFormation templates. +Configure | CloudFormation templates offer extensive flexibility to customize and update all infrastructure components. Refer to [CloudFormation Template Anatomy](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-anatomy.html) for more details on customizing templates. +Deploy | Update your CloudFormation templates to alter the resources in a stack. Depending on your application architecture, you might need an additional deployment service to update the application version running on your infrastructure. Refer to [Deploying Applications on Amazon EC2 with AWS CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/deploying.applications.html) for more details on how CloudFormation can be used as a deployment solution. +Scale | CloudFormation will not automatically handle infrastructure scaling on your behalf; however, you can configure auto scaling policies for your resources in a CloudFormation template. +Monitor | CloudFormation provides native monitoring of the success or failure of updates to infrastructure defined in a template, as well as _drift detection_ to monitor when resources defined in a template do not meet specifications. Additional monitoring solutions will need to be in place for application-level monitoring and metrics. Refer to [Monitoring the Progress of a Stack Update](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-monitor-stack.html) for more details on how CloudFormation monitors infrastructure updates. @@ -30 +30 @@ Monitor | AWS CloudFormation provides native monitoring of the success or fail -The following diagram shows a common use case for AWS CloudFormation. Here, AWS CloudFormation templates are created to define all infrastructure components necessary to create a simple three-tier web application. In this example, we are using bootstrap scripts defined in AWS CloudFormation to deploy the latest version of our application onto Amazon EC2 instances; however, it is also a common practice to combine additional deployment services with AWS CloudFormation (using AWS CloudFormation only for its infrastructure management and provisioning capabilities). Note that more than one AWS CloudFormation template is used to create the infrastructure. In the diagram, AWS CloudFormation is used to create all infrastructure components including IAM roles, VPCs, subnets, route tables, security groups, and Amazon S3 bucket policies. Separate AWS CloudFormation templates are used to build each domain of the application architecture. +The following diagram shows a common use case for CloudFormation. Here, CloudFormation templates are created to define all infrastructure components necessary to create a simple three-tier web application. In this example, we are using bootstrap scripts defined in CloudFormation to deploy the latest version of our application onto Amazon EC2 instances; however, it is also a common practice to combine additional deployment services with CloudFormation (using CloudFormation only for its infrastructure management and provisioning capabilities). Note that more than one CloudFormation template is used to create the infrastructure. In the diagram, CloudFormation is used to create all infrastructure components including IAM roles, VPCs, subnets, route tables, security groups, and Amazon S3 bucket policies. Separate CloudFormation templates are used to build each domain of the application architecture.