Full narration of the briefing. Click a section heading to jump the player to that moment.
Here is the paradox that defines life inside an AWS commitment. Everything your engineering team does well makes your contractual position worse. Right sizing, Graviton migrations, Savings Plan coverage, shutting down idle capacity. Every one of them lowers the spend that retires your commitment, and none of them lower the commitment.
So the better your FinOps team performs, the closer you drift to a shortfall.
Watch the burn down, not the bill. The number that matters between renewals is not what you spent, it is what retired your commitment, and those are different figures because of the measurement rules from episode two. So build a burn down chart on day one: committed amount, retired to date, and the run rate required to land on target. Review it monthly.
And know your own definitions, because whether support, professional services and marketplace count toward retirement varies by agreement, and most teams have never read their own answer.
Coverage is a monthly discipline. Published data has the median AWS customer achieving about fifteen percent effective savings on compute while the top decile clears forty, and the bottom quarter gets nothing at all. That gap is execution, not negotiation. New steady state workloads get a coverage decision within the quarter, not at renewal.
And remember the interaction: buying a Savings Plan lowers your billed spend, which slows your commitment burn down. Two commitments that each look prudent alone can be jointly ruinous, so model them together every time. One more thing to check quarterly rather than annually: whether your discount is bundled into the Savings Plan rate. If the standard and net values match in your cost report, bundling is on, and sizing new purchases off public rates will make you overbuy systematically.
Credits and marketplace need an owner. Credits expire, typically a year from issue, and they cannot be applied to support, marketplace, professional services or prepayments. An expired credit is a discount you handed back. And marketplace eligibility is now a live compliance item, not a one time decision.
Since the rules tightened, only software hosted entirely on AWS retires commitment, judged by invoice date. A vendor can lose that status mid contract, AWS provides no tracking, and the first you learn of it is a shortfall. So audit the marketplace lines quarterly against the current eligibility list, and keep the named vendors written into your agreement.
If you are running under, do the arithmetic before you panic. Shortfall is billed at your discounted rate, not at list, so being modestly underwater is often cheaper than the cure. The practical bands used by independent advisors: ten to fifteen percent under, do nothing, because you are still ahead of retail. Twenty to thirty percent, probably still do nothing.
Fifty percent under, renegotiate, but cut costs aggressively first so the new baseline is lower before you reopen the conversation. What you should not do is consume your way to the number. Spending money on capacity you do not need to avoid a true up is buying something worthless to avoid paying for something worthless, and it sets a higher baseline that AWS will anchor your renewal on. And if you genuinely need relief, ask for restructure rather than release.
The public record shows AWS reshaping commitments, stretching a five year deal into six with a slightly larger total, far more readily than it enforces. There is no known case of AWS taking a customer to court over a shortfall.
Then start the next negotiation early. Put the re-compete in the diary the day you sign. Refresh the alternative annually so it is mature rather than manufactured. And keep the evidence file warm: run rate, coverage, burn down, credit balances, uptime history, and every eligibility question and its answer.
Because the renewal is where AWS rebaselines on everything you achieved, with a discount percentage that can step down as easily as up. The buyer who arrives with three years of their own evidence and a live alternative gets a different conversation than the one who arrives assuming continuity, and the gap between those two conversations is worth more than any clause in the contract.
One last point. At Redress Compliance we run this discipline for clients year round and negotiate the renewal on pure contingency: twenty five percent of what we save you, and nothing saved, nothing paid. Final episode: the whole method run end to end on one estate.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a AWS negotiator