-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ssh_private_key_file is of limited use without key_pair_name parameter #1635
Labels
Comments
We can possibly extend "temporary_key_pair_name" usage for the case when ssh_private_key_file is in place to set the key pair name. The name of the parameter will be misleading though |
This also appears related to #1697 |
sethvargo
changed the title
amazon-ebs builder: ssh_private_key_file is of limited use without key_pair_name parameter
ssh_private_key_file is of limited use without key_pair_name parameter
Feb 24, 2015
Closed
ghost
locked and limited conversation to collaborators
Apr 9, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It's possible now to specify a key to use instead of a generated key for amazon EBS builders. However, it results in launching an instance with an empty key pair and, to my understanding, suggesting that the key will be put on the source instance authorized_keys beforehand.
This behaviour could be significantly improved by providing a "key_pair_name" parameter, which will be used along with "ssh_private_key_file" to let amazon put public key to the instance on start.
The text was updated successfully, but these errors were encountered: