Vacuum your AWS account of unused resources to save you 💲💲!!
To run:
vacuum all
▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
░░░░░░░░░░ ▒▒▒▒ ▒▒▒▒▒▒
░░░░░░░░░░░░░░ ▒▒▒▒ ▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒ ▒▒▒▒
░░░░▒▒▒▒▒▒▒▒▒▒▒▒▒▒░░░░ ▓▓▒▒▒▒ ▒▒▒▒
░░░░░░░░▒▒▒▒▒▒▒▒▒▒░░░░░░░░ ▒▒▒▒ ▒▒▒▒
▒▒░░░░░░░░░░░░░░░░░░░░░░▒▒ ▒▒▒▒ ▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒ ▒▒▒▒
░░▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒░░ ▒▒▒▒ ▒▒▒▒
░░░░░░▒▒▒▒▒▒▒▒▒▒▒▒▒▒░░░░░░ ▒▒▒▒▒▒ ▒▒▒▒
░░░░░░░░░░░░░░░░░░░░░░░░▒▒▒▒▒▒▒▒ ▒▒▒▒
░░░░░░░░░░░░░░░░░░░░░░░░▒▒▒▒▒▒ ▒▒▒▒
░░░░░░░░░░░░░░░░░░░░░░░░░░ ▒▒▒▒
░░░░░░░░░░░░░░░░░░░░░░░░░░ ▒▒▓▓
░░░░░░░░░░░░░░░░░░░░░░░░░░ ▒▒▒▒
░░░░░░░░░░░░░░░░░░░░░░░░░░ ▒▒▒▒
▒▒░░░░░░░░░░░░░░░░░░░░░░▒▒ ▒▒▒▒
▒▒▒▒▒▒▒▒░░░░░░░░░░▒▒▒▒▒▒▒▒ ▒▒▒▒
██▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒██ ▒▒▒▒▒▒▒▒
████ ▒▒▒▒▒▒▒▒▒▒ ████ ▒▒▒▒▒▒▒▒▒▒▒▒
████ ░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░
░░░░░░░░░░
Even when using infrastructure as code tools like Terraform it is easy to leave behind relic resources such as EC2 EBS volumes and ENIs.
These relics cost you money! Enter vacuum, to deep clean your account!
To run all the commands and thoroughly deep clean your account run vacuum all
By default, regions eu-west-1
and eu-west-2
will be vacuumed. You can override this using the regions flag:
vacuum all -r "us-east-1,us-east-2"
Dont worry Vacuum will ask you to confirm removal before deleting anything!
Clean up available EC2 volumes using the volumes
command. The volumes are not attached to anything and are just sitting there lining Jeff Bezos's pocket. No one wants that so clean them up using:
vacuum volumes
By default, regions eu-west-1
and eu-west-2
will be vacuumed. You can override this using the regions flag:
vacuum volumes -r "us-east-1,us-east-2"
Clean up available ENIs using the enis
command. The ENIs are not attached to anything and are just sitting there costing you money, clean them up using:
vacuum enis
By default, regions eu-west-1
and eu-west-2
will be vacuumed. You can override this using the regions flag:
vacuum enis -r "us-east-1,us-east-2"
Clean up dangling security group rules which were created by K8s aws-load-balancer-controller
via relevant annotations (e.g. resulting in descriptions like kubernetes.io/rule/nlb/health=a6ba247c8d1e94b0691e80c29a769193
). These security group rules are created during automatic creation of NLBs and can be left dangling if the relevant services have not been shut down gracefully. Eventually you will hit the maximum number of allowed rules within your security group and need to perform a cleanup. To clean them up automatically use this:
vacuum securityRules
By default, regions eu-west-1
and eu-west-2
will be vacuumed. You can override this using the regions flag:
vacuum securityRules -r "us-east-1,us-east-2"