Mirroring auto-created/destroyed for EC2 instances #45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
ec2:DescribeInstances
API call. The issues is thatterminated
EC2 instances don't have attached ENIs. We catch/process theshutting-down
event which precedesterminated
, and the ENIs are still available then, but if there's an unexpected delay in processing it's possible that we might make ourec2:DescribeInstances
call after the ENIs have been removed from the instance, at which point we won't know which ENI to tear mirroring down for.Tasks
Testing
AwsEventListener Lambda: EC2 Instance Running
CreateEniMirroring Lambda
AwsEventListener Lambda: EC2 Instance Shutting Down
DestroyEniMirroring Lambda