Repository navigation
feat: updated tool to push target and bastion keys in parallel - #57
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Push EC2 Instance Connect keys to the bastion and target in parallel
EC2 Instance Connect keys only last 60 seconds. aws-ssh pushed the key to the target first and the bastion second. Each push makes several AWS calls (loading credentials, looking up the instance, sending the key). By the time SSH hopped from the bastion to the target, the target's key had often expired resulting in an error:
What changed
bastion: access denied. If several fail, all errors are shown.