Help Center/ Migration Center/ User Guide/ New Edition/ Resource Discovery and Management/ Online Discovery
Updated on 2025-08-19 GMT+08:00
View PDF
Share

Online Discovery

Before migrating, you need to discover your resources and collect their details. This section describes how to discover resources provisioned on cloud platforms such as Alibaba Cloud, Huawei Cloud, AWS, Tencent Cloud, Google Cloud, Azure, Qiniu Cloud, and Kingsoft Cloud over the Internet. Then you can organize the associations between resources and applications. The resource types supported by MgC depend on the source cloud platform.

  • Alibaba Cloud and Huawei Cloud: servers, containers, middleware, databases, big data clusters, networks, and storage
  • Tencent Cloud: servers, databases, and storage
  • AWS, Google Cloud, and Azure: servers, containers, middleware, databases, storage, and networks
  • Qiniu Cloud and Kingsoft Cloud: object storage

Creating an Online Discovery Task

  1. Sign in to the MgC console. In the navigation pane, under Project, select an application migration project from the drop-down list.
  2. In the navigation pane, choose Source Resources.
  3. Under Online Discovery, click Cloud Discovery.

    Figure 1 Cloud platform discovery

  4. Configure the parameters listed in Table 1 to create a discovery task.

    Table 1 Parameters for creating a cloud discovery task

    Area

    Parameter

    Description

    Task Settings

    Source Platform

    Select the source cloud platform. Currently, Alibaba Cloud, Huawei Cloud, AWS, Tencent Cloud, Google Cloud, Azure, Qiniu Cloud, and Kingsoft Cloud are supported.

    Collection Method

    If you choose Credential, select the credential for accessing the source cloud platform. If the credential is not in the drop-down list, choose Create to add it. For details, see Managing Credentials.

    • If the source cloud platform is Alibaba Cloud, Huawei Cloud, AWS, or Tencent Cloud, select AK/SK for Authentication and enter the AK/SK pair of your source cloud account.
    • If the source cloud platform is Google Cloud, select Configuration File for Authentication and upload the configuration file that contains your Google Cloud service account credentials. The file must be in JSON format and cannot exceed 4 KB. For details about how to obtain the configuration file, see Obtaining Google Cloud Credentials Configuration Files.
    • If the source cloud platform is Azure, Select ID/Secret for Authentication. To learn how to obtain Azure credentials, see How Do I Obtain Azure Credentials?

    If you choose Agency, a cloud service agency is required to assign MgC the permissions required to access resources in the current account. For details about the agency permissions, see Cloud Discovery.

    NOTE:

    This option is available only when Source Platform is set to Huawei Cloud.

    If the Agency Status is Agency not created, click Create Agency. On the displayed page, click OK.

    Region

    Select the region where your source environment is located. Multiple regions can be selected.

    Resource Type

    Choose the types of source resources (collection items) to be collected from the drop-down list. You can review the supported cloud platforms and resource types.

    NOTICE:

    If Source Platform is set to Huawei Cloud and Collection Method to Agency, the following resources can be collected: servers, EIPs, security groups, and VPCs.

    Basic Information

    Task Name

    The default name format is <task type>-<current-time>. You can also specify a name.

    Task Description (Optional)

    Describe the task.

    Application (Optional)

    Select the application that you want to group the discovered resources into. If no applications are available, perform the following steps to create one:

    1. Click Create Application. Enter an application name and description.
    2. Configure Business Scenario and Environment, and set Region to the region that you want to migrate to.
    3. Click OK.

  5. Click Confirm. After the online discovery task is created, MgC starts discovering source resources.

Checking Migration Readiness for Servers

Perform the following steps to check whether your source servers meet migration requirements:
  1. Ensure that the MgC Agent has been installed in the source intranet environment and has been connected to MgC.
  2. Go to the Source Resources page, in the server list, select the servers to be migrated and click Group as Application above the list. If you have specified an application in the online discovery task for discovering these source servers, skip this step.
    • If an application is available, select the application from the drop-down list and click OK.
    • If no applications are available, click Create Application in the displayed dialog box. Then enter an application name and description, select a business scenario, environment, and target region, and click Create. Then click OK.
  3. On the top of the server list, choose Migration Scenario > Server migration. If the Migration Readiness column is not in the list, click next to the search box and select Migration Readiness.
  4. For each source server, click Configure in the Migration Readiness column.
  5. Configure the parameters listed in Table 2.
    Table 2 Parameters for configuring migration readiness check

    Parameter

    Configuration

    Type

    Set this parameter based on the source server OS type.

    MgC Agent

    Select the MgC Agent installed in the source environment.

    Access IP Address

    Specify the IP address for accessing the source server. You can specify a public or private IP address. After the check is passed, the IP address you specify here will be used for migration.

    Port

    Enter the accessible port of the server.

    • The port defaults to 5985 on Windows and can be modified.
    • The port defaults to 22 on Linux and can be modified.

    Credential

    Select the server credential. If the credential is not displayed in the list, go to the MgC Agent console, add the server credential, and synchronize it to MgC.

    NOTICE:

    The credentials you provide must have sufficient permissions, so the MgC Agent can collect necessary server details. Deep collection requires that the credentials you provide meet the following requirements:

    • Linux: root and its password
    • Windows: administrator and its password
  6. Click Confirm. The system checks whether the source server can be accessed using the information you provide and whether the server can be migrated. If Ready shows up in the Migration Readiness column, the source server can be migrated.

Performing a Deep Collection for Servers

Perform the following steps to perform a deep collection for your source servers:
  1. Ensure that the MgC Agent has been installed in the source intranet environment and has been connected to MgC.
  2. On the Source Resources page, in the server list, locate the source server whose details you want to collect and click Configure in the MgC Agent column. Configure the parameters listed in Table 3.
    Table 3 Parameters for configuring a deep collection

    Parameter

    Configuration

    Type

    Set this parameter based on the source server OS type.

    MgC Agent

    Select the MgC Agent installed in the source environment.

    Access IP Address

    Specify the IP address for accessing the source server. You can specify a public or private IP address. After the check is passed, the IP address you specify here will be used for migration.

    Port

    Enter the accessible port of the server.

    • The port defaults to 5985 on Windows and can be modified.
    • The port defaults to 22 on Linux and can be modified.

    Credential

    Select the server credential. If the credential is not displayed in the list, go to the MgC Agent console, add the server credential, and synchronize it to MgC.

    NOTICE:

    The credentials you provide must have sufficient permissions, so the MgC Agent can collect necessary server details. Deep collection requires that the credentials you provide meet the following requirements:

    • Linux: root and its password
    • Windows: administrator and its password
  3. Click Confirm. Then the system automatically starts executing a deep collection. When Collected shows up in the Deep Collection column, the collection is complete.

Performing a Deep Collection for Containers

Perform the following steps to perform a deep collection for your containers:
  1. Ensure that the MgC Agent has been installed in the source intranet environment and has been connected to MgC.
  2. On the Source Resources page, click the Containers tab.
  3. For each container resource whose details need to be collected, click Associate in the MgC Agent column.

    If you want to associate multiple resources with an MgC agent at a time, select them and click Manage MgC Agent above the list.

  4. Select the MgC Agent installed in the source environment and click OK. After the association is done, Associated will appear in the MgC Agent column.
  5. For each container resource, in the Credential column, click Associate to configure their credentials.
  6. Select the resource credential. If the credential is not displayed in the list, go to the MgC Agent console, add the credential to the MgC Agent, and synchronize it to MgC.
  7. Click OK. Then MgC checks whether the resource can be accessed using the associated credential. When Ready appears in the Deep Collection column, click Collect to perform a deep collection. You can click Collect Again in the Deep Collection column to launch a deep collection again if needed. After the collection is complete, click the resource name to view the collected details.

Performing a Deep Collection for Object Storage Resources

Follow the steps below to perform a deep collection for your object storage resources, so the system can use the collected details to recommend rightsized migration clusters.
  1. Ensure that the MgC Agent has been installed in the source intranet environment and has been connected to MgC.
  2. On the Source Resources page, click the Storage tab.
  3. Locate an object storage resource and click Configure in the Deep Collection column.
  4. Select the MgC Agent in the source environment and the credential for accessing the resource, and click Confirm. If the credential is not displayed in the drop-down list, go to the MgC Agent console and add the resource credential to the MgC Agent and synchronize it to MgC.

    To perform a deep collection for your Azure object storage resources, you need to provide your storage account and access key. For details about how to obtain the credentials, see How Do I Obtain the Required Credentials Before Using MgC to Perform a Deep Collection for My Azure Object Storage Resources?

  5. Click Add Prefix in the Operation column.
  6. Enter a prefix to filter the objects whose details need to be collected. If this parameter is not specified, all objects in the bucket are collected by default. Click OK to save the prefix settings.
  7. Click Deep Collection in the Operation column. The system starts collecting resource details. You can perform a deep collection on a resource for multiple times. When Collection Status changes to Completed, click the resource name to view the collected information.

Performing a Deep Collection for Databases

Deep collection is available for AWS RDS (for MySQL, MariaDB, Aurora, PostgreSQL, SQL Server, and Oracle) and AWS DocumentDB databases. The data collected includes database versions, engines, server character sets, average transactions per second (TPS), and queries per second (QPS), and other key performance metrics (KPIs). The collected data depends on the database type.

  1. Ensure that the MgC Agent has been installed in the source intranet environment, can access source databases, and has been connected to MgC.
  2. On the Source Resources page, click the Databases tab.
  3. In the database list, filter all discovered AWS databases by applying the Vendor filter. Locate a supported database and in the MgC Agent column, click Associate.

    If you want to associate multiple resources with an MgC agent at a time, select them and click Manage MgC Agent above the list.

  4. Select your MgC Agent. For Access Setting, if the selected resource is in the same VPC as your MgC Agent, select Private access. Otherwise, select Public access. Then click OK. Wait until Associated appears in the MgC Agent column.
  5. In the Credential column, click Associate to configure the credential for accessing the resource.
  6. Select the resource credential. If the credential is not displayed in the list, go to the MgC Agent console, add the credential, and synchronize it to MgC.
  7. Click OK. Then MgC checks whether the resource can be accessed using the associated credential. When Ready appears in the Deep Collection column, click Collect to perform a deep collection. You can click Collect Again in the Deep Collection column to launch a deep collection again if needed.
  8. Wait for the deep collection to complete. Then click the database name to go to the database details page. In the Database Information area, you can view the collected details.

Viewing Discovered Source Resources

A discovery task can collect only basic information about source resources. More detailed information needs to be collected through a deep collection.
  1. On the Source Resources page, you can view the list and number of discovered resources.
    Figure 3 Viewing the resource list
  2. Click each tab to view the list of resources for that type.
  3. Click a resource name to view its details.

Supported Resource Types

Cloud Platform

Resource Type

Subtype

Alibaba Cloud
  • Servers
  • Containers
  • Big data clusters
  • Databases

-

Middleware
  • Redis
  • Kafka

Storage
  • Object storage
  • File storage

Networking
  • Cloud connections
  • Load balancers (ALB and CLB)
  • Private lines
  • Public domain names
  • Private domain names
  • EIPs
  • Public NAT gateways
  • Route tables
  • Security groups
  • VPCs
  • VPN gateways

Huawei Cloud
  • Servers
  • Containers
  • Big data clusters
  • Databases

-

Middleware
  • Redis
  • Kafka

Storage
  • Object storage
  • File storage

Networking
  • Load balancers (ELB)
  • Public domain names
  • Private domain names
  • EIPs
  • Public NAT gateways
  • Route tables
  • Security groups
  • VPCs

AWS
  • Servers
  • Containers
  • Databases

-

Middleware
  • Redis
  • Kafka

Networking
  • Load balancers (ELB) (Currently, only CLB balancers are supported.)
  • Public domain names
  • Private domain names
  • EIPs
  • Public NAT gateways
  • Route tables
  • Security groups
  • VPCs

Storage
  • Object storage
  • File storage

Tencent Cloud
  • Servers
  • Databases

-

Storage
  • Object storage
  • File storage

Google Cloud
  • Servers
  • Containers
  • Databases

-

Middleware

Redis

Storage
  • Object storage
  • File storage

Networking
  • EIPs
  • Route tables
  • Security groups
  • VPCs

Azure
  • Servers
  • Containers
  • Databases

-

Storage
  • Object storage
  • File storage

Middleware
  • Redis
  • Kafka

Networking
  • EIPs
  • Route tables
  • Security groups
  • Public NAT gateways
  • VPCs
  • Load balancers (ELB)

Qiniu Cloud

Storage

Object storage

Kingsoft Cloud

Storage

Object storage
Parent Topic: Resource Discovery and Management