AWS wellarchitected documentation change
Summary
Changed 'AWS CloudFormation' to 'CloudFormation' in example scenario and blog post reference
Security assessment
The change is a branding terminology update (removing redundant 'AWS' prefix) but does not alter security context. The security group example remains unchanged in substance.
Diff
diff --git a/wellarchitected/2023-04-10/framework/ops_dev_integ_test_val_chg.md b/wellarchitected/2023-04-10/framework/ops_dev_integ_test_val_chg.md index c76e06926..afb85a89a 100644 --- a//wellarchitected/2023-04-10/framework/ops_dev_integ_test_val_chg.md +++ b//wellarchitected/2023-04-10/framework/ops_dev_integ_test_val_chg.md @@ -28 +28 @@ Your organization must develop testing standards for all software artifacts. Aut - * New security groups are deployed with AWS CloudFormation without being tested in a pre-production environment. The security groups make your app unreachable for your customers. + * New security groups are deployed with CloudFormation without being tested in a pre-production environment. The security groups make your app unreachable for your customers. @@ -94 +94 @@ As part of their continuous integration pipeline, AnyCompany Retail conducts sev - * [ Automated AWS CloudFormation Testing Pipeline with TaskCat and CodePipeline ](https://aws.amazon.com/blogs/devops/automated-cloudformation-testing-pipeline-with-taskcat-and-codepipeline/) + * [ Automated CloudFormation Testing Pipeline with TaskCat and CodePipeline ](https://aws.amazon.com/blogs/devops/automated-cloudformation-testing-pipeline-with-taskcat-and-codepipeline/)