# CloudWatch Logs pricing explained

AWS pricing explained · Updated 17 November 2026

**Short answer:** CloudWatch Logs charges $0.50 per GB ingested into the Standard log class ($0.25 for Infrequent Access), $0.03 per GB-month to store it, and $0.005 per GB scanned by Logs Insights queries, in us-east-1 at the time of writing. Ingestion is usually the biggest line, so the volume your code logs matters far more than how long you keep it.

## Pricing dimensions

| Dimension | Unit | us-east-1 price |
|---|---|---|
| Ingestion, Standard log class | GB | $0.50 |
| Ingestion, Infrequent Access log class | GB | $0.25 |
| Storage (archived log data) | GB-month | $0.03 |
| Logs Insights queries | GB scanned | $0.005 |
| Vended logs (VPC Flow Logs and similar), first 10 TB | GB | $0.50, lower in later tiers |
| Vended logs delivered to S3, first 10 TB | GB | $0.25 |

From the AWS Price List API at the time of writing. Vended logs are logs AWS services publish on your behalf (VPC Flow Logs, Route 53 Resolver query logs and others) and get volume discounts that application logs do not.

## Worked examples

**1. A fleet of Lambda functions.** 100 GB of logs a month with 30-day retention, so about 100 GB stored at any time:

- Ingestion: 100 × $0.50 = $50.00
- Storage: 100 × $0.03 = $3.00
- **Total: $53.00** a month

**2. Never-expire retention.** The same 100 GB a month kept for a year leaves 1,200 GB stored: 1,200 × $0.03 = $36.00 a month and still rising. Retention is cheap per GB but never stops growing; see [how to set log retention](https://cloudconsole.dev/how-to/set-cloudwatch-log-retention).

**3. A dashboard of Insights queries.** A widget scanning 50 GB, refreshed 20 times a day for 30 days, runs 600 queries: 600 × 50 = 30,000 GB × $0.005 = **$150.00**. Narrow the time range and the log groups queried to cut it.

Infrequent Access would make example 1's ingestion 100 × $0.25 = $25.00, at the cost of features.

## Choosing a log class

The Infrequent Access class halves ingestion cost but lacks features the Standard class has, including metric filters, subscription filters and Live Tail; you can still query it with Logs Insights. The class is chosen when the log group is created and cannot be changed afterwards, so use it for debug and audit logs you rarely search rather than for logs that drive alarms.

## Hidden and easy-to-miss charges

- **Default retention is "Never expire"** for most log groups created by services.
- **Debug logging left on** after an incident, often doubling ingestion.
- **VPC Flow Logs to CloudWatch** for a busy VPC; sending them to S3 is cheaper per GB.
- **Subscription filters** forwarding logs to Lambda or Firehose, which bill on the receiving side.
- **Data protection policies** that scan logs for sensitive data are billed per GB scanned.
- **Exports to S3** and cross-account delivery, which add transfer and request charges.

## Seeing log cost

Cost Explorer shows logs under CloudWatch. Group by Usage type: `DataProcessing-Bytes` is Standard ingestion, `TimedStorage-ByteHrs` storage, `USE1-DataScanned-Bytes` Insights and `USE1-VendedLog-Bytes` vended logs. To find the noisiest log group, sort log groups by the `IncomingBytes` metric in the `AWS/Logs` namespace. Set retention in bulk with [logs put-retention-policy](https://cloudconsole.dev/cli/logs-put-retention-policy).

Cutting it: [cutting CloudWatch Logs cost](https://cloudconsole.dev/costs/cloudwatch-logs-cost) and [VPC Flow Logs cost](https://cloudconsole.dev/costs/vpc-flow-logs-cost).

## Questions

### How much does CloudWatch Logs cost per GB?

$0.50 per GB ingested for the Standard class and $0.25 for Infrequent Access, plus $0.03 per GB-month stored, in us-east-1 at the time of writing.

### How much do Logs Insights queries cost?

$0.005 per GB of log data scanned, in us-east-1 at the time of writing. A query over a narrower time range scans less and costs less.

### Does log retention reduce cost?

It reduces the storage line, which grows every month without retention. It does nothing for ingestion, usually the larger charge.

### Are VPC Flow Logs charged as CloudWatch Logs?

Yes, as vended logs, which start at the same per-GB price as Standard ingestion and get cheaper at high volume. Delivering them to S3 instead is cheaper.

## When this happens away from your desk

A log group that suddenly ingests ten times its usual volume is worth knowing about the same day. CloudConsole is being built to show logs, alarms and costs on a phone.

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [Amazon CloudWatch pricing](https://aws.amazon.com/cloudwatch/pricing/)
- [Amazon CloudWatch Logs User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/)

## Related

- [Amazon CloudWatch pricing explained](https://cloudconsole.dev/aws-pricing/cloudwatch-pricing)
- [How to set CloudWatch log retention](https://cloudconsole.dev/how-to/set-cloudwatch-log-retention)
- [aws logs put-retention-policy](https://cloudconsole.dev/cli/logs-put-retention-policy)
- [How much do VPC Flow Logs cost?](https://cloudconsole.dev/costs/vpc-flow-logs-cost)
- [Why is my CloudWatch Logs bill so high?](https://cloudconsole.dev/costs/cloudwatch-logs-cost)
- [AWS Lambda pricing explained](https://cloudconsole.dev/aws-pricing/lambda-pricing)
- [AWS CloudTrail pricing explained](https://cloudconsole.dev/aws-pricing/cloudtrail-pricing)

---

Source: https://cloudconsole.dev/aws-pricing/cloudwatch-logs-pricing

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
