1 Resposta
- Mais recentes
- Mais votos
- Mais comentários
0
This is solved now. It was a CloudFormation stack that booked the ENI from deletion.
Once the CloudFromation stack was destroyed, it worked.
respondido há 4 anos
Conteúdo relevante
- AWS OFICIALAtualizada há 2 anos