Cloud Usage Optimisation

If you are a cloud engineer or anyone related, you may have this situation.

A: “Are you using this RDS? there is a huge database, but never had I/O in the past 30 days”

B: “Oh, there are still in there? I thought I deleted it”

Don’t feel shame if you put yourself in B’s shoes. This is a common conversation in cloud management. Let’s see another one.

B: “The compute resource utilization is only 3% average, does your product really need that high spec of EC2?”

A: “Did you know we had a couple of spikes in a week? sometimes it hits 80%, I was about to ask you a higher one!”

How about this? Many cloud teams or departments usually put more value on business and can’t be against their request.

What you can do for the optimisation?

• Remove or do lifecycle the lost/forgotten resources
• Resizing (Find the resizing)

Remove or do lifecycle the lost/forgotten resources

This may be easier as there is rarely a contrary view if it is really wasting. Instead, we need to think about how we prevent forgotten (wasting) resources without being reviewed. (Regularly review on the entire resources)

Resizing (Find the resizing)

Rightsizing is not easy especially when the usage of resources (service) dramatically fluctuates over time…