- the listed AMI isn't found
- t2.micros can only be in a VPC(? so said an error), and the docs say
we're using a t1.micro anyway
- Updates to the vagrant file to get the website to build
These changes permit the use of pre-created SSH keypairs with AWS. If
so, the configuration for the builder needs to include an
ssh_keypair_name option and a ssh_private_key_file.
If ssh_private_key_file is *not* defined, it'll go through the
rigamarole of creating a temporary keypair. The ssh_keypair_name option
by itself won't make that change, because it doesn't make sense to
specify a keypair but not tell packer where the private key is, but it
does happen that you could have a private key and the public-key is
"baked in", and not part of your EC2 account.
Adds a 'ssh_keypair_name' option to the configuration
for AWS, along with some munging to create the
temporarily keypair if one isn't specific.
NOT YET WORKING.
From a 'make' I get the following errors:
builder/amazon/ebs/builder.go:94: b.config.SSHKeyPairName undefined
(type config has no field or method SSHKeyPairName)
builder/amazon/instance/builder.go:199: b.config.SSHKeyPairName
undefined (type Config has no field or method SSHKeyPairName)
Clint Shryock
Seth Vargo
Ross Smith II
Yuya Kusakabe
Mehul Kar
Sergio Pantoja
Paul Schooss
Misha Brukman
lalyos
Danny Lockard
Lesko, Matthew (NIH/NLM/NCBI) [C]
Sebastian Röder
Colin Hebert