How to investigate the costs of AWS Config configuration item recording
Introduction
Hello. This is Omori from Technical Support.
Recently my daughter became obsessed with Pompompurin.
She keeps singing the song "Purin to Muffin no Pompom Beat☆".
I often receive inquiries about the high cost of AWS Config configuration item recording.
I'd like to compile the investigation methods we typically recommend into a single blog post.
How to investigate using the CloudWatch metric "ConfigurationItemsRecorded"
You can actually identify which resource types are increasing in recording volume using CloudWatch metrics.
Since we already have a detailed company blog on the procedure, please refer to it for your investigation.
【AWS Config Cost Reduction】Checking which resources are causing the issue using CloudWatch metrics
How to analyze AWS Config logs delivered to S3 buckets using Amazon Athena
By querying the logs delivered to S3 buckets with Athena, you can identify the specific resources causing the increase in recordings.
For procedures, please refer to our company blog and re:Post.
How can I retrieve the number of configuration items recorded by AWS Config each month?
How to reduce AWS Config costs
You can reduce AWS Config charges by either decreasing the recording frequency of resource types or excluding them from recording.
Consider the following methods for cost reduction.
Changing the recording frequency for customer-managed configuration recorders
Excluding resources from recording using AWS Config
If you're managing AWS Config with AWS Control Tower, directly modifying resources is not recommended.
For solutions on how to modify existing AWS Config in such cases, please refer to the AWS blog published here.
Customizing AWS Config resource tracking in AWS Control Tower environments
Conclusion
I've compiled the methods we frequently recommend in one place.
I hope this blog will be helpful to some of you.
