AWS res documentation change
Summary
Added troubleshooting section for network interface deletion failure during stack deletion.
Security assessment
The change provides operational guidance for cleaning up network interfaces that failed to delete. There is no mention of a security vulnerability or feature.
Diff
diff --git a/res/archive/release-minus-1/ug/res-troubleshooting-issue-runbooks.md b/res/archive/release-minus-1/ug/res-troubleshooting-issue-runbooks.md index 89360496e..2c6661075 100644 --- a//res/archive/release-minus-1/ug/res-troubleshooting-issue-runbooks.md +++ b//res/archive/release-minus-1/ug/res-troubleshooting-issue-runbooks.md @@ -116,0 +117,2 @@ The following section contains issues that may occur, how to detect them, and su + * Network interface deletion failure + @@ -1177,0 +1180,2 @@ You can fix this by following the instructions at: [ https://really-simple-ssl.c + * Network interface deletion failure + @@ -1363,0 +1368,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. +