CloudWatch Logs Insights Cost Calculator
Logs Insights-style pricing is often driven by how much data your queries scan. This calculator estimates monthly query scan cost from scanned GB/day and your per-GB scan price, and compares baseline vs peak query volume.
Maintained by CloudCostKit Editorial Team. Last updated: 2026-01-28. Editorial policy and methodology.
Best next steps
Use this calculator for the first estimate, then validate the answer with the closest guide or companion tool.
Inputs
Results
CloudWatch Logs Insights cost is mostly about scanned scope and cadence
This page should stay CloudWatch-specific. The expensive part is not only that you have logs in CloudWatch. It is that Logs Insights queries can repeatedly scan broad windows across active log groups. The real cost driver is how often that happens and how wide each query reaches.
- Dashboard cadence: repeated Insights queries create the calm-month scan baseline.
- Query window: wide time ranges expand scanned GB faster than teams expect.
- Incident mode: outages often multiply both query frequency and query breadth.
Where Logs Insights estimates usually go wrong
- Query scan cost is blended together with ingestion and retention instead of treated as its own behavior-driven line.
- Dashboard refresh cadence is forgotten even though it runs all day.
- Common investigation windows are guessed instead of taken from actual team habits.
- Peak incident search behavior is averaged into a normal month.
What to capture before trusting the CloudWatch query model
- List top dashboards and Insights queries, then note their refresh intervals.
- Estimate typical and incident-time query window sizes separately.
- Keep Logs Insights scan cost separate from CloudWatch ingestion and retention lines.
- Review whether filters, saved queries, or narrower group selection can cut scanned GB materially.
Baseline vs incident-driven Insights scenarios
| Scenario | GB scanned/day | Query frequency | Notes |
|---|---|---|---|
| Baseline | Expected | Normal | Daily dashboards |
| Peak | High | High | Incident queries |
How to review the first real Logs Insights bill
- Check scanned GB against real dashboard cadence and the most common incident queries before changing retention assumptions.
- Identify whether the dominant driver was broad time windows, high refresh frequency, or too many active log groups in the query scope.
Next steps
Example scenario
- 800 GB/day scanned at $0.005/GB = about 24,320 GB scanned/month and ~$122/month.
- Use a peak multiplier for incident dashboards and query bursts.
Included
- Query scan cost estimate from GB scanned per day and $/GB scan pricing.
- Useful for CloudWatch Logs Insights and similar per-scan log query models.
- Baseline vs peak comparison for scan spikes.
Not included
- Log ingestion charges and retention storage (model separately).
- Provider-specific query minimums, caching, and index behavior.
How we calculate
- Monthly scanned GB ~ GB scanned per day x 30.4.
- Scan cost = monthly scanned GB x scan price per GB.
- Use a peak multiplier when dashboards refresh more often or scan wider windows.
- This tool estimates scan-only (not ingestion or retention).
FAQ
How do I estimate GB scanned per day?
How do I reduce Logs Insights scan costs?
Related tools
Related guides
Disclaimer
Educational use only. Not legal, financial, or professional advice. Results are estimates based on the inputs and assumptions shown on this page. Verify pricing and limits with your providers and documentation.
Last updated: 2026-01-28. Reviewed against CloudCostKit methodology and current provider documentation. See the Editorial Policy .