AWS Account Management (Resource Management)
There is quite a bit of nuance in managing accounts in AWS. One particular issue I see come up is with managing account lifecycles (i.e. if a person wants to have "temp" accounts to provide for people to "play" and learn). This is simply not easily accomplished. However, there are procedural ways to deal with this if folks need this type of functionality. I have given it the following moniker: "account recycling"
The idea is that you would have different account types:
The idea is that you would have different account types:
- "core" accounts under the control of your master/payer account - and these do not get recycled.
- Long lived line of business accounts - hosting production, etc...
- long lived developer accounts - (still trying to work through how these would be managed)
- "burner" accounts - preset limits for usage, pre-determined length of time the account is available
The idea of the burner account is that you would create a "pool" of accounts that could be provided to end-users to consume for testing, then put back in to the pool and used by someone else. I believe that teams started to utilize this method due to the challenges of disabling/deleting/closing an AWS account.
The nice thing about the first tools listed here is that they also can "clean up" unused resources
There seems to be a few aws-nuke sources out there
https://github.com/rebuy-de/aws-nuke
(also, there is "cloud nuke" as it is more than just AWS now)
https://github.com/gruntwork-io/cloud-nuke
https://github.com/rebuy-de/aws-nuke
(also, there is "cloud nuke" as it is more than just AWS now)
https://github.com/gruntwork-io/cloud-nuke
Comments
Post a Comment