Posted on Jun 24, 2026 · Updated Jun 24, 2026 · 9 min read
AWS CloudWatch Costs: Why Logging Eats Your Bill (2026)
CloudWatch is one of the most common surprise line items on an AWS bill. The reason is simple: log ingestion costs $0.50 per GB, and a chatty application can emit hundreds of gigabytes a month without anyone noticing until the invoice arrives. Add custom metrics at $0.30 each per month, and CloudWatch routinely reaches 5–15% of a growth-stage AWS bill — almost all of it avoidable.
The good news: CloudWatch cost is one of the easiest wins in FinOps because it's driven by a few knobs — log volume, retention, custom metrics, and query scanning. This guide explains how each is priced in 2026, why the bill creeps up, and the specific changes that cut it 40–70%. It pairs with our data transfer cost map and AWS pricing changes 2026.
TL;DR — CloudWatch cost (2026)
- Log ingestion: $0.50/GB (Standard), $0.25/GB (Infrequent Access)
- Log storage: $0.03/GB/month — infinite retention is a silent cost
- Custom metrics: $0.30/metric/month; high-cardinality dimensions multiply fast
- Logs Insights queries: $0.005/GB scanned
- Dashboards $3 each/month; alarms $0.10 standard, $0.30 high-resolution
- Biggest levers: log levels, retention policies, dropping unused custom metrics, exporting cold logs to S3
Table of contents
How is CloudWatch priced?
CloudWatch is not one product but several, each metered differently. The two that dominate most bills are Logs ingestion and custom metrics. The table below covers the components you are most likely to see, at 2026 us-east-1 list prices (AWS CloudWatch Pricing).
| Component | Price | Notes |
|---|---|---|
| Logs ingestion (Standard) | $0.50/GB | The usual #1 cost |
| Logs ingestion (Infrequent Access) | $0.25/GB | Half price; limited query features |
| Logs storage | $0.03/GB/month | Charged until logs expire |
| Custom metrics | $0.30/metric/month | First 10,000; each dimension combo is a metric |
| Logs Insights queries | $0.005/GB scanned | Cost scales with data scanned, not rows returned |
| Dashboards | $3.00/dashboard/month | First 3 free |
| Alarms | $0.10–$0.30/alarm | Standard vs high-resolution |
Why does the bill surprise teams?
CloudWatch costs creep because the drivers are invisible at write time. Nobody sees a line item when an app logs a verbose debug payload on every request, or when a developer adds a custom metric per customer ID (turning one metric into thousands via high cardinality), or when a default log group keeps logs forever at $0.03/GB/month. The spend accrues quietly and only shows up aggregated on the bill — which is exactly why it's usually 20–70% reducible once you look.
The $0.50/GB ingestion math
Work an example. A service handling 50 requests/second that logs 2 KB per request emits roughly 100 MB/minute, or about 260 GB/month. At $0.50/GB that is $130/month in ingestion alone for a single service — before storage, metrics, or queries. Multiply across a fleet of microservices each running verbose logging and the number compounds quickly. Dropping log level from DEBUG to INFO often cuts volume by 5–10x, taking that $130 to $15–$25.
How do you reduce CloudWatch costs?
Six high-impact moves, roughly in order of payoff:
- Right-size log levels. Ship INFO or WARN in production, not DEBUG. This single change is usually the biggest reducer.
- Set retention on every log group. Default is "never expire." Most teams need 7–30 days hot; set it explicitly.
- Use the Infrequent Access log class ($0.25/GB) for logs you rarely query interactively.
- Export cold logs to S3 ($0.023/GB) and query with Athena instead of paying CloudWatch storage indefinitely.
- Audit custom metrics. Delete unused ones and avoid high-cardinality dimensions (per-user, per-request IDs) that explode metric counts.
- Scope Logs Insights queries. Cost scales with GB scanned — narrow the time range and log group before running broad queries.
For where CloudWatch fits in the broader bill, see the average AWS bill by company stage and the line-item $500/mo AWS bill breakdown.
Find your CloudWatch waste automatically
spendark surfaces your highest-volume log groups, unused custom metrics, and log groups with no retention policy — so you can cut CloudWatch spend without guesswork.
Frequently asked questions
Why is my CloudWatch bill so high?
Almost always log ingestion at $0.50/GB and custom metrics at $0.30 each. Verbose (DEBUG-level) logging, log groups with no retention limit, and high-cardinality custom metrics are the three biggest drivers. CloudWatch commonly reaches 5–15% of an AWS bill and is usually 20–70% reducible.
How much does CloudWatch Logs cost?
Log ingestion is $0.50/GB on the Standard class and $0.25/GB on Infrequent Access, plus $0.03/GB/month for storage until logs expire. A single service logging 2 KB per request at 50 req/s generates ~260 GB/month, or ~$130 in ingestion alone.
How do CloudWatch custom metrics get expensive?
Each custom metric costs $0.30/month, and every unique combination of dimension values counts as a separate metric. Adding a per-customer or per-request-ID dimension can turn one metric into thousands, so high-cardinality dimensions are the fastest way to a large metrics bill.
Should I export CloudWatch logs to S3?
For logs you keep for compliance or occasional analysis, yes. S3 storage is $0.023/GB versus CloudWatch's $0.03/GB, and you can query with Athena on demand instead of paying to keep everything hot. Keep only recent, actively-queried logs in CloudWatch.
What's the fastest way to cut CloudWatch costs?
Lower production log verbosity from DEBUG to INFO and set a retention policy on every log group. These two changes alone routinely cut CloudWatch spend by half or more, because ingestion volume and indefinite storage are the dominant costs.
Estimate your cloud costs — for free
Compare AWS, Azure, and GCP pricing side by side with our free calculator, and dig into the guides to learn how to cut cloud waste. No sign-up required.