Loading today’s stories
Build1 distinct publisher3 min readUpdated
A dev.to breakdown pairs each idle AWS resource type with a measurement window and a monthly list price. Eleven such resources add up to about $1,016 a month.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
A dev.to post has published a per-type price list for idle AWS resources, pairing each type with the measurement threshold that makes "idle" a defensible claim rather than a hunch [1]. The reason to care is procedural: "we have idle resources" starts a debate, and "these eleven resources burn $1,340 a month doing nothing" starts a cleanup [3].
The framing worth stealing is that idle is not one condition. An unused NAT gateway, a load balancer at rest, and an EC2 instance at 4% CPU are three different problems with three different price tags and three different confidence levels about whether they are safe to touch [2].
Compute is the expensive category and the one most teams measure badly. The threshold offered is average CPU below 5% *and* negligible network traffic, sustained for 14 days, with both conditions required: a proxy at 2% CPU pushing gigabits is not idle, and one quiet week proves nothing [4]. The price is the full instance, with no discount for emptiness: about $70 a month for an m5.large that is 96% idle, about $280 for an m5.2xlarge, about $500 for a c5.4xlarge [5]. Verification is one CloudWatch get-metric-statistics call at an 86400-second period over 14 days, plus a NetworkPacketsIn check [6].
Databases get 14 days rather than 7, on the grounds that weekly batch jobs exist: DatabaseConnections maximum of zero across the window [7]. A db.t3.medium runs about $50 a month, a db.m5.large about $125, and Multi-AZ doubles both [8].
Then the fixed-price gear nobody remembers owning. A NAT gateway is $32.85 a month before a single processed gigabyte; threshold is BytesOutToDestination flat at zero for 7 days [9]. An ALB or NLB at rest is $16.43, a Classic $18.25; threshold is zero requests, or zero processed bytes for an NLB, for 7 days [10]. Confirm nothing still resolves to the DNS name before deleting, since the name outlives the service and the balancer itself is recreatable in minutes [11]. A separate finding while you are in there: a NAT gateway carrying S3 or DynamoDB traffic charges $0.045/GB for a path a gateway VPC endpoint provides free, which is overpriced rather than idle [12]. An EKS control plane with zero nodes bills $73 a month; threshold is node count zero for 7 days [13].
The honesty section is what makes the rest usable. A Lambda with zero invocations costs approximately nothing to leave alone, so it is a hygiene item (dead code, stale IAM permissions, possibly paid log storage) and not a savings line; the post's view is that any tool claiming dollar savings from idle Lambdas is padding the number [14]. Stopped instances are a storage problem, not idle compute, because their EBS volumes and Elastic IPs keep billing [15].
The portfolio example is where the argument lands: six sub-5% instances at about $420, two forgotten NAT gateways at $66, five idle load balancers at $82, two zero-connection databases including one Multi-AZ at $375, and one node-less EKS control plane at $73, for roughly $1,016 a month or about $12,000 a year from eleven resources a two-hour sweep can identify [16]. The arithmetic checks out against the unit prices: the components sum to exactly $1,016 [1], $66 is two gateways at $32.85 [2], $82 is five balancers at $16.43 [3], and $375 is one db.m5.large plus one Multi-AZ db.m5.large [4]. Annualised at twelve months it is $12,192 [5]. Compute plus databases account for $795, or 78% of the total [6]; the fixed network gear is $148, about 15% [7].
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
A representative mid-size account sweep: six sub-5% instances averaging m5.large-ish (about $420 a month), two forgotten NAT gateways ($66), five idle load balancers ($82), two zero-connection databases one of them Multi-AZ ($375), one node-less EKS control plane ($73). Total roughly $1,016 a month, about $12,000 a year, from eleven resources a two-hour metrics sweep can identify with defensible thresholds.
The post gives, for each idle resource type, the threshold that makes "idle" a defensible claim rather than a hunch, and the monthly dollar figure at us-east-1 list prices (early 2026, 730-hour month).
"We're paying for things that are running and doing nothing" is the most common cloud cost complaint and the least specific; an idle NAT gateway, an idle load balancer and a 4%-CPU EC2 instance are three different problems with three different price tags and three different confidence levels about whether they are safe to touch.
"We have idle resources" starts a debate, and "these eleven resources burn $1,340 a month doing nothing" starts a cleanup.
EC2 threshold worth defending: average CPU below 5% AND negligible network traffic, sustained for 14 days; both conditions matter because a proxy at 2% CPU pushing gigabits is not idle, and one quiet week proves nothing.
An idle instance costs its full price: an m5.large burns about $70 a month to be 96% empty, an m5.2xlarge about $280, a c5.4xlarge about $500. Idleness does not discount the meter.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Internally consistent, entirely self-asserted
Every number traces to one dev.to post with no external citation, pricing link, tool output or second publisher. What raises it above the floor is checkability and internal coherence: thresholds are expressed as named CloudWatch metrics with explicit windows, the CLI invocation is complete enough to reproduce, the stated pricing basis is declared (us-east-1 list, early 2026, 730-hour month), and the portfolio line items reconcile exactly with the unit prices given earlier in the same text. What holds it down: list prices are unverified in this cluster, the example account is hypothetical, and the aggregate ranking of where idle spend concentrates is asserted rather than measured.
No adoption signal in cluster
The cluster contains no release, deployment, benchmark, pricing-change, license-change or usage-disclosure event. The post is guidance about a practice; nothing in the supplied material shows any team running this sweep, any tool implementing these thresholds, or any account where the cleanup was executed. No adoption observations were recorded, so this dimension cannot be scored.
Mildly overstated, but self-policing
Slightly positive rather than strongly so. Overstatement sources: the lede's "$1,340 a month" for eleven resources exceeds the $1,016 the post itself computes for eleven resources; the annual framing (~$12,000) and the "two-hour metrics sweep" effort claim are presented with more confidence than a hypothetical account supports; and the concentration claim about where idle spend lives is generalised from a single invented portfolio. Working the other way, the post explicitly deflates a common inflation tactic by refusing to count zero-invocation Lambdas as savings and by moving stopped instances into a storage category, which is unusually restrained for cost-savings content and keeps the gap small.
Low visible promotional pull
Scored low, and only from what is observable in the supplied text: the post names no product, tool, consultancy or vendor, contains no call to action, pricing offer or affiliate framing, and its recommendations are executable with first-party AWS CLI calls the reader already has. It also argues against inflated savings numbers, which works against the usual incentive of cost-optimisation content. The residual is the ordinary self-published-developer-blog incentive toward attention-grabbing dollar figures, visible in the lede's unreconciled "$1,340" framing. No author affiliation or sponsorship disclosure is present in the cluster, so nothing beyond the text itself is assumed.
Moderate on method, low on magnitudes
Confidence splits by claim type. The methodology claims -- which metric, which window, why 14 days rather than 7, why CPU alone is insufficient -- are specific, self-consistent and independently reproducible, so they carry reasonable confidence. The dollar magnitudes and the portfolio total are single-source, unlinked list prices applied to a hypothetical account, and the cluster has no adoption evidence and no second publisher, so aggregate savings figures should be treated as an illustration rather than a measurement.
build
Two NAT Gateways nobody asked for: review cloud bills at 100x, not at this month1 distinct publisher
build
One ALB rule, zero legacy commits: shipping a feature around an app nobody will touch1 distinct publisher
build
Two mechanisms, one vCPU floor: why db.t3.micro cannot meet a 1-second RPO on RDS1 distinct publisher
build
Your agent thinks for two minutes and your Lambda pays for it1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
dev.to
1 article · August 20, 2026