1 Answer
0
This is solved now. It was a CloudFormation stack that booked the ENI from deletion.
Once the CloudFromation stack was destroyed, it worked.
answered 3 years ago
Relevant content
- asked 4 years ago
- asked 14 days ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago