← sources

TIFU by ignoring MySQL 8.0 EOL and blaming my Fargate bill spike on the wrong thing

source: reddit (reddit:aws)published 2026-08-31 17:15ingested 2026-09-01 02:39

retained text

So a while back I got the AWS email saying MySQL 8.0 was hitting end of standard support and moving to Extended Support pricing. I read it. and I was *planning* to upgrade. I just didn't think the Extended Support charges would be that big a deal, so I didn't treat it as urgent...(big mistake)

Then comes the kick in the ass

Right around the same time my AWS Budget alerts started firing. I was expecting that, but not because of Extended Support. We had bumped the resources on one of our Fargate containers because we were troubleshooting a process that kept spiking CPU.

So I confidently told myself "yeah that's probably the Fargate thing, makes sense" and didn't give it a second though

\~20 days later I finally log into Billing and see a $600+ charge that is absolutely not explained by the container scaling. As soon as that though crossed my mind, I suspected that I fucked up about the Extended Support

And surely enough, there it was in the detailed bill. I'd been paying Extended Support fees the whole time I was blaming Fargate for the bump.

100% my bad. I knew about the EOL, I just underestimated the pricing impact AND let a legit concurrent scaling event mask the real cost driver. Two wrong assumptions stacked on top of each other.

I opened a support case asking AWS to help me with part or all of the Extended Support charges for that \~20-day window. My reasoning was that I was aware of the EOL but misjudged the pricing impact and the source of my budget alerts, and I'd already fully remediated (upgraded the RDS instances), and the alerts were genuinely masked by a real Fargate scaling event.

The response was: nope. They said it's not possible to help me.

Fair enough I guess...

So I'm posting this partly to vent and partly as a PSA: **if you get that MySQL 8.0 EOL email, upgrade as soon as possible or prepare yourself for a surprise in your bill**

For context, we're a really small company. This $600+ charge came from just 2 RDS small instances. Usually our **entire bill** comes at $400\~$500, so this mistake basically doubled our cost for the month.

At least I gave them two suggestions:

1. P**ut the estimated monthly cost impact in the Extended Support notification email** (I know they're not obligated to do any of that, but for sure seeing "**your bill may increase by $600+"** would definitely have gotten my attention)
2. Make budget alerts distinguish between new charge types and usage increases. A spike caused by a new fee and a spike caused by scaling a container look identical in the alert (once again, I know, 100% my fault, okay?)

Anyway, TIFU, and now both my boss and manager are pissed at me. Has anyone else been in a similar situation, or am I the only idiot who’s managed to do this?

  
UPDATE: Including examples of how the email could be

https://preview.redd.it/isn52j7d2smh1.png?width=743&format=png&auto=webp&s=082e3c06012e0ccb3d21ea92844136295b52f5f9

https://preview.redd.it/9b8rhar73smh1.png?width=743&format=png&auto=webp&s=05db839a169f1b324a21379b734fe79958094f4b

document fetched 2026-09-01 00:37 · canonical https://reddit.com/r/aws/comments/1w3k729/tifu_by_ignoring_mysql_80_eol_and_blaming_my