This all about AWS support related tasks and questions
Jan 27 2021
Apr 30 2020
Nov 12 2019
Oct 19 2019
This works as expected
I'm still having an issue with using build-ami to create an AMI in us-gov-west-1.
Jun 4 2019
All you need for ssh keys to work for AMI is to add cloud-init package in configure step:
May 30 2019
build-ami is working for me if I remove disable-password-authentication from the config template and add in a password into the config template. I have come across another issue though. I was able to get it to work in us-east-1 and us-east-2, but I can't deploy into us-gov-west-1. First problem was it couldn't find a debian-jessie image but that was solved by changing the owner from 379101102735 to 256493402735. Now it's throwing an 401 when attempting to list all subnets. I'm guessing that the python code pulled from ansible is configured for a specific region or the cli command used in GovCloud is slightly different. Either way it's not working.
Apr 20 2019
I wasn't aware that there was an aws target for the vyos-build scripts.
@spectre3500 Now that I think of it, did you build it with build-ami or the AWS target of the vyos-build scripts?
...oh, and remove "disable-password-authentication" from the SSH settings of course.
I wonder if this issue will ever stop re-occuring. Every time it happens, it's for some new reason. I think this time it may be related to ongoing work of @Unicron.
Apr 19 2019
I'm also experiencing the same issue with vyos-1.2.0-rolling-201904190439. I was able to create the ami using the build-ami playbooks, but when launched I could not login using the keypair. Is there a fix for this or a workaround?
Dec 21 2018
Dec 14 2018
added the patch! thanks
Dec 10 2018
I found an AMI I had built from 1.1.8 back on July 7th. I can create functional 1.1.8 instances from that, so it looks to be something unique to 1.2.0, but I can't say for sure because I don't have a working way to build 1.1.8 AMIs currently. The 1.1.8 playbooks rely on modules that have been removed from Ansible, so I would have to rewrite them or downgrade my ansible install.
Dec 8 2018
Also tried 1.2.0-rolling-201812080337. My best guess is that its not copying the SSH key into the system properly to allow the vyos user to login, as the system responds, accepts the username, rejects the key then disconnects with no further auth method.
I tried the build with 1.2.0-rc9 and rc10 with the same results. The instance boots up without issue, but rejects any login attempts with the SSH key the instance was launched with. The error it gets back suggests its not configured for key or password login, or any other method for some reason.
Dec 5 2018
Dec 3 2018
I forgot to fetch commits for the latest build-ami version when submitted report.
Now I confirms that problem exists in the latest version with the last commit:
Dec 1 2018
@UnicronNL can you explain right way to create 1.2 ami
Nov 30 2018
This is great an very important feature for AWS since they introduced very cheap and advanced t3 instances.
Nov 27 2018
Nov 23 2018
@m.tremer added the patch, thanks... was under the impression cloud-init added the user as it is stated as default user, but clearly it does not.
Isn't that how Open Source is supposed to work? :)
Nov 22 2018
Good idea, thanks! I've applied the patch and will push it shortly.
Nov 21 2018
Okay, that is good to know. Unfortunately documentation is heavily outdated. However, I found a fix for this problem which I attached to this message as a patch.
Nov 20 2018
build-ami is obsolete and never was intended for 1.2 but 1.1
therefore it will not start work and will be removed at some point in favor of aws target
Just to confirm, I tested this with RC8 and unfortunately, it still does not work.
Nov 19 2018
Nov 16 2018
Nov 15 2018
Same problem, but at the bare metal server with VyOS 1.2-rc7 from repo.
Nov 13 2018
Thanks for your reply.
Do you also create the iso yourself or dowload it?
In 1.2 we will be using cloud-init and the ec2 init script was removed.