- 最新
- 最多得票
- 最多評論
Hi again,
We're still experiencing this issue. We'd gladly appreciate some help with solving this.
Best Regards,
Benjamin Simonsson
After direct discussions with the AWS Technical Support I managed to fix this.
In case anyone else ever stumbles upon this thread while having the same issue:
Our problem was that some of our Lambda functions had old inactive versions that still referenced the subnets which we wanted to delete; this caused their network interfaces to apparently still be in use.
To fix this I went through the relevant Lambda functions in the AWS Console and manually deleted the old versions which were affected. After that the subnets could successfully be deleted.
Please see https://aws.amazon.com/premiumsupport/knowledge-center/lambda-eni-find-delete/. There are links to some scripts you can run to confirm/identify if the ENIs are owned/held by Lambda.
-
Warm Greetings Everyone!* I am having a similar situation with my account . I am unable to delete my Network Firewall , Network Interface, VPC, Endpoints . When trying to delete Network Firewall, this is the error received : 1 * For Firewall : " Cannot DeleteFirewall because at least one of the firewall endpoints are missing the AWSNetworkFirewallManaged:true tag: [vpce-00957b459fe0dec1b] " I have added tags to endpoints per recommendation but still. 2 For endpoints: "vpce-00957b459fe0dec1b - Operation is not allowed for requester-managed VPC endpoints for the service com.amazonaws.vpce.us-east-2.vpce-svc-0f427de517c75a430." 3 * Network Interface: "Network interface is currently in use by ela-attach-xxxxxxxxxxxx"
-
Kindly note that i have released all elastic IPs, NAT, Internet Gateway. I need your assistance please because the bill for Network interface keeps increasing for a service i don't use.
相關內容
- 已提問 7 個月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前