Cloud Cost Optimization Library
Practical guides, case studies, and FinOps insights for cutting cloud bills without slowing your team down.

Your Bedrock Line Is Not Your AI Bill: Claude Bills as AWS Marketplace
Claude on Amazon Bedrock is not billed as Amazon Bedrock. AWS sells it as a third-party model through AWS Marketplace, so the charges land under the AWS Marketplace billing entity, one service per model, and a report filtered to "Amazon Bedrock" misses every dollar of it. On one AWS Organization I run, that filter showed 0.4% of the model spend. That classification decides more than the report: general promotional credits exclude Marketplace, and until 19 August 2026 Cost Anomaly Detection ignored it, which is why one AWS user's $30,141.33 of Claude inference charges in April raised no alert. Two more gaps are program rules that apply whatever the billing entity: reseller private pricing covers Bedrock for Amazon Nova and Titan only, and Savings Plans have never covered Bedrock. Here is what AWS's own documents say, the two filters that give you one honest AI number, which discounts and credits actually reach the line, and the order to check them in before you report AI spend or sign a commitment.

What Is the Maximum AWS Savings Plan Discount? The Answer Depends on the Plan
The 72 percent discount everyone quotes is a product property, not a price. It belongs to EC2 Instance Savings Plans, which lock one instance family in one region; the flexible Compute Savings Plan most teams actually buy is capped at 66 percent, and the newer Database and SageMaker products at 35 and 64. AWS's own rate table priced m6a.large at 27 percent on the 1-year no-upfront plan and 54 percent at the absolute 3-year all-upfront maximum, where the family-locked product paid exactly the same. Here is where each ceiling lives, why your rate diverges from any headline, the ten-minute lookup that replaces the guesswork, and the order of operations that keeps the commitment sized on your bill instead of AWS's best case.

AWS EDP vs Savings Plans: Which Commitment Comes First?
They are not competitors: Savings Plans discount the rate you pay per hour of compute, while an EDP (now sold as a Private Pricing Agreement) is a negotiated percentage off almost your whole bill in exchange for a multi-year total-spend commitment, typically from around $1M a year. They stack, and the order matters. Optimize first, then buy Savings Plans against the baseline that survives, then size the EDP commitment on that optimized number, because both commitments bill you whether you use them or not.

My AWS Bill Grew 40%. Revenue Grew 20%. Here's the Math I Showed the Board.
A bill growing twice as fast as its revenue looks like a failure waiting for a meeting. Last quarter I decomposed exactly that gap for a client board: of the extra $24,000 a month, $17,000 was customers and one AI feature doing what the business asked, $5,000 was fixable waste, and $2,000 was a commitment gap that would have sat there for years. Cost per customer had moved from $300 to $311 while the bill grew 40 percent. The split turned a hostile question into a 60-day plan worth $7,000 a month. Here is the arithmetic: the three buckets, the consoles that populate them, why the 29 percent waste headline does not apply to a growing bill, and the one slide that ended the argument.

What Should AWS Cost? The Benchmarks That Survive an Exec Meeting (2026)
Ask a room what AWS should cost and you will get five numbers: 5 percent of revenue, 10 percent, 29 percent wasted, half the bill recoverable if you would only repatriate, and AWS's own efficiency score. Nearly all of it is quoted by people who never opened the source. This is the briefing I wish someone had handed me before my first cloud review: the ranges that survive contact with an exec meeting (cloud at roughly 5 to 15 percent of revenue depending on what you sell, self-estimated waste at 29 percent across Flexera's 753 respondents, 98 percent of FinOps teams now carrying AI spend), the quiet way each number lies, and the five slides I bring instead of an industry average. The benchmark that ends arguments is your own cost per customer.

How to Stop AWS Charges: Find What Is Billing You, Shut It Off, Keep It Off
AWS keeps charging you because resources bill until they are deleted, not stopped. Here is the sequence that actually ends the charges: read the bill by usage type, stop or delete whatever sits behind each line, verify on the next day of usage data, and close the account properly if you want everything off.

AWS Savings Plans vs Reserved Instances: What Reddit Actually Says
Most Reddit threads on Savings Plans vs Reserved Instances land on the same answer: buy Compute Savings Plans first, keep Standard RIs for steady fleets that need guaranteed capacity. That advice is still right. What has changed is everything around it. AWS launched Database Savings Plans on 2 December 2025, the Standard RI discount is 72% and not the 75% half the internet still quotes, and the resale escape hatch that gets cited in every thread requires a bank account with a US address. This is what the r/aws and r/FinOps threads get right, what they get out of date, and what the AWS documentation says when you check it.

How to Reduce Your AWS Bill: A 30-Day Step-by-Step Guide
To reduce your AWS bill, work in this order: turn on Cost Explorer and daily CUR to find where the money actually goes, delete idle and orphaned resources, right-size overprovisioned compute and storage, then buy Savings Plans against the baseline that survives. Most accounts that have never been optimized give up 20% to 35% within 30 days, and the first two steps cost nothing and carry no production risk. Buying commitments first is the common mistake: it locks in the waste you have not removed yet.

AWS FinOps Tools: The Complete Free Native Stack
You can run a real FinOps practice on AWS native tools alone. Cost Explorer gives you the interactive view, Cost and Usage Reports give you the queryable truth, Budgets and Cost Anomaly Detection give you the alerts, and Compute Optimizer gives you the right-sizing candidates. Almost all of it is free, with three specific exceptions that catch people out. Third-party tooling earns its price later, when you need chargeback across many teams or continuous automated action, not on day one.

Sync Cursor Teams Spend to Your Warehouse with Airbyte
An open source Airbyte connector for preserving Cursor Teams spend, usage, member, and event data before the API retention window rolls forward.

Your AI Bill Is Split Across Bedrock, OpenAI, and Azure. Nobody Can Explain It.
98% of FinOps teams now manage AI spend, and the number one capability they are asking for is the one no tool delivers: granular token and GPU visibility. Here is how to build it yourself.

My AWS Bill Suddenly Doubled: The 20-Minute Triage
When an AWS bill spikes overnight, the cause is almost always one of six things. Here is the exact order to check them in, and how to stop the bleeding in the same billing cycle.

How Much Does a FinOps Consultant Cost in 2026? Real Numbers
Published market rates, the three pricing models, and an honest rule of thumb for when hiring cost help pays for itself, and when it does not.

The $198K/Year AWS Bill Hiding in "EC2-Other"
A rising "EC2-Other" line turned out to be database backups taking the most expensive possible route to S3, then paying premium storage rates on arrival. Two config changes, zero code, zero downtime: $16,500/month recovered.

The Bedrock Bill Trap: Capping GenAI Costs on AWS in 2026
GenAI spend is forecast to grow 80% in 2026, and most of it lands on the AWS bill before anyone notices. Here is the FinOps playbook for Amazon Bedrock: prompt caching, model laddering, inference profiles, and chargeback that actually works.

18 AWS Cost Optimizations We Find in Every Audit
The same waste patterns show up in nearly every AWS account we review. Here are the 18 fixes, sorted by effort, that consistently recover 30 to 35% of cloud spend.

The Cloud Budget You're Already Sitting On
Most tech companies waste 30 to 35% of their AWS spend without knowing it. Here's the framework for reclaiming it and what to do with the capital.

FinOps Framework 2026: What Changed and What It Means
The FinOps Foundation just released its biggest framework update yet. Here is what actually changed, and the three moves AWS-heavy teams should make right now.

AWS Savings Plans vs Reserved Instances 2026: Which to Buy
A practical comparison of AWS Savings Plans and Reserved Instances for 2026, with decision frameworks, pricing examples, and a recommended purchase sequence for every team size.

7 AWS Cost Cuts You Can Make This Week (2026 Playbook)
A ranked, implementation-first checklist for reducing AWS spend in 2026 by focusing on the fastest, highest-impact savings opportunities first.

Case Study: E-commerce Saves $175K/yr on AWS in 60 Days
How a technology services company unlocked six-figure annual savings through automated commitment management.