Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.porter.run/llms.txt

Use this file to discover all available pages before exploring further.

Deleting a cluster removes all applications and data running on it. This action cannot be undone.

​
Before You Delete

Before deleting your cluster:
  1. Back up any data stored in your applications or persistent volumes
  2. Export environment variables and secrets if you need them for future deployments
  3. Note your configuration if you plan to recreate the cluster later

​
Delete the Cluster

Porter needs the IAM role to delete resources. Delete the cluster first, then delete the IAM role. If you’ve already deleted the IAM role, you’ll need to delete resources directly from the AWS console.
1

Delete the cluster in Porter

  1. Navigate to the Infrastructure tab in the Porter dashboard
  2. Click Delete Cluster
  3. Confirm the deletion
This process may take up to 30 minutes.
2

Delete the IAM role

After the cluster is deleted:
  1. Navigate to CloudFormation Stacks in your AWS console
  2. Select the stack named PorterRole
  3. Click Delete
This revokes Porter’s access to your AWS account.
3

Verify cleanup

Check your AWS console to verify all resources have been removed:
  • EC2: No instances, load balancers, or security groups related to the cluster
  • EKS: No clusters remaining
  • VPC: No VPCs created by Porter
  • ECR: Container images may remain (delete manually if not needed)
Deleting resources via Porter may result in dangling resources. See Deleting Dangling Resources for cleanup guidance.

​
Troubleshooting Deletion

If deletion takes more than 45 minutes:
  1. Check your cloud provider’s console for any resources in a “deleting” state
  2. Look for dependencies that may be blocking deletion (e.g., load balancers with active connections)
  3. Contact us through the dashboard chat bot with your project ID
If resources remain in your cloud account after Porter reports deletion complete:
  1. Follow the Deleting Dangling Resources guide
  2. Check for resources in different regions than expected
  3. Look for resources with names containing your project ID
If Porter can’t delete because it can no longer authenticate to your cloud:AWS: Re-create the CloudFormation stack to restore the IAM role, then delete the cluster.GCP: Workload Identity Federation tokens are minted on demand and do not expire. If Porter can’t authenticate, either the porter-pool-* Workload Identity Pool or the porter-manager-* service account was deleted. Re-run the connect flow in Integrations → GCP to recreate them, then delete the cluster.Azure: Generate a new client secret and update it in Integrations → Azure, then delete the cluster.If you can’t restore credentials, you’ll need to delete resources manually.