You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@thoraxe raised the issue that catasb is not cleaning up after itself with ec2 provisioning.
There is no mechanism to clean up the various resources beyond the instance/volume that are provisioned.
Example: VPC, Security Groups, Subnets, etc.
This issue is tracking an ability to provide a "nuke_all.sh" or equivalent that a user can run to cleanup any resources created by catasb.
One thought for implementation is we could tag all resources with a "catasb" identifier then query the account for all resources matching the explicit tag and remove those for a nuke operation.
There is a concern of not making this part of typical workflow in a shared IAM account, as in a shared account it's expected that multiple users will be reusing the same VPC, Subnets, etc. In the shared use case we expect catasb to create a specific VPC once and for all users to reuse it. We wouldn't want individual users to "nuke" these shared resources after their testing is complete as it would adversely impact others in the account.
The text was updated successfully, but these errors were encountered:
@thoraxe raised the issue that catasb is not cleaning up after itself with ec2 provisioning.
There is no mechanism to clean up the various resources beyond the instance/volume that are provisioned.
Example: VPC, Security Groups, Subnets, etc.
This issue is tracking an ability to provide a "nuke_all.sh" or equivalent that a user can run to cleanup any resources created by catasb.
One thought for implementation is we could tag all resources with a "catasb" identifier then query the account for all resources matching the explicit tag and remove those for a nuke operation.
There is a concern of not making this part of typical workflow in a shared IAM account, as in a shared account it's expected that multiple users will be reusing the same VPC, Subnets, etc. In the shared use case we expect catasb to create a specific VPC once and for all users to reuse it. We wouldn't want individual users to "nuke" these shared resources after their testing is complete as it would adversely impact others in the account.
The text was updated successfully, but these errors were encountered: