AWS won’t negotiate with hostages
I have AWS Business Support+ on three accounts in the same organization. Management, devops, and GovCloud. I wanted to cancel two of them and keep GovCloud.
I started with the management account. The cancellation flow showed a retention offer: “Keep Business Support+ at 40% off — $29/mo minimum for 12 months.” Full Business+ features at a fraction of the normal minimum. Good deal. I filed it away.
Before accepting, I wanted to know if the other accounts would get the same offer. I checked devops and GovCloud — neither showed an offer. My first theory: the management account owns the billing relationship, so AWS is negotiating with the boss.
Then I tried to actually cancel devops first, since there was no offer to think about. Hard error:
AWS Support plans require a minimum 30-day subscription. Because you’re still within this subscription period, we can’t process your request right now.
GovCloud — same error.
That killed my billing-relationship theory. The management account wasn’t special because it’s the org owner. It was special because it was past the 30-day subscription lock. The other two weren’t. AWS didn’t show them an offer because they couldn’t actually cancel — and AWS knew it.
The 30-day minimum isn’t just a billing constraint. It’s a funnel filter. It separates real churn signals from noise. On the other side of that filter, AWS rolls out the retention carpet — because now the threat is credible.
This has nothing to do with spend. The management account spends $3/month on infrastructure. The devops account spends $500/month. The low-spend account got the offer. The high-spend account got the error. The gate isn’t “how valuable is this customer” — it’s “can this customer actually leave right now.”
Every SaaS cancellation flow works this way if you look hard enough. The ones that show you a retention offer before you’ve passed the contractual exit point are burning money on people who can’t churn anyway. AWS doesn’t burn money.
If you’re planning support plan downgrades across an AWS org: stagger your subscription changes so you’re always past the 30-day lock when you want to cancel or harvest an offer. The cookies are in the lobby, but the door has to be unlocked before they’ll offer you one.