AWS res documentation change
Summary
Added troubleshooting documentation for 'Network interface deletion failure' during RES stack deletion, including manual cleanup instructions
Security assessment
This change adds operational troubleshooting guidance for cleaning up stale network interfaces when Lambda fails to delete them during stack deletion. This is an operational reliability issue, not a security vulnerability. No security implications are mentioned.
Diff
diff --git a/res/latest/ug/res-troubleshooting-issue-runbooks.md b/res/latest/ug/res-troubleshooting-issue-runbooks.md index c3058fb29..10417b32c 100644 --- a//res/latest/ug/res-troubleshooting-issue-runbooks.md +++ b//res/latest/ug/res-troubleshooting-issue-runbooks.md @@ -114,0 +115,2 @@ The following section contains issues that may occur, how to detect them, and su + * Network interface deletion failure + @@ -1175,0 +1178,2 @@ You can fix this by following the instructions at: [ https://really-simple-ssl.c + * Network interface deletion failure + @@ -1361,0 +1366,6 @@ After this, go to the S3 console, select the bucket with name `<environment_name +### Network interface deletion failure + +If you notice a `detachvpcfromlambdacustomresource` deletion failure in the Events section of the RES finalizer stack deletion, this most likely means the Lambda service either failed to delete or did not delete in time the network interfaces attached to RES Lambdas. + +You can manually delete these stale network interfaces by navigating to the **Network Interfaces** page within the [ Amazon EC2 console](https://console.aws.amazon.com/ec2) and filtering by descriptions containing `AWS Lambda VPC ENI-`{RES-Environment-Name}``. There should be up to 14 network interfaces, though it could be fewer depending on how many Lambda was able to successfully delete. Manually delete these network interfaces, then restart the RES stack deletion. +