CloudCycle – Set lifecycle for your cloud resources to avoid surprising costs

RMAG news

I have recently forgot to Turn off / Terminate two ec2 instances running m5x.large and t3.medium that runs about 1 month and I just received a notification of my AWS monthly bill and shocked me!

At the first place I thought my account was hacked, But turns out that I just left two AWS EC2 Instances running. 🥲😔

So, that’s why I came up with a basic solution and share it. So now, whether I forgot to turn it off / terminate a running AWS Resources, I don’t have to worry about it anymore, if I have properly set the desired lifecycle of my cloud resources.

I have created a lambda function which get’s executed every 15 minutes to check if the supported resources are due to termination or not.

Now, if you or your team forgot to terminate cloud resources, the CloudCycle will do the job for you.

Tools & Language used

Golang – Since lambda function bills will be based on the duration of execution. At first, I developed this by using python and I have realized that I need to consider it’s performance and execution time.

Terraform – Used only for deployment and examples.

Objective

My objective with CloudCycle is to automatically cleanup supported resources based on the specified duration or lifecycle through resource tagging, And to support the commonly used resources that causes AWS Bills to grow even though the cloud resources is not needed anymore.

No more story telling!

For complete documentation and project link, you can proceed directly to my GitHub repo below.

https://github.com/redopsbay/cloudcycle

This repo is open for contributors!!! Some documents and cloud resources are currently WORK-IN-PROGRESS

Benefit’s

No nightmare’s, No poverty! 😂🤣

Please follow and like us:
Pin Share