Instances are not being terminated in time (extra AWS costs)

[mroy]

For a few days we have been trying to figure out why our AWS costs suddenly went up around March 20th, and we just found the answer: the EC2 instances are left in an unterminated state for a couple of minutes at the end of each run! 😱

This is a very serious bug, and I'm sure we're not the only customers being affected by this. 💸

We have many jobs which run very often (every 15 minutes, 30 minutes, hourly, etc.), and all of these incur an extra cost because of this bug (more than double the cost in some cases). It affects all jobs, but the impact is much less for those which run less often.

This screenshot is very explicit (y axis is the costs). It is from Cloudability, which we use to manage our AWS costs.

Please fix this!

[mroy · Accepted solution]

Nevermind, this was actually due to a reservation that expired. 🤦‍