Deletion of subnet and therefore VPC fails when Lambda ENIs are still attached in the subnets

[Puneeth-n]

terraform-provides-aws: 1.27.0
terraform-core: 0.10.8

Seems to be related to hashicorp/terraform/issues/10272

I recently tried to destroy one of out test environments comprising of a VPC, around 50 lambdas all running within the VPC and 2 subnets.

I do not explicitly create any ENIs for lambdas so AWS creates it automagically upon lambda invocations.

When I tried to destroy my environment, the subnet deletion failed with a timeout as there were ENIs still attached and active in the subnets.

How does one go about fixing this?

[bflad]

@Puneeth-n can you confirm if this is already reported by #829? It seems very similar. Thanks! (For what its worth, there's an open PR relating to this as well: #4884)

[Puneeth-n]

@bflad Thanks for the pointers. Seems to be the same issue. Is there a timeline on when it will be merged?

[bflad]

Closing as a duplicate of #829 to consolidate discussions and efforts there. Its not personally on my roadmap to look at currently and doesn't look like there's currently much community 👍 upvoting at the moment.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!