Skip to content

Commit 8aa13f2

Browse files
authored
Merge pull request #43 from aws-samples/bug/documentation-cleanup
Modified the delete instructions for the GuardDuty solution
2 parents 853ec32 + 816db66 commit 8aa13f2

File tree

1 file changed

+19
-14
lines changed
  • solutions/guardduty/guardduty-org/aws-control-tower

1 file changed

+19
-14
lines changed

solutions/guardduty/guardduty-org/aws-control-tower/README.md

Lines changed: 19 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -35,19 +35,24 @@ Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved. SPDX-License-
3535
# Delete Instructions
3636

3737
1. Within the Customizations for AWS Control Tower configuration
38-
1. Remove the CloudTrail configurations from the manifest.yaml file
39-
2. (Optional) Delete the parameter and template files for the CloudTrail solution
38+
1. Remove the GuardDuty configurations from the manifest.yaml file
39+
2. (Optional) Delete the parameter and template files for the GuardDuty solution
4040
2. Deploy the Customizations for AWS Control Tower configuration
4141
3. After the pipeline completes, log into the Management account and navigate to the CloudFormation page
42-
1. Delete the Stack Instance from the CustomControlTower-CloudTrailOrg CloudFormation StackSet
43-
1. Verify that the CloudTrail created by the solution has been deleted
44-
2. After the Stack Instance deletes, delete the CustomControlTower-CloudTrailOrg CloudFormation StackSet
45-
3. Log into the Log Archive account and delete the 2 org-trail-logs S3 buckets
46-
4. Delete the Stack Instance from the CustomControlTower-CloudTrailOrgS3Buckets CloudFormation StackSet
47-
5. After the Stack Instance deletes, delete the CustomControlTower-CloudTrailOrgS3Buckets CloudFormation StackSet
48-
6. Delete the Stack Instance from the CustomControlTower-CloudTrailOrgKMSKey CloudFormation StackSet
49-
7. After the Stack Instance deletes, delete the CustomControlTower-CloudTrailOrgKMSKey CloudFormation StackSet
50-
51-
52-
53-
42+
1. Delete the Stack Instance from the CustomControlTower-GuardDutyOrgConfiguration CloudFormation StackSet
43+
1. Verify that the GuardDuty has been disabled in all accounts/regions
44+
2. After the Stack Instance deletes, delete the CustomControlTower-GuardDutyOrgConfiguration CloudFormation StackSet
45+
3. Delete the Stack Instance from the CustomControlTower-GuardDutyOrgConfigurationRole CloudFormation StackSet
46+
4. After the Stack Instance deletes, delete the CustomControlTower-GuardDutyOrgConfigurationRole CloudFormation
47+
StackSet
48+
5. Delete the stack instances from the CustomControlTower-GuardDutyDeleteDetectorRole CloudFormation StackSet
49+
6. After the stack instances are deleted, delete the CustomControlTower-GuardDutyDeleteDetectorRole CloudFormation
50+
StackSet
51+
7. Log into the Log Archive account and empty/delete the guardduty-delivery S3 bucket
52+
8. Delete the Stack Instance from the CustomControlTower-GuardDutyOrgDeliveryS3Bucket CloudFormation StackSet
53+
9. After the Stack Instance deletes, delete the CustomControlTower-GuardDutyOrgDeliveryS3Bucket CloudFormation
54+
StackSet
55+
10. Delete the Stack Instance from the CustomControlTower-GuardDutyOrgDeliveryKMSKey CloudFormation StackSet
56+
11. After the Stack Instance deletes, delete the CustomControlTower-GuardDutyOrgDeliveryKMSKey CloudFormation
57+
StackSet
58+
12. Verify that the CloudWatch Log Group "/aws/lambda/...guardduty-org-configuration" was deleted

0 commit comments

Comments
 (0)