diff --git a/cloud-accounts/deleting-a-cluster.mdx b/cloud-accounts/deleting-a-cluster.mdx
index c852d9a..18367c9 100644
--- a/cloud-accounts/deleting-a-cluster.mdx
+++ b/cloud-accounts/deleting-a-cluster.mdx
@@ -49,6 +49,7 @@ Before deleting your cluster:
         - **EC2**: No instances, load balancers, or security groups related to the cluster
         - **EKS**: No clusters remaining
         - **VPC**: No VPCs created by Porter
+        - **EFS**: Porter-managed EFS file systems in the cluster VPC are deleted automatically during teardown
         - **ECR**: Container images may remain (delete manually if not needed)
       </Step>
     </Steps>
diff --git a/other/deleting-dangling-resources.mdx b/other/deleting-dangling-resources.mdx
index b258b3f..cdd5d0b 100644
--- a/other/deleting-dangling-resources.mdx
+++ b/other/deleting-dangling-resources.mdx
@@ -30,6 +30,10 @@ First, navigate to the **VPC** section in your AWS console to see the VPC's that
 
 Deleting the EKS cluster and associated auto scaling groups and launch configurations will ensure your EC2 nodes are also terminated; you can navigate to the **Instances** section on the EC2 dashboard to confirm.
 
+### Removing EFS File Systems[](#removing-efs-file-systems "Direct link to heading")
+
+Porter-managed EFS file systems associated with the cluster's VPC are deleted automatically during cluster teardown. If any EFS file systems remain (for example, because cluster deletion was interrupted), navigate to the **EFS** section in your AWS console, locate any file systems tagged with your cluster's VPC ID, and delete them along with their mount targets before removing VPC resources.
+
 ### Removing VPC Resources[](#removing-vpc-resources "Direct link to heading")
 
 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, and copy the VPC ID.