Step 1: Create a data collector and install the DMS Collector
After your prerequisites are in place as described in Prerequisites, you create a data collector. You then download, install, and configure the DMS Collector. A data collector is an AWS resource that you use to manage incoming information from the DMS Collector. The DMS Collector is an executable file that you run locally to collect information about your data environment.
To create a data collector
Sign in to the AWS Management Console and open the AWS DMS console at https://console.aws.amazon.com/dms/v2/
. Choose DMS Studio Experience to turn on DMS Studio functionality in the AWS DMS console.
Choose Data collectors in the navigation pane.
Choose Create data collector.
In the Create data collector page, provide the following values:
Name –
Test Collector
Description –
My test collector
Amazon S3 bucket – Choose the Amazon S3 bucket that you created in Amazon S3 bucket.
IAM role – Choose DMSDiscoveryS3FullAccess.
Choose Create data collector.
The new data collector appears on the Data collectors page.

To download, install, and configure the DMS Collector
Open the AWS DMS console at https://console.aws.amazon.com/dms/v2/
. In the navigation pane, choose Data collectors.
Choose Test Collector.
For Actions, choose Download local collector.
When the download completes, run the
AWS_DMS_Collector_Installer.msi
file. Leave all of the settings as they are, and choose Finish.After the DMS Collector installation is complete, open the following location in a browser if it doesn't open automatically:
http://localhost:11000
.The DMS Collector Configure Credentials page appears. Provide a login name and password, confirm the password, and choose Configure credentials. Using a login name and password keeps your DMS Collector secure.
The DMS Collector page appears.
On the DMS Collector page, verify that MySQL connector for .NET in the Software check section is Passed.
In the Data forwarding section, choose Configure credentials.
In the Configure credentials for data forwarding dialog box, enter your AWS account credentials, and choose Save credentials.
For more information about account credentials, see Programmatic Access in the AWS General Reference.
On the DMS Collector page, verify that the Data forwarding section has Yes for Access to Amazon S3 and Access to AWS DMS.
If your computer is on an Active Directory domain, you can specify a domain controller that DMS Collector uses to discover database servers.
If your computer is not on a domain, or you want to skip server discovery and specify your local database manually, skip to step 13.
In the LDAP servers configuration section, choose + Server.
In the Add LDAP Server dialog box, enter the fully qualified domain name (FQDN) and credentials for your domain controller. To find your domain controller's FQDN, do the following:
Open a command prompt window, and enter the following command to find the domain controller's hostname.
> echo %logonserver%
Enter the following command to find your DNS suffix.
nslookup
Your domain suffix is listed as Connection-specific DNS suffix.
Your domain controller's FQDN is its hostname followed by its DNS suffix, as in the following example.
my_dc.corp.example.com
(Optional) If you want to add your local database manually rather than running server discovery, do the following:
On the DMS Collector home page, choose the Monitored objects icon from the navigation pane.
Choose the Database servers tab.
Choose + Server. In the Add monitored object dialog box, provide the following information:
Engine –
MySQL Server
Host name/ IP –
localhost
Port –
3306
Authentication type – Login/ Password authentication
Allow public key retrieval – Select this check box
User name –
root
Password – Enter the password that you created in Create a local MySQL database
Choose Verify connection. If the credentials are correct and the connection is successful, you see Connection verified.
Choose Save. The local server appears in the list of monitored objects.