One of the pre-requisites of AWS DMS is to have configured a subnet group, which is a collection of subnets that can be used by the DMS Replication Instance.
In the Create replication subnet group form enter the following parameter values.
Parameter | Value |
---|---|
Name | dms-subnet-group |
Description | Default VPC Subnet Group for DMS |
VPC | select TargetVPC |
Add subnets | select TargetVPC-public-a, TargetVPC-public-b |
Double check that all settings are correct, in particular the public subnets with TargetVPC-public in their name, and then click on the Create subnet group button.
In this step you will create an AWS Database Migration Service Replication Instance that initiates the connection between the source and target databases, transfers the data, and caches any changes that occur on the source database during the initial data load.
Inside AWS Console, go to Services and Database Migration Service.
Click on Replication instances and then on the Create replication instance button.
On the Create replication instance screen configure a new replication instance with the following parameter values:
Parameter | Value |
---|---|
Name | replication-instance |
Description | DMS replication instance |
Instance Class | dms.t3.medium |
Engine version | 3.4.5 |
Allocated storage (GB) | 50 |
VPC | TargetVPC |
Multi-AZ | Dev or test workload (Single-AZ) |
Publicly accessible | Checked |
In the Advanced security and network configuration, make sure to select the replication subnet group, Availability zone (us-west-2a) and the replication instance security group that you created earlier.
Click Create button.
If you get an error saying “SYSTEM ERROR MESSAGE:Cannot create a dms.t3.medium replication instance”, create the DMS replication instance again but select us-west-2b Availability Zone and if this doesn’t help - select larger instance class.