AWS (Amazon) AMI for OpenVPNAS - Cloud-init reference?

tedk-42

Does this exist? If so my Google skills are lacking :lol:

Basically I want to automate the build of the Openvpn server using Terraform and use cloud-init for the Openvpn configuration but I can't find anything on it.

I can SSH into the EC2 instance and can confirm cloud-init package is installed and I have a sample text file which has the parameters below which can be passed into the 'user_data' attribute in Terraform:

admin_user=test
admin_pw=testpassword
reroute_gw=0
reroute_dns=1

tedk-42

Bumps allowed?

No-one knows any extra key-value pairs I can pass into cloud-init?

tedk-42

To answer my own question, I found this document: https://docs.openvpn.net/how-to-tutorialsguides/virtual-platforms/amazon-ec2-appliance-ami-quick-start-guide/

public_hostname -- hostname that clients should use to contact the server.

admin_user (default=openvpn) -- Access Server administrative account name.

admin_pw -- administrative account initial password. Note that
this parameter is communicated to the instance via a
cleartext channel. A more secure method would be to ssh
to the instance and use the passwd command to set the
password.

license -- Access Server license key (without a license key, the
Access Server will support up to 2 concurrent connections).

reroute_gw (boolean, default=0) -- if 1, clients will route internet
traffic through the VPN.

reroute_dns (boolean, default=0) -- if 1, clients will route DNS
queries through the VPN.

jgomo3

tedk-42 wrote To answer my own question, I found this document: https://docs.openvpn.net/how-to-tutorialsguides/virtual-platforms/amazon-ec2-appliance-ami-quick-start-guide/
.
.
.

I don't find any mention to Cloud-Init in that document. Is that the right link?

The Johan

It may be the right link but the whole documentation site was refreshed a few months ago. So that information may have been cleared away or is put somewhere else on the documentation site. This is the danger of reviving a year-old thread from the dead.

tedk-42

Indeed it has been refreshed for worse. You can't auto deploy the CLI configuration, instead it wants user input now every time