AWS ECS & EC2 hibernation for cost savings
Gorilla empowers B2B utilities with data-driven solutions for pricing, forecasting and reporting. Our product is cloud-native, and we’re all-in on Amazon Web Services (AWS).
We make heavy use of AWS ECS and Dask for scheduling long-running calculations. Many of our ECS clusters are only used during office hours, though, meaning they can be shut down at night for cost savings. More generally, periods of inactivity can be detected based on the arrival rate of jobs in a cluster’s queue, the cluster’s CPU usage, and other metrics.
This kind of cost optimization is a recommended practice, but we haven’t seen many examples of how to actually implement it. Considering that every product is slightly different, such examples may not generalize well.
In this blog post, we show how we built our in-house hibernation system for cost savings, implemented in Serverless Framework, and geared towards services running on AWS ECS. It likely won’t work as-is with your particular service, though. We simply want to share this as an example to be adapted.
