- Newest
- Most votes
- Most comments
I understand your frustration with being unable to delete AWS Kubernetes Services (EKS) and continuing to incur charges. This is a common issue that often occurs due to dependencies that prevent resource deletion.
To resolve this issue, you'll need to:
- Identify and remove all resources associated with your EKS cluster. These might include:
- EC2 instances
- Load balancers
- NAT gateways
- Network interfaces
- VPC endpoints (especially "requester-managed" endpoints)
-
Pay special attention to network interfaces and VPC endpoints, as these are often the culprits preventing deletion. Some of these might be "requester-managed" endpoints created by AWS services.
-
Check for any resources still running in your VPC using:
- The billing console or AWS Cost Explorer to identify what's generating charges
- The EC2 console's Elastic Network Interfaces section to find interfaces attached to your VPC
- After removing all dependencies, wait a few minutes for AWS to clean up associated resources automatically, then try deleting the EKS cluster again.
Regarding your refund request, AWS does consider refund requests on a case-by-case basis. To request a refund:
- Open the AWS Support Center
- Create a support case under "Account and Billing Support"
- Select "Billing" as the issue type
- Provide details about your situation, including that you've been unable to delete resources despite attempts
While there's no guarantee of a refund, AWS Support can help identify any hidden dependencies preventing deletion and may consider your refund request, especially if this is your first time encountering such an issue.
Sources
Delete unused services | AWS re:Post
Aws free tier - Unexpected Charges for EKS Usage - Request for Assistance | AWS re:Post
Request for Refund Due to Unintended AWS Service Charge Within 7-Day Right of Withdrawal | AWS re:Post
I can not delete my vpc | AWS re:Post
Relevant content
asked 2 years ago
- AWS OFFICIALUpdated 4 years ago
