Discovering databases for migration using data collectors in AWS DMS
To discover your source data infrastructure, you can use either AWS Application Discovery Service Agentless Collector or AWS DMS data collectors. The ADS Agentless Collector is an on-premises application that collects information about your on-premises environment through agentless methods, including server profile information (for example, OS, number of CPUs, amount of RAM), database metadata, and utilization metrics. You install the Agentless Collector as a virtual machine (VM) in your VMware vCenter Server environment using an Open Virtualization Archive (OVA) file. An AWS DMS data collector is a Windows application that you install in your local environment. This application connects to your data environment and collects metadata and performance metrics from your on-premises database and analytic servers. Once database metadata and performance metrics have been collected through either the ADS Agentless Collector or a DMS data collector, DMS Fleet Advisor builds an inventory of servers, databases, and schemas that you can migrate to the AWS Cloud.
The DMS data collector is a Windows application which uses .NET libraries, connectors, and data providers to connect to your source databases for database discovery and data collection.
The DMS data collector runs on Windows. However, your DMS data collector can collect data from all supported database vendors regardless of the OS server where they run.
The DMS data collector uses a protected RTPS protocol with TLS encryption to establish a secure connection with DMS Fleet Advisor. Therefore, your data is encrypted during transit by default.
AWS DMS has the maximum number of data collectors that you can create for your AWS account. See the following section for information about AWS DMS service quotas Quotas for AWS Database Migration Service.
Topics
- Permissions for a DMS data collector
- Creating a data collector for AWS DMS Fleet Advisor
- Installing and configuring a data collector in AWS DMS
- Discovering OS and database servers to monitor in AWS DMS
- Managing monitored objects in AWS DMS
- Using SSL with AWS DMS Fleet Advisor
- Collecting data for AWS DMS Fleet Advisor
- Troubleshooting for DMS data collector
Permissions for a DMS data collector
The database users that you create for the DMS data collector should have read permissions. However,
in some cases, the database user requires the EXECUTE permission. For more information,
see Creating database users for AWS DMS Fleet Advisor.
The DMS data collector requires additional permissions to run the discovery scripts.
-
For OS discovery, the DMS data collector needs credentials for the domain server to run requests using the LDAP protocol.
-
For database discovery in Linux, the DMS data collector needs credentials with
sudo SSHgrants. Also, you should configure your Linux servers to allow running remote SSH scripts. -
For database discovery in Windows, the DMS data collector needs credentials with grants to run Windows Management Instrumentation (WMI) and WMI Query Language (WQL) queries and read the registry. Also, you should configure your Windows servers to allow running remote WMI, WQL, and PowerShell scripts.
