2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hello.
Do you know which resource the network interface was created from?
I think it's probably an ENI related to EKS, so try deleting EKS first.
Also, if ALB etc. were deployed together, I think there is a possibility that it is the ENI of ALB.
If you check the "Description" of the ENI, you may be able to determine which resource it was created from.
https://repost.aws/knowledge-center/troubleshoot-dependency-error-delete-vpc
Review the Description to see which resources the network interface is attached to.
0
wow thanks all. It works. (deleting EKS cluster!) I couldn't think about it. I thought I should delete all underlying resources before deleting the cluster. The answer is deleting the cluster first!
beantwortet vor einem Monat
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren