nsen
The AMIs listed on this page doesn't seem to be available.
https://docs.openvpn.net/how-to-tutorialsguides/amazon-ec2-appliance-ami-quick-start-guide/
I did a search and used a public OpenVPN Access Server AMI but they keep "vanishing". Where can I get a list of valid community Access Server AMI in AWS?
The Johan
The Johan
Actually, I was just informed there's a reason for this other page..? I'll ask internally and take whatever action necessary to fix or update this.
nsen
Is there another page out there that lists the current valid AMIs?
The Johan
Not at this time, the AMI's are being changed at this very moment.
nsen
When I search for and try to use openvpn access server AMIs, they all fail to install as they are Marketplace AMIs and I need to subscribe to them in Marketplace. Is there any change of strategy within openvpn to not provide public community version of the access server AMIs?
The Johan
The Johan
So to clarify, what I'm trying to figure out is if we even need to support the community AMIs anymore. The image above can be used by anyone on Amazon AWS as far as I know, and is our officially supported image, and does not require a license key to function, and does not require any payment other than what you normally pay for launching an instance on AWS. So what valid reason is there to maintain two separate versions?
nsen
To use the AMI in AWS Marketplace, you need to subscribe to them first (which are not required for the community AMIs). So, any automation you do to launch openVPN (as part of a larger solution) fails as the AMI is not subscribed to in the first place.
nsen
If openvpn is not going to maintain a community version of the AMI (which is fine), I need to know so that we can create our own image from first principles and install openvpn from the binaries published by openvpn. A AWS Marketplace based image is not going to cut it for us.
The Johan
And why can you not automate subscribing? Pretty sure aws-cli can do that.
I am now speaking as purely myself but I really don't see the point of doing double work; managing 2 different AMIs that are doing the exact same thing. Now if there was a valid reason to maintain two completely different systems that do the exact same thing, then sure, but so far I'm not being convinced yet.
The Johan
And besides, doing an installation of OpenVPN Access Server on a standard Ubuntu image is child's play, it's literally like 3 lines of codes or so.
