Tutorial: Migrate from AWS Tiered to AWS PAYG
Overview
If your Access Server is hosted on an AWS Tiered instance, you may have experienced the challenge of migrating to a new server to adjust the number of connections. With our AWS SaaS Marketplace listing, you can migrate to a new EC2 instance with a flexible subscription model through AWS. This option allows you to manage your Access Server connections directly through AWS billing while maintaining the ability to quickly scale your connections up or down as needed without the hassle of instance migrations.
Follow this guide to migrate from an AWS-tiered instance to the new SaaS listing, where you can choose your connections and adjust them anytime through AWS.
To migrate, you’ll follow these steps:
Back up your current system.
Launch a new instance from the AWS SaaS Marketplace.
Move your backup to the new system.
When done correctly, your OpenVPN clients won’t require reinstalling to connect, as the migration keeps the necessary certificate and user data intact.
Before you begin
Helpful Tips
The passwords are stored in the operating system if you use PAM authentication. They will not be backed up in the configuration files from step one.
If you encounter errors when attempting to transfer the files using WinSCP, it may be due to insufficient privileges. Connect using SCP and choose “sudo su -” from the Shell field.
If you use Access Server's clustering function, your data is stored separately in a MySQL-type database. Rather than following the above steps for backing up and restoring database configurations, you will simply set up a new server of PAYG type, add it to the cluster, and then remove the old node from the cluster.