Show HN: Cut your AWS costs by stopping non-production resources when not needed
21–30 of 39 posts
Re: Show HN: Cut your AWS costs by stopping non-production resources when not needed
#22Are Naxes, SLawlor82 and mia2670 your friends? Or your accounts?
Re: Show HN: Cut your AWS costs by stopping non-production resources when not needed
#23Are Naxes, SLawlor82 and mia2670 your friends? Or your accounts?
Re: Show HN: Cut your AWS costs by stopping non-production resources when not needed
#24Re: Show HN: Cut your AWS costs by stopping non-production resources when not needed
#25Good luck on your project, though.
Re: Show HN: Cut your AWS costs by stopping non-production resources when not needed
#26The large amount of similar comments by new accounts makes this seem a bit iffy. Especially given that most of those comments were flagged. Good luck on your project, though.
Re: Show HN: Cut your AWS costs by stopping non-production resources when not needed
#27Users can override it by adding a custom tag to their resources to change the hours or not have the workload shut down. It's reduced our AWS costs tremendously.
Since we heavily push using terraform even for dev stuff, users can quickly re-spin up their instances, fix DNS records and the like with a terraform apply to get back up and running when they get back to their desk.
Re: Show HN: Cut your AWS costs by stopping non-production resources when not needed
#28At $WORK we use a tool named Cloud Custodian that does this, and can do so for almost all resources. We use it almost exclusively for EC2 and other resources in our dev account where at midnight EST it shuts down all resources. Users can override it by adding a custom tag to their resources to change the hours or not have the workload shut down. It's reduced our AWS costs tremendously. Since we heavily push using ter…
Another primary reason for them to prefer CloudPal is that most software engineers can use CloudPal without a lot of IaC or AWS knowledge such as tagging resources.