3 ms·
We just went through an exercise on saving costs by shutting down resources in our development environments. I looked over our bill and found the following: -
by scarface74 7y ago
We just went through an exercise on saving costs by shutting down resources in our development environments. I looked over our bill and found the following:
- most of our costs for Aurora was data. Shutting down the database didn't save us too much of anything. We were already running some of the smallest instances. Aurora Serverless wasn't an option. It was missing features we needed.
- We only had a few small T* pet servers in DEV that we could shut down.
- Most of our greenfield projects are either Lambda (no cost when you aren't using, very cheap when you are) or Fargate (Docker). We could iterate through all of our clusters and set it to 0 at night and spin them back up as needed I guess
- You can't just shut down your ElasticSearch cluster.
- Do you really want to deprovision load balancers and your NAT gateway?
Did I mention that we have an entire team that works opposite hours than we do?
-