I launched Cloud Nuke to make it easy to safely delete AWS resources in 3 clicks!
I've found that deleting idle & underutilized cloud resources is the quickest win to reduce spending on cloud bills. Additionally the workflow of deleting cloud resources often exist in Engineering teams but it is not well thought out and a single member scrambles to determine what needs to be deleted.
Building on clouds is getting easier, and conversely harder to delete since resources often depend on each other.
I don't think anyone is going to just throw keys in this willy nilly. Perhaps put up some instructions on how to make a one off user with the bare needed access that can be revoked after or something. Still a stretch tho.
Comments
I launched Cloud Nuke to make it easy to safely delete AWS resources in 3 clicks!
I've found that deleting idle & underutilized cloud resources is the quickest win to reduce spending on cloud bills. Additionally the workflow of deleting cloud resources often exist in Engineering teams but it is not well thought out and a single member scrambles to determine what needs to be deleted.
Building on clouds is getting easier, and conversely harder to delete since resources often depend on each other.
I don't think anyone is going to just throw keys in this willy nilly. Perhaps put up some instructions on how to make a one off user with the bare needed access that can be revoked after or something. Still a stretch tho.
Great suggestion, thanks!
The hard bit is checking that all the dependencies you're about to delete are not used anywhere else.
Agree. This is an early version of that pitch :)