- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Thanks everyone, the issue has been resolved. there was a dependency of RDS proxy because of which VPC endpoints were not being deleted.
Once i deleted RDS proxy with teh help of my colleague, entire VPC i was able to delete. I am pursuing Cloud Computing and while doing a Cloud lab i came across this error.
Hello.
In that case, I think you need to delete the VPC endpoint first.
https://docs.aws.amazon.com/vpc/latest/privatelink/delete-interface-endpoint.html
I already tried that, it didn’t work.
In that case, please follow the steps in the document below to find the ENI dependencies. Even if you think it is tied to a VPC endpoint, it may be tied to a different resource. https://repost.aws/knowledge-center/troubleshoot-dependency-error-delete-vpc
Also, if possible, please share the ENI images that cannot be deleted. Why did you decide that the ENI was tied to a VPC endpoint?By the way, please note that in the case of a requester-type VPC endpoint, the VPC endpoint will not disappear unless you delete the resources on each used service side. https://repost.aws/knowledge-center/vpc-delete-requester-managed-endpoint
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 4 Monaten- AWS OFFICIALAktualisiert vor 9 Monaten
- AWS OFFICIALAktualisiert vor 3 Jahren
- Wie lösche ich meinen Network Load Balancer, der VPC-Endpunkt-Services (PrivateLink) zugeordnet ist?AWS OFFICIALAktualisiert vor 2 Jahren
This is it, VPC endpionts should specify their dependencies/Parent component. (Error message being bugged upon attempt to delete made it even worse). Thank you!!