3 years ago

Category: Jenkins, logging, github, yaml

In most organizations, a common pattern of using AWS is to have multiple accounts for production, staging, development, etc. In such a setup, it is inevitable to lose track of various experimental AWS resources instantiated by your developers. Eventually, you are billed for these resources; even though this could have been avoided if you were proactively identifying and deleting all such resources.

Our organization recently created an internal Jenkins wizard on top of aws-nuke to help developers clean up their AWS accounts.

Your developers must be able to use this default mode to save some of their resources from deletion if required.