Yeah, do not do this. You'll end up with a $1000 bill from Amazon becuase you forgot to shut it down and discover very quickly they don't care at all once they already have your money.
Yes, you can set up a budget but it's only used for alerting. The services will happily keep running and building up to that 1k bill if you miss the alerts or don't react to them.
Wow, they really made it complex, didn't they? On one hand they advertise how anyone can spin up a VM and connect to it but you still need to do some serverless black magic to keep your budget in check. Anyway, thanks for the heads up. I'll definitely try that out.
It seems to follow their practice of building the “API first” solution. By the way, a lambda/programmatic solution allows you to disable lower priority resources and retain higher priority resources. It’s a lot of effort, but it’s incredibly flexible.
Yeah, that's not a terrible idea. But I work with tools that could, like, cut my thumbs off... I feel like this is still pretty nerfed up by comparison.
Setting up a CloudWatch alert to email you when the bill goes over $10 in 6 hours is a good measure (of course you probably won't get the alert for 24 hours because of Amazon's billing update delay).
I dunno if they'd eat that cost again, and I wouldn't try it on purpose.
But keep in mind that they have an incentive to do this: it's the cost of acquiring users without scaring them about a possibly humongous bill.
I now have better billing alarms set.