- Newest
- Most votes
- Most comments
AWS Config's intended role in what you're working on would be to map out the existence, locations, and configurations of your resources. If you have AWS Config enabled in all the regions you want to get rid of, you could query the configuration snapshots you can set it to deliver to your S3 bucket with a tool such as Athena to discover which resources you have in the non-preferred regions.
There's a blog post with a step-by-step walkthrough for setting up AWS Config snapshot delivery to S3 and querying the configuration snapshots in your central S3 bucket for AWS Config with SQL in Amazon Athena: https://aws.amazon.com/blogs/mt/how-to-query-your-aws-resource-configuration-states-using-aws-config-and-amazon-athena/
Deleting your resources, such as databases, I would think you'd want to do very carefully and under human review and control, rather than having a script wiping out entire databases, servers, encryption keys required for accessing data and backups, and other resources.
Relevant content
- Accepted Answerasked 3 months ago
- asked 2 months ago
- asked 2 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a month ago