The SSLT Secure Egress use-case deploys a number of components to your AWS account in the region you specified. This includes:
- EC2 instances, keypairs, security groups, volumes
- An NLB and target group
- VPCs, subnets, route tables, nat gateway, etc
- EIPs and network interfaces
- An S3 bucket and contents
- IAM roles and policies
- KMS keys
You can see a listing of many of these items by searching with the AWS tag editor for ‘Owner:Aviatrix-SelfService’
To clean up the infrastructure in your account, complete the items in the following order:
- Remove ‘termination protection’ from the EC2 instances ‘AviatrixController’ and ‘aviatrix-avx-ec2-spoke-selfservice’
- Terminate all instances
- Delete the NLB ‘AVX-SelfService-EC2-NLB-Egress’
- Delete the Target Group ‘AVX-SelfService-EC2-TG-Egress’
- Delete all Keypairs with ‘selfservice’ in the name
- Delete the nat gateway aviatrix-selfservice-vpc-secure-egress-us-east-2a
- Delete the controller and copilot network interfaces
- Release Elastic IP addresses
- Delete all of the security groups
- Delete ‘controller_vpc’ and ‘aviatrix-selfservice-vpc-secure-egress’
- Empty the selfservice s3 bucket
- Delete the ‘AviatrixSelfServiceDeploy’ cloudformation stack
- Delete the iam policies '*-aviatrix-role-app-app-policy' and '*-aviatrix-role-ec2-assume-role-policy'
- Delete the iam roles '*-aviatrix-role-app' and '*-aviatrix-role-ec2'
Note that some resources are dependent on others and may need time to fully delete before moving onto the next step.
If these instructions do not work for you or you have any questions, start a conversation here so we can help you.