Tutorial: How to Use the Access Server AWS Launcher
Overview
Our simple setup wizard allows you to create a pre-configured Access Server for Amazon AWS and easily create a CloudFormation script directly on our site.
Follow these steps to launch Access Server with CloudFormation
Sign in to the Access Server portal.
Click Activation Keys.
Get a free subscription for two VPN connections, or purchase one with more connections.
Your new subscription license and activation key are displayed under Activation Keys.
Click on Install Access Server.
Click Amazon AWS from the Cloud provider (Iaas) options.
The AWS installation page displays with Deployment with CloudFormation Script.
Select your preferred AWS region from the drop-down.
Select your subscription from step 1.
Click Launch Script on AWS or click Download the CloudFormation Script to launch manually.
AWS opens with Quick create stack.
Enter a Stack name or leave it as is.
Note that the Activation Key is populated.
Select your VPC ID and Public Subnet ID.
Adjust the Instance Name and Instance Type if needed.
Select a Key Pair Name for SSH access.
Check the box to acknowledge that AWS CloudFormation might create IAM resources.
Click Create stack.
CREATE_IN_PROGRESS displays, and you can monitor the progress until CREATE_COMPLETE displays.
After your new stack completes, click the Outputs tab.
Take note of the admin portal URL for the Admin Web UI and the password.
Click the URL to open the Admin Web UI.
Sign in with the openvpn username and the provided, randomly generated password.
Review and click Agree for the EULA.
After successful authentication, change the temporary password:
Click User Management > User Permissions.
Click More Settings for the user, openvpn.
Enter a new password in the Local Password field.
Select Save Settings and Update Running Server.
You can now complete the configuration for your network. Refer to our Setup Guide for documentation resources.
Issue: Key Pair (or other parameter) doesn't display as an option in the drop-down.
Resolution: Ensure that you have the key pair, VPC, subnet, or other parameter in the same AWS region that you selected for your CloudFormation script.