Here are the steps involved:
To get started, first create your database instance in Amazon RDS console. Choose any of the database server options that fit your needs. There is only one MySQL option, and we chose “Microsoft SQL Server Express Edition” for our MSSQL test.
Below are the additional settings we applied to the test instances (in case you want to compare).
Once the instance is created, and the status shows “Available,” you can connect to it from ActiveCampaign.
First, though, we have to allow access to our database instance from the ActiveCampaign servers. On the Database Sync page of ActiveCampaign, we list the IP’s you need to whitelist:
In the RDS console, click on “DB Security Groups” on the left side, and add in each IP address:
Next, let’s create some sample data in the MSSQL database so we can fully test it through ActiveCampaign. You can use any tool you’d like to connect to the database, but if you’re looking for something, we used HeidiSQL to connect from a Windows 7 desktop.
Through the HeidiSQL session manager, add your RDS instance details.
You can find your database host at the bottom of the RDS page:
In HeidiSQL, I went ahead and created a new database and table (both named “subscribers”), and added some sample data.
In ActiveCampaign, add a new database sync using the same connection details from the HeidiSQL client:
A successful connection should appear, and show the table you just created:
Map your fields and you’re all set!
You can save this connection to re-import subscribers from your external database instance at any time.