teardown-rosa-aws

To clean up stuck ROSA cluster resources, you can run targeted scripts that remove leftover load balancers, VPC endpoints, ENIs, and security groups blocking Terraform destroy. This ensures the AWS teardown process completes without manual remediation.

The best way to fully destroy a ROSA HCP cluster is to run Terraform destroy against the deployment state, clean up any stuck infrastructure, and then verify orphaned VPC, IAM, OIDC, and NAT resources are completely removed.

Yes, you need Terraform state to execute the ROSA cluster destruction process. The teardown workflow applies Terraform destroy against the existing deployment state and requires AWS CLI access to manage and remove the underlying AWS infrastructure.

Your ROSA Terraform destroy leaves dangling VPC and IAM resources because stubborn leftover infrastructure like load balancers and VPC endpoints can block normal deletion. Running ROSA-specific cleanup scripts removes these dependencies to allow full deletion.

To verify an AWS VPC is completely removed after a ROSA teardown, run a post-destroy verification workflow that checks for orphaned VPC, EIP, IGW, subnet, and load balancer resources to confirm no billable infrastructure remains behind.