Deleting Dangling Resources

When you delete your project or clusters, Porter automatically destroys your resources so you don't get charged for any unused resources. Sometimes, this automatic destruction occurs only partially and results in dangling resources. This is a guide with specific steps on how to delete these resources for each cloud provider.

AWS

Deleting VPC

Navigate to the VPC section in your AWS console to see the VPC's that are currently in use. Select the VPC that belongs to the cluster you've provisioned, then click Actions > Delete VPC.

Delete VPCDelete VPC

AWS might warn you that the VPC cannot be deleted due to existing NAT gateways or network interfaces that are in use. Click on the text NAT Gateways to view the NAT gateway in use. Once you delete the NAT gateway, you'll be able to delete the VPC.

NAT gatewayNAT gateway

Deleting Elastic IP

Head to the Elastic IP addresses section in the VPC tab. Select the EIP of the cluster you have deleted and click Actions > Release Elastic IP Addresses.

Deleting EKS

Head to the EKS tab, select the cluster and click Delete .

EKSEKS

Deleting Nodes

It sometimes occurs that even after the EKS cluster has been deleted, the actual EC2 machines comprising the cluster do not get deleted properly. Navigate to EC2 > Autoscaling Groups and ensure that autoscaling groups attached to your cluster has been deleted. If this autoscaling group persists, AWS will continue to spin back up your nodes even after manual deletion.

Once you've deleted the Autoscaling Group, head to EC2 > Instances and delete all the nodes.

Autoscaling groupAutoscaling group