Scaling EC2

We run into this sort of industry wide experience where whenever somebody picks the size of a resource, they're going to pick one generally larger than they need. So we have to programmatically use data science and math to say, based on these utilization values, these are the sizes that would make sense for your business. And it's super important that we provide this capability from a technology standpoint because it would cost so much money to try to solve that problem. But when we talk to the finance folks, the conversations are more about reservations and savings plans. How do we correctly apply savings plans and reservations across a high percentage of our portfolio?