As of November 15, 2026, this post sums up the official pages linked here.
The problem
A common story from AWS users: someone opens the monthly bill and finds that CloudWatch costs more than the servers it watches. They drill in, and almost all of it is one usage type ending in DataProcessing-Bytes . They ask what that is, and why it grew when traffic didn't.
Our team at CloudSkill Consulting LLC sees the same pattern in cost reviews. In most cases nothing is broken. A service is simply sending far more log data than anyone planned, and the data is kept forever. In this post we show how to find the cause, fix it safely with the AWS CLI and Terraform, and check that the fix worked.
Root cause: you pay to send logs, then to keep them
CloudWatch Logs charges separately for each step.…