Open the EC2-Other drawer

Synopsis

EC2-Other is a label, not an explanation

The name makes the charge look like one thing. It is usually a mixture: EBS, NAT gateway processing, data transfer, public IPv4, and other usage can all land there. The mix is different in every environment.

Observation

Open the drawer before discussing fixes

Start with the movement, not the total. Find the day it changed, then group by usage type, region, and linked account. That usually turns one vague line into a short list of charges worth investigating.

Evidence ruleBilling evidence establishes cost and usage. Configuration and operational evidence add context. Business cause remains an inference until the sources support it.

Diagnostics

A practical first pass

Filter to EC2-Other and switch to daily granularity. Group by usage type, then region and linked account. Move to the billing export when you need line items, resource identifiers, or a query another person can rerun.

Limits

The charge does not name the workload

A NAT usage line establishes billed volume, not workload identity. There is no universal free fix; endpoints, routing, inspection, and regional pricing change the decision.

Kulshan

Keep attribution honest

Kulshan surfaces cost movement and configuration context without claiming a workload identity the source data does not contain.

Keep reading

Follow the charge into the architecture

Yuvdeep Singh builds Kulshan and runs AWS cost investigations from Mission, BC. These notes distinguish observation, estimate, and inference.

← Back to Thinking