Unable to detach/delete 2 Network Interfaces #56

[ghost]

Really appreciated this project. Thanks to AWS. But having issues with clean up.

I am having the same issue raised in #56. As recommended by @abaird986, I deleted ECS resources (i.e. Fargate) but still cannot delete NLB or VPC. When trying to delete mysfits-nlb, I get error:

Load balancer 'arn:aws:elasticloadbalancing:us-east-1:641860735165:loadbalancer/net/mysfits-nlb/82ff6e1df96b980a' cannot be deleted because it is currently associated with another service.

When trying to delete the VPC, I get error:

Unable to delete this VPC:
The VPC contains one or more in-use network interfaces, and cannot be deleted until those network interfaces have been deleted.
View in-use network interfaces in the VPC.
eni-098d350b165da699f
eni-09e539d8f129d5008

When trying to detach a network interface, I get error:

Error deleting network interface
eni-098d350b165da699f: You are not allowed to manage 'ela-attach' attachments.

Thanks in advance.

[ramnarayanp]

@dbw12345 ,
i too was having the same problem a little earlier today, but i was able to clean it all up. It was really cumbersome, but i got it done finally. I think, the steps i followed was to go to the service end points and deleted them manually before attempting the n/w interface clean up. can you please try that?

[ghost]

Thanks, @ramnarayanp.

I have worked through the clean up again and found some additional resources such as:

• Deletion of CloudWatch logs (it seems this was the reason for not being able to delete the network interfaces).
• Deletion of Listener associated with nlb,
• Deletion of Target Groups.
• Rejection of endpoint in Endpoint Services/Endpoint Connections.

This enabled deletion of the network load balancer.

I then deleted the subnets, and a few other resources. To be honest, I have lost track of the exact things I have done because there were so many resources hidden under layers!

Anyway, I have been able to delete the CoreStack. Thanks for the response and advice.

[ramnarayanp]

The creators of this project could it better with documenting the clean up!

[ghost]

It definitely can be improved, but to document it properly, they'd have to add a sixth module! There are so many resources created throughout the project. As a beginner, it is hard to comprehend all the things that are being created.

[passionatedevops]

Solution
Look at the "Description" column of "Network Interfaces" (which is under "Network and Security"). Find the relevant item, device or object (e.g., if you see ELB go to Load Balancing -> Load Balancers, if you can see FS > go to EFS etc). Delete this object . Then go back and delete the Network Interface. Now you can delete the Security Group

[pavankumarupadhyayula]

Please Delete all CloudWatch Logs and Verify.

[th3r10n]

@passionatedevops ,
How come deleting the ELB is the solution when in fact the problem is not being to delete the ELB?

[th3r10n]

I deleted the cluster, service, target groups, listener, log groups and still was not able to delete the ELB.
After that:

1. Go to API Gateway --> APIs and delete the Mysfits REST API.
2. Go to API Gateway --> VPC links and delete the VPC link created for that API.
   After that I was able to delete the mysfits-nlb.
   AWS should definitely add a sixth module just for the clean up.

[andypuckett]

Delete the Endpoint Service