# How much do VPC Flow Logs cost?

AWS cost guides · Updated 17 November 2026

**Short answer:** VPC Flow Logs have no charge of their own; you pay vended log delivery per GB to the destination, plus storage and query costs there. Delivery to CloudWatch Logs is volume-tiered (the pricing example for N. Virginia starts at $0.50 per GB for the first 10 TB) and is usually the most expensive option; delivery to S3 is billed at a lower vended-log rate plus S3 storage.

## How the charge appears

| Destination | Usage types | Then also pay for |
|---|---|---|
| CloudWatch Logs (Standard) | `VendedLog-Bytes` | Log storage (`TimedStorage-ByteHrs`), Logs Insights scans |
| CloudWatch Logs (Essentials) | `VendedLogIA-Bytes` | Same storage and query charges |
| Amazon S3 | `S3-Egress-Bytes`; `S3-Egress-InputBytes` for Parquet conversion | S3 storage and requests, Athena scans |
| Amazon Data Firehose | `FH-Egress-Bytes` | Firehose ingestion and its destination |

All of these appear under the **CloudWatch** service, not under VPC, which is why flow log cost is often mistaken for application logging. Volume tiers reset each month and depend on destination and Region.

## What makes flow logs big

- **Scope**: a flow log on a whole VPC records every ENI, including load balancers, NAT gateways and EKS nodes.
- **Traffic type ALL** rather than REJECT.
- **One-minute aggregation** produces more records than the 10-minute default for chatty, long-lived connections.
- **Duplicate flow logs**: one per VPC and another per subnet or ENI on the same traffic.

```
# Every flow log in the Region, with scope, filter, destination and interval
aws ec2 describe-flow-logs \
  --query 'FlowLogs[].[FlowLogId,ResourceId,TrafficType,LogDestinationType,LogDestination||LogGroupName,MaxAggregationInterval]' \
  --output table
```

Estimate before you commit: volume tracks the number of flows per aggregation interval more than the bytes transferred. Enable a flow log on one busy subnet for a day, read the delivered volume from the `VendedLog-Bytes` or `S3-Egress-Bytes` line, and scale that up before choosing a destination for the whole VPC.

## Reduce it, biggest saving first

1. **Send to S3 instead of CloudWatch Logs** if you query flow logs occasionally; query them with Athena. Parquet format reduces Athena scan cost at a small conversion charge.
2. **Capture only what you use**: REJECT for security review, or ALL only on the subnets you troubleshoot.
3. **Keep the 10-minute aggregation interval** unless you need one-minute detail.
4. **Remove duplicates** found by the command above.
5. **Retention and lifecycle**: set CloudWatch retention or S3 expiry to your investigation window.

```
# Rejected traffic for a VPC, to S3 in Parquet with hourly partitions
aws ec2 create-flow-logs --resource-type VPC --resource-ids vpc-0123456789abcdef0 \
  --traffic-type REJECT --log-destination-type s3 \
  --log-destination arn:aws:s3:::my-flow-logs-bucket/vpc/ \
  --max-aggregation-interval 600 \
  --destination-options FileFormat=parquet,PerHourPartition=true
```

## What not to do

- Do not switch flow logs off in accounts where security or compliance requires them. Move them to a cheaper destination instead.
- Do not enable VPC flow logs just for GuardDuty. GuardDuty analyses VPC flow log data from its own independent stream, and bills that analysis separately ([GuardDuty cost](https://cloudconsole.dev/aws-pricing/guardduty-pricing)).
- Do not run unbounded Logs Insights queries across months of flow logs; each run bills per GB scanned.

## Questions

### Do VPC flow logs cost money?

Creating them is free, but delivery is billed as vended logs per GB, plus storage and query costs at the destination.

### Is it cheaper to send flow logs to S3 or CloudWatch?

S3 delivery is billed at a lower vended-log rate than CloudWatch Logs delivery, and S3 storage is cheaper; you query with Athena instead of Logs Insights.

### Where do flow log charges show in Cost Explorer?

Under CloudWatch, as VendedLog-Bytes for CloudWatch Logs delivery or S3-Egress-Bytes for S3 delivery.

## When this happens away from your desk

Flow log cost hides under CloudWatch, so it is often blamed on the wrong team. CloudConsole, a phone app for AWS, shows spend by usage type and explains VendedLog-Bytes, so you can tell flow logs from application logs on your 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

- [Publish flow logs to Amazon S3](https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs-s3.html)
- [Analyzing, optimizing, and reducing CloudWatch costs](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch_billing.html)
- [Amazon CloudWatch pricing](https://aws.amazon.com/cloudwatch/pricing/)

## Related

- [Why is my CloudWatch Logs bill so high?](https://cloudconsole.dev/costs/cloudwatch-logs-cost)
- [CloudWatch usage types decoded](https://cloudconsole.dev/costs/cloudwatch-usage-types)
- [Amazon GuardDuty pricing explained](https://cloudconsole.dev/aws-pricing/guardduty-pricing)
- [AWS data transfer cost between Availability Zones](https://cloudconsole.dev/costs/cross-az-data-transfer-cost)
- [VPC Flow Logs rejected traffic in Logs Insights](https://cloudconsole.dev/logs-insights/vpc-flow-logs-rejected-traffic)
- [Aurora I/O-Optimized vs Aurora Standard](https://cloudconsole.dev/costs/aurora-io-optimized-vs-standard)

---

Source: https://cloudconsole.dev/costs/vpc-flow-logs-cost

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