AWS Config costs can skyrocket for volatile workloads like Fargate tasks due to frequent resource creation and deletion. Each Fargate task launch triggers 4 configuration changes (ENI, VPC, subnet, security group), making Config costs exceed the actual compute costs. Switching from continuous to daily recording frequency can reduce Config costs by up to 1400% while maintaining Security Hub compliance, though it comes with trade-offs like missing some changes and higher per-change costs for non-volatile workloads.
Table of contents
Checking my AWS billInvestigating the Cost SpikeRoot Cause AnalysisAWS Config cost optimizationSummary20 Impressions