How to deal with unused assets on AWS?

πŸ’Έ Rational

Using the public cloud will let you do experiments, iterate, test new services and new capabilities; it will unleash the potential of your teams to do innovation and, in the end, reduce the time to market with innovative products.

Cloud computing comes with a promise: “Pay as you go”.

In fact, this statement is partially true. However, it is only accurate if you take care – really care – of your active assets on your Cloud Service Provider (CSP).

It’s even harder to accomplish this with large agile, fast-moving teams, with many AWS accounts, and even harder with many teammates spread across continents. So you will need to put some guardrails and awareness to tackle the lack of visibility and constantly changing environments.

  • How often have you forgotten to turn off this EC2 or SageMaker Notebook in the exotic AWS region in this lab / sandbox AWS Account for the last two weeks?
  • How often have you realized you were in the wrong region in the AWS Console and provisioned some assets in the wrong place?

πŸ– Start saving now

Here is born πŸ’Έ unusd.cloud, a micro-SaaS product built for operational teams to bring cloud sustainability: cost awareness and waste detection in your effort to reduce costs and lower your carbon footprint. A win-win strategy.

It works like a garbage collector 🚚. On a schedule, you will receive a report of what you missed to turn it off in the following AWS resources types:

  1. EC2 Instances
  2. RDS Instances
  3. Glue DevEndpoints
  4. Redshift Clusters
  5. SageMaker Notebooks
  6. Detached EBS Volumes
  7. Unused Elastic IPs
  8. More to come

You will be able to put in an allowlist all legitimate assets to avoid any alert fatigue and get relevant reports.

Learn more and start saving now with (free forever for a single AWS account): πŸ’Έ unusd.cloud


comments powered by Disqus