AWS Security ChangesHomeSearch

AWS codedeploy documentation change

Service: codedeploy · 2025-11-19 · Documentation low

File: codedeploy/latest/userguide/tutorials-windows-clean-up.md

Summary

Standardized terminology by replacing 'AWS CloudFormation' with 'CloudFormation' throughout the cleanup instructions

Security assessment

Changes are purely cosmetic/nomenclature updates to align with product naming conventions. No security-related content was added or modified, and no vulnerabilities are addressed. Instructions for resource cleanup remain functionally identical.

Diff

diff --git a/codedeploy/latest/userguide/tutorials-windows-clean-up.md b/codedeploy/latest/userguide/tutorials-windows-clean-up.md
index 42745381f..823cec425 100644
--- a//codedeploy/latest/userguide/tutorials-windows-clean-up.md
+++ b//codedeploy/latest/userguide/tutorials-windows-clean-up.md
@@ -11 +11 @@ You've now successfully made an update to the "Hello, World!" code and redeploye
-  * Any AWS CloudFormation stacks (or terminate any Amazon EC2 instances, if you created them outside of AWS CloudFormation).
+  * Any CloudFormation stacks (or terminate any Amazon EC2 instances, if you created them outside of CloudFormation).
@@ -22 +22 @@ You've now successfully made an update to the "Hello, World!" code and redeploye
-You can use the AWS CLI, the AWS CloudFormation, Amazon S3, Amazon EC2, and CodeDeploy consoles, or the AWS APIs to perform the cleanup.
+You can use the AWS CLI, the CloudFormation, Amazon S3, Amazon EC2, and CodeDeploy consoles, or the AWS APIs to perform the cleanup.
@@ -37 +37 @@ You can use the AWS CLI, the AWS CloudFormation, Amazon S3, Amazon EC2, and Code
-  1. If you used the AWS CloudFormation stack for this tutorial, delete the stack by calling the **delete-stack** command against the stack named `CodeDeployDemoStack`. This terminates all accompanying Amazon EC2 instances and delete all accompanying IAM roles originally created by the stack.
+  1. If you used the CloudFormation stack for this tutorial, delete the stack by calling the **delete-stack** command against the stack named `CodeDeployDemoStack`. This terminates all accompanying Amazon EC2 instances and delete all accompanying IAM roles originally created by the stack.
@@ -57 +57 @@ You can get the `association-id` by calling the **describe-association** command
-  5. If you did not use the AWS CloudFormation stack for this tutorial, call the **terminate-instances** command to terminate Amazon EC2 instances you manually created. Supply the ID of the Amazon EC2 instance to terminate.
+  5. If you did not use the CloudFormation stack for this tutorial, call the **terminate-instances** command to terminate Amazon EC2 instances you manually created. Supply the ID of the Amazon EC2 instance to terminate.
@@ -66 +66 @@ You can get the `association-id` by calling the **describe-association** command
-If you used our AWS CloudFormation template for this tutorial, delete the associated AWS CloudFormation stack.
+If you used our CloudFormation template for this tutorial, delete the associated CloudFormation stack.
@@ -68 +68 @@ If you used our AWS CloudFormation template for this tutorial, delete the associ
-  1. Sign in to the AWS Management Console and open the AWS CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/).
+  1. Sign in to the AWS Management Console and open the CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/).
@@ -70 +70 @@ If you used our AWS CloudFormation template for this tutorial, delete the associ
-  2. In the search box, type the AWS CloudFormation stack name (for example, `CodeDeployDemoStack`).
+  2. In the search box, type the CloudFormation stack name (for example, `CodeDeployDemoStack`).
@@ -79 +79 @@ If you used our AWS CloudFormation template for this tutorial, delete the associ
-To terminate Amazon EC2 instances you created outside of an AWS CloudFormation stack:
+To terminate Amazon EC2 instances you created outside of an CloudFormation stack: