AWS solutions documentation change
Summary
Updated uninstallation documentation with clearer resource cleanup instructions, added details about ALB+ECS Fargate cleanup, and emphasized pre-deletion steps for regional stacks and test scenarios.
Security assessment
Changes focus on operational cleanup procedures (S3 buckets, DynamoDB, CloudWatch) and deployment-specific resource removal. No evidence of security vulnerability fixes, security incident references, or new security features. Updates improve clarity but don't address security weaknesses.
Diff
diff --git a/solutions/latest/distributed-load-testing-on-aws/uninstall-the-solution.md b/solutions/latest/distributed-load-testing-on-aws/uninstall-the-solution.md index b8a207059..39ea24bbb 100644 --- a//solutions/latest/distributed-load-testing-on-aws/uninstall-the-solution.md +++ b//solutions/latest/distributed-load-testing-on-aws/uninstall-the-solution.md @@ -7 +7 @@ -Using the AWS Management ConsoleUsing AWS Command Line InterfaceDeleting the Amazon S3 buckets +Using the AWS Management ConsoleUsing AWS Command Line InterfaceCleaning up ALB + ECS Fargate post-deployment resources @@ -11 +11 @@ Using the AWS Management ConsoleUsing AWS Command Line InterfaceDeleting the Ama -You can uninstall the Distributed Load Testing on AWS solution from the AWS Management Console or by using the AWS Command Line Interface. You must manually delete the console, scenario, and logging Amazon Simple Storage Service (Amazon S3) buckets created by this solution. AWS Solutions Implementations do not automatically delete them in case you have data to retain. +You can uninstall the Distributed Load Testing on AWS solution from the AWS Management Console or by using the AWS Command Line Interface (AWS CLI). You must manually delete several retained resources created by this solution. AWS Solutions do not automatically delete storage and logging resources in case you have data to retain. As such, see the following information on how to delete S3 buckets, DynamoDB tables, CloudWatch log groups, and CloudWatch dashboards. @@ -13 +13 @@ You can uninstall the Distributed Load Testing on AWS solution from the AWS Mana -###### Note +###### Important @@ -15 +15 @@ You can uninstall the Distributed Load Testing on AWS solution from the AWS Mana -If you have deployed regional stacks, you must delete the stacks in those Regions before deleting the main stack. +Before uninstalling the solution, ensure that all regional stacks have been deleted first. We also recommend deleting all test scenarios through the DLT web console before deleting the main stack. This ensures that runtime-created resources such as CloudWatch dashboards are properly cleaned up. @@ -21 +21 @@ If you have deployed regional stacks, you must delete the stacks in those Region - 1. Sign in to the [AWS CloudFormation console](https://console.aws.amazon.com/cloudformation/home). + 1. Sign in to the [CloudFormation console](https://console.aws.amazon.com/cloudformation/home/). @@ -45 +45 @@ If you have deployed regional stacks, you must delete the stacks in those Region -Determine whether the AWS Command Line Interface (AWS CLI) is available in your environment. For installation instructions, refer to [What Is the AWS Command Line Interface](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html) in the _AWS CLI User Guide_. After confirming that the AWS CLI is available, run the following command. +Determine whether the AWS Command Line Interface (AWS CLI) is available in your environment. For installation instructions, see [What Is the AWS Command Line Interface](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html) in the _AWS CLI User Guide_. After confirming that the AWS CLI is available, run the following command. @@ -50 +50 @@ Determine whether the AWS Command Line Interface (AWS CLI) is available in your -## Deleting the Amazon S3 buckets +## Cleaning up ALB + ECS Fargate post-deployment resources @@ -52,25 +52 @@ Determine whether the AWS Command Line Interface (AWS CLI) is available in your -This solution is configured to retain the solution-created Amazon S3 buckets (for deploying in an opt-in Region) if you decide to delete the AWS CloudFormation stack to prevent accidental data loss. After uninstalling the solution, you can manually delete this S3 bucket if you do not need to retain the data. Follow these steps to delete the Amazon S3 bucket. - - 1. Sign in to the [Amazon S3 console](https://console.aws.amazon.com/s3/home). - - 2. Choose **Buckets** from the left navigation pane. - - 3. In the **Find buckets by name** field, enter the name of this solution’s stack. - - 4. Select one of the solution’s S3 buckets and choose **Empty**. - - 5. Enter **permanently delete** in the verification field and choose **Empty**. - - 6. Select the S3 bucket you just emptied and choose **Delete**. - - 7. Enter the S3 bucket name in the verification field and choose **Delete bucket**. - - - - -Repeat steps 4 through 7 until you delete all the S3 buckets. - -To delete the S3 bucket using AWS CLI, run the following command: - - - $ aws s3 rb s3://<bucket-name> --force +If you chose the ALB + ECS Fargate deployment option, delete the CNAME or Route 53 Alias record that maps your custom domain to the ALB DNS name in your DNS provider. If the ACM certificate is no longer needed, you can also delete it from the [ACM console](https://console.aws.amazon.com/acm/). The AWS WAF web ACL deployed in front of the ALB is automatically deleted when the CloudFormation stack is deleted. @@ -84 +60 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Contact AWS Support +Update using AWS CloudFormation @@ -86 +62 @@ Contact AWS Support -Use the solution +Manually deleting retained resources