how do i delete network interface that its type is lambda

0

i didn't create lambda. I even haven't used any service with lambda.

It might have been created with related service.

the network interface is in use type of interface is lambda connection status is attached also I have Requester ID that is provided and Attachment ID

the message that comes up when i try to delete is said "The network interface can't be deleted" Reason : Network interface is currently in user and is of type lambda.

following the link on the message, there is no Lambda service at all.

so i tried this procedure to solve it

/root/aws-support-tools/Lambda/FindEniMappings]# ./findEniAssociations --eni 'eni-name' --region 'us-somewhere-1' This script is for determining why an ENI that is managed by AWS Lambda has not been deleted.

Found 'eni-name' with 'subnet-name' using Security Groups 'sg-name' Searching for Lambda function versions using 'subnet-name' and Security Groups 'sg-name'..

No Lambda functions or versions found that were using the same subnet as this ENI. If this ENI is not deleted automatically in the next 24 hours then it may be 'stuck'. If the ENI will not allow you to delete it manually after 24 hours then please contact AWS support and send them the output of this script.

Junho
질문됨 2달 전308회 조회
2개 답변
0

Hello.

I think it would be best to contact AWS Support as output in the message.
In this case, there may be a problem with your account, so I think you should open a case with "Account and billing" and inquire.
Inquiries under "Account and billing" can be made free of charge.
https://docs.aws.amazon.com/awssupport/latest/user/case-management.html

profile picture
전문가
답변함 2달 전
0

It appears that you've utilized a script to attempt to identify why the ENI associated with Lambda hasn't been automatically deleted. Since you've confirmed there are no Lambda functions or versions using the same subnet and security groups as the ENI, and you've already attempted to delete it manually but couldn't be due to the type being Lambda, here are a few additional steps you can take:

  • Verify Dependency: Check if there are any other AWS services or resources that might be indirectly associated with Lambda, which could be utilizing this ENI.

  • Inspect CloudWatch Metrics: Look into CloudWatch metrics to see if there's any activity or usage associated with this Lambda-related ENI.

  • Check AWS Config Rules: Review AWS Config Rules to ensure there are no specific rules or configurations that might be linked to Lambda and causing the ENI to persist.

  • Examine CloudFormation Stacks: Investigate if any CloudFormation stacks might have created this ENI, even indirectly through nested stacks or dependencies.

  • Consult AWS Documentation: Refer to the latest AWS documentation for any updates or known issues regarding Lambda-related ENIs.

  • Contact AWS Support: If none of the above steps yield a solution, reaching out to AWS Support with detailed information about the issue, including the output of your diagnostic script, will likely provide the best assistance.

Remember to approach deletion with caution, especially when dealing with network interfaces that may have dependencies or implications on your infrastructure's functionality.

답변함 2달 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠