← All articlesInfra and cloud

Why is my AWS bill so high? Where to look first

Before cutting anything, find the line that moved. Cost Explorer gives it to you in four groupings, if you run them in the right order.

Julien Mauclair · ~5 min · intermediate
StackAWSCost ExplorerAWS CLI

When your AWS bill is high, open Cost Explorer and group by service over the last three months, then by usage type on the service that grew most, then by region and account, and finally by day to date the change. The console is free, with 13 months of history.

The common reflex is to hunt for resources to shut down at random. Do the opposite: first find which line moved and when, then act. What follows is a reading order, not a savings list. For the savings themselves, the overall method is in cut an AWS bill in half.

01The 30 minutes, in order

Cost Explorer refreshes its data at least once every 24 hours, so yesterday may be incomplete. Work on closed months, or on days at least 48 hours old.

Minutes 0 to 5Group by Service, monthly granularity, last 3 months
Minutes 5 to 15Filter on the service that grew most, group by Usage type
Minutes 15 to 20Same filter, group by Region, then by Linked account
Minutes 20 to 25Switch to daily granularity to date the change
Minutes 25 to 30Check the cost metric and write down the 3 lines to fix

1. By service: which item moved

Look at the month-over-month change, not the absolute amount. A service that is steady at a high level is an architecture question; a service that doubled from one month to the next points to a recent change, and that is the one to handle first. Write down the two or three services with the biggest gap.

2. By usage type: what you actually pay for

The service name says little. The usage type says a lot: instance hours, gigabytes transferred, volume storage, requests. It matters most for the EC2-Other line, which according to AWS covers EBS volumes and snapshots, Elastic IP addresses, data transfer, NAT gateways and more. AWS recommends breaking it down by grouping on usage type. Labels start with a region prefix and their exact form can vary, so check them in your own account.

If a NatGateway line stands out, the detailed math is in AWS NAT Gateway cost. If it is public IPv4 addresses, each one costs $0.005 per hour, in use or idle, which is $3.65 a month over 730 hours at the rate checked in November 2026.

3. By region and account: where it happens

A resource launched in a region nobody watches, or in a forgotten test account, only shows up with these two groupings. If an unexpected region appears, it is often the shortest path to a resource you can delete.

4. By day: when it started

A step-shaped increase points to a deployment, a new resource or a configuration change on a specific date: match it against your release history. A gradual slope points to traffic or storage growth, which you handle differently, through sizing or retention.

5. The right cost metric

By default, a Reserved Instance purchase shows up as a spike on the day you pay. The Amortized costs metric spreads those fees across the period, and Net unblended costs shows cost after discounts. Before concluding that a month blew up, make sure it is not an upfront payment or credits that ran out.

02Repeating the reading from the CLI

If you want a record of the analysis or to repeat it every month, the Cost Explorer API returns the same numbers. Note that unlike the console, each paginated API request costs $0.01, per the pricing page checked in November 2026. The commands below follow the get-cost-and-usage reference; the end date is exclusive.

read-bill.shBASHCopy
# Step 1: cost per service, month by month (August to October 2026)
aws ce get-cost-and-usage \
--time-period Start=2026-08-01,End=2026-11-01 \
--granularity MONTHLY \
--metrics UnblendedCost \
--group-by Type=DIMENSION,Key=SERVICE
# Step 2: EC2-Other broken down by usage type for October
aws ce get-cost-and-usage \
--time-period Start=2026-10-01,End=2026-11-01 \
--granularity MONTHLY \
--metrics UnblendedCost \
--filter '{"Dimensions":{"Key":"SERVICE","Values":["EC2 - Other"]}}' \
--group-by Type=DIMENSION,Key=USAGE_TYPE
# Steps 3 and 4: by region, day by day
aws ce get-cost-and-usage \
--time-period Start=2026-10-01,End=2026-11-01 \
--granularity DAILY \
--metrics UnblendedCost \
--group-by Type=DIMENSION,Key=REGION

The API accepts at most two groupings per request, for example service and region together. The exact EC2-Other service name in the filter may differ between accounts: list the values with aws ce get-dimension-values before filtering. These commands were not run against a real account for this article, so check the output before using them in a script.

03What usually turns up

Once you have the line, the cause almost always falls into a short list. In an r/aws thread, a developer who reviewed a small startup's account describes development servers running around the clock at near-zero load, a frontend hosted on EC2 and RDS databases nobody used anymore (Reddit thread). That is a testimony, not a statistic, but it matches the categories AWS puts under EC2-Other and the items covered in the 5 lines that wreck your bill.

The increase is on EC2-OtherGroup by usage type: EBS, snapshots, IPs, NAT, transfer
An unexpected region appearsList and delete the resources in that region
A spike on a single dayCheck for a reservation purchase or upfront payment
A gradual slope over monthsRevisit sizing, log and storage retention
Data transfer keeps risingLook for cross-AZ and internet-bound traffic

To stop discovering the increase at the end of the month, turn on AWS Cost Anomaly Detection: its AWS managed monitors automatically track all services and all accounts and alert you when spend breaks from the trend. And if you would rather have an outside look at the bill and the architecture, that is what Stralya does.

Worth noting

Prices and features checked against the AWS documentation on November 10, 2026. Check the Cost Explorer pricing page before automating API calls.

04FAQ

Why is my AWS bill higher this month?

Group by service over three months to see which one moved, then by usage type and by day to date the change. Also check the metric: a reservation purchase shows up as a spike unless you display amortized costs.

What is the EC2-Other line on my bill?

It groups EC2-related charges other than instance hours: EBS volumes and snapshots, Elastic IP addresses, data transfer, NAT gateways. To see which one weighs most, filter on EC2-Other and group by usage type in Cost Explorer.

Does Cost Explorer cost money?

The console is free. The API costs $0.01 per paginated request, and hourly granularity, which covers the last 14 days, is billed on top per usage record, according to the AWS pricing page.

In short

Read your bill in the order service, usage type, region and account, then day, and write down the three lines that moved most. Only then decide what to stop, resize or reserve.

Talk about your project ↗
Julien MauclairJulien Mauclair is the co-founder and CTO of Klickbee, where he builds the agency’s websites, tracking and AI automations, and develops Klickbee Tracking. He also runs Stralya, which designs and runs AWS infrastructure for scale-ups. Before that, he built the entire AWS infrastructure of an e-commerce business, since sold.

Read next