- Newest
- Most votes
- Most comments
It appears you're facing a common issue where you can't delete a VPC due to a VPC endpoint dependency, but the endpoint itself doesn't seem to exist when you try to delete it. This situation often occurs with requester-managed VPC endpoints, which are created and managed by AWS services on your behalf.
To resolve this issue, follow these steps:
-
First, identify which AWS service is associated with this VPC endpoint. Common services that create requester-managed endpoints include RDS Proxy, ElastiCache Serverless, or other AWS PrivateLink-enabled services.
-
Once identified, locate and delete the underlying AWS resource that's using this VPC endpoint. For example, if it's an ElastiCache Serverless cluster or an RDS Proxy, delete that resource.
-
After deleting the associated resource, wait for a few minutes. AWS should automatically clean up the requester-managed VPC endpoint and its associated network interfaces.
-
If you're still unable to delete the VPC after this, check for other AWS services that might be using the VPC or creating requester-managed resources.
-
As a last resort, if you can't identify the service or resource causing the issue, you may need to contact AWS Support. They can provide account-specific guidance and help identify any hidden dependencies in your setup.
Remember, when dealing with requester-managed resources, the key is to focus on removing the underlying service or resource that's creating them, rather than trying to delete the endpoints directly. This approach should allow you to successfully delete your VPC once all dependencies are removed.
Sources
Unable to Delete VPC Due to Requester-Managed VPC Endpoint and Network Interface Dependencies | AWS re:Post
I cannot delete a VPC Endpoint | AWS re:Post
Relevant content
- asked 8 days ago
- asked a year ago
- asked 6 days ago
- AWS OFFICIALUpdated 10 months ago