Skip to content

VPCE and Associated Network Interface are in loop and not deleting: Redshift

0

Hi ... I am very new to RedShift cluster , two days before I created a RedShift Cluster and wanted to connect with my Spyder(Anaconda). However in order to connect the two components, I created VPCE but all in vain. The two components did not interacted.

At the end of my exercise I deleted RedShift Cluster but its associated VPCE and associated Network Interface did not get deleted. Now its continuously costing me..

If anybody can help...

asked 7 months ago98 views
1 Answer
0

It sounds like you're experiencing a common issue with requester-managed VPC endpoints that can occur when deleting Redshift clusters. Even though you've deleted the Redshift cluster, the associated VPC endpoint and network interface may still remain, causing ongoing costs.

This situation typically happens because the VPC endpoint is of the "requester-managed" type, which means it's managed by AWS and cannot be deleted directly by the user. These endpoints are often created automatically when you set up certain AWS services, including Redshift.

To resolve this issue, you should check if there are any remaining Redshift resources that might be keeping the VPC endpoint alive. Specifically, look for any Redshift workgroups that may still exist. Sometimes, deleting the workgroup can trigger the deletion of the associated VPC endpoint.

If you can't find any remaining Redshift resources, you may need to do a thorough check of your AWS account for any other services or resources that could be linked to this VPC endpoint. This could include things like RDS Proxy, Lambda functions connected to the VPC, or other services that might use VPC endpoints.

If you're still unable to identify the source, you can try to trace the creation of the VPC endpoint using CloudTrail's event history, provided it was created within the last 90 days. This might give you clues about which service created it.

As a last resort, you may need to contact AWS Support for assistance in identifying and removing the lingering resources. They have tools to help track down these kinds of dependencies that aren't always visible to users.

Remember, it's important to be thorough when cleaning up AWS resources to avoid unexpected costs. Always double-check for associated resources when deleting services like Redshift clusters in the future.

Sources
There was an error deleting your endpoints | AWS re:Post
Cannot disassociate or delete an elastic IP address, and cannot delete VPC endpoint | AWS re:Post
I cannot delete a VPC Endpoint | AWS re:Post

answered 7 months ago
EXPERT
reviewed 7 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.