EC2 is one of the ‘big three’ of AWS spending. In many cases, the majority of your AWS bill is made up of EC2, EBS, and RDS consumption.
Reducing EC2 spending is easy - You don’t need fancy tools or in-depth analysis.
When a resource like an EC2 instance isn’t in use - shut it down. If your Proof-of-Concept (POC) project is complete - terminate the resources.
We recently worked through this process for a customer - you can see the results below.
How you do this is up to you. If you’re getting just started on the AWS platform, a simple script may be all you need.
If you’re like me and you value automation, you could consider building a couple of simple AWS Lambda functions which you could schedule to run via AWS CloudWatch Events.
To make things easier - tag everything that is taggable - even the resources which are not costing you any money. Come up with a corporate tagging strategy which you enforce via CloudFormation, AWS Config, and scripting.
Not having (or enforcing) a tagging strategy is one of the most common mistakes we see organizations (of all sizes) make. Even if you think you don’t need them right away - make sure you have tags defined - you can thank me later.
Like what you read? Why not subscribe to the weekly Orbit newsletter and get content before everyone else?