Reserved Instances are a really quick and easy way to blow a few million with one click.
Europe (Frankfurt), 3 year, all-upfront, Windows w/ SQL Enterprise, Dedicated Tenancy, u-12tb1.112xlarge instance at $5,926,378 up-front.
The discounted $225/hour rate for it disappears into the background noise.
(No, I'm not willing to test it to find out if it actually works)
[1] https://aws.amazon.com/ec2/pricing/reserved-instances/pricin...
(should have read the licensing issue - still you can buy 2 and the consultant)
A couple months ago, folk were grumbling about a non-deterministic failure in the main build CI plan, for the N'th time without attempting to do anything about it. So, I proceeded to queue up dozens of jobs at a time, every 15 minutes for several hours, until I had several failures worth of interesting logs. I also had the interest of several other software teams, wondering why the entire CI pipeline was clogged up.
It turned out someone years ago had written a cron job that would asynchronously delete every file on the build server older than a week, every hour on the hour. At some point some build artifacts got added that came from a cached copy on a remote server rather than locally built, and their modification timestamps were preserved. Any jobs that happened to be running while on the hour would have those files mysteriously disappear without a trace. Oops!