By walking through these scenarios you generated, analyzed, and remediated some or all of the following findings in your environment:
Now that you understand the different components of the GuardDuty service and how it integrates with other AWS services, you can explore ways of using it across your own environments.
To remove the assets created by the CloudFormation, follow these steps:
- Delete the S3 buckets that were created by the CloudFormation template (it will have names that begins with guardduty-example). This needs to be done because data was put in the bucket and CloudFormation will not allow you to delete a bucket with data in it.
- Delete the compromised instance IAM Roles (it will have the name GuardDuty-Example-EC2-Compromised). Because one of the Lambda functions added an additional policy to this Role you need to manually delete this.
- Delete the custom Threat List within GuardDuty. Within the GuardDuty console click Lists in the left navigation. From there delete the Example-Threat-List.
Disable GuardDuty. Within the GuardDuty console click Settings. Then check the box to Disable GuardDuty and save.
Suspending GuardDuty stops the service from monitoring so you don't incur any costs and won't receive any findings but it will retain your existing findings and baseline activity.
Delete the CloudFormation Stack. If you see any errors, it means you didn't delete the S3 Bucket or IAM role in the previous steps.