AWS solutions documentation change
Summary
Completely restructured the uninstallation instructions, adding notes about RETAIN removal policies, providing a specific `mdaa destroy` command, and clarifying manual deletion steps for retained data resources.
Security assessment
This change improves operational clarity for uninstalling the solution and data retention. It mentions security groups and dependencies but does not address a security vulnerability or add security-specific documentation.
Diff
diff --git a/solutions/latest/modern-data-architecture-accelerator/uninstall-the-solution.md b/solutions/latest/modern-data-architecture-accelerator/uninstall-the-solution.md index 299d353c4..0331a3c95 100644 --- a//solutions/latest/modern-data-architecture-accelerator/uninstall-the-solution.md +++ b//solutions/latest/modern-data-architecture-accelerator/uninstall-the-solution.md @@ -4,0 +5,2 @@ +Additional notes + @@ -7 +9,11 @@ -The following manual steps would need to be followed in order to properly uninstall MDAA: +###### Note + +Infrastructure resources that maintain data (for example, S3 buckets, RDS instances, DynamoDB tables) are configured with a `RETAIN` removal policy. Running `mdaa destroy` will not remove these resources, so your data is preserved. + +However, some non-retained resources (for example, Security Groups) may depend on retained resources like RDS or OpenSearch instances. In these cases, the destroy can fail or take a long time to complete. To avoid this, delete the retained resources first before running `mdaa destroy`. + +Follow these steps to uninstall the solution: + + 1. Run `mdaa destroy` using the same configuration file (`mdaa.yaml`) that was used for deployment. This tears down all remaining MDAA-managed stacks in the correct dependency order. + + mdaa destroy -c ./mdaa.yaml @@ -9 +21 @@ The following manual steps would need to be followed in order to properly uninst - 1. Delete all the stacks that start with the organization name + 2. Delete any retained data resources (for example, S3 buckets, RDS instances, DynamoDB tables, OpenSearch domains) that are no longer needed. These resources will have the organization name as a prefix. @@ -11 +22,0 @@ The following manual steps would need to be followed in order to properly uninst - 2. Delete also the stack that the installer template created @@ -13 +23,0 @@ The following manual steps would need to be followed in order to properly uninst - 3. Delete all the S3 buckets with the organization name as prefix in the bucket name @@ -15,0 +26 @@ The following manual steps would need to be followed in order to properly uninst +## Additional notes @@ -16,0 +28 @@ The following manual steps would need to be followed in order to properly uninst +For more information on AWS CDK, refer to the [AWS CDK Developer Guide](https://docs.aws.amazon.com/cdk/v2/guide/home.html).