Help Center/ Migration Center/ User Guide/ Application Migration Projects/ Resource Survey/ Online Discovery – Cloud Platform Discovery
Updated on 2026-05-22 GMT+08:00

Online Discovery – Cloud Platform 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, Google Cloud, Azure, and Tencent 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

Creating a Cloud Platform Collection Task

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

    Figure 1 Cloud discovery

  4. Configure the parameters based on 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, Google Cloud, Azure, and Tencent 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, click Add Credential 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 your 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 set up, click Create Agency. On the displayed page, click OK. After the authorization is complete, the agency status changes to Agency set up.

    Region

    Select the region where your source environment is deployed. You can select multiple regions.

    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. This is recommended for the assessment and migration of a small number of resources. 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.

    • If the task succeeds, return to the Resource List page and check the discovered source resources and their details. For details, see Checking Discovered Source Resources.
    • If the task fails, click the task name to view the data source that failed to be collected. Hover over the collection status to view the failure cause.
      Figure 2 Viewing the failure cause

Supported Resource Types for Cloud Platform Collection

Cloud Platform

Resource Type

Subtype

Remarks

Alibaba Cloud

Servers

-

Only IPv4 addresses are supported.

  • 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

-

Only IPv4 addresses are supported.

  • Big data clusters
  • Databases

-

-

Containers

  • CCE Standard Cluster
  • CCE Turbo Cluster

CCE Autopilot clusters cannot be collected.

Middleware

  • Redis
  • Kafka

-

Storage

  • Object storage
  • File storage

SFS file storage is not supported.

Networking

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

-

AWS

Servers

-

Only IPv4 addresses are supported.

  • 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

-

Only IPv4 addresses are supported.

Databases

-

-

Storage

  • Object storage
  • File storage

-

Google Cloud

Servers

-

Only IPv4 addresses are supported.

  • Containers
  • Databases

-

-

Databases

-

Database specifications are determined by parsing the machine type string. Specifications can only be identified if they follow the rules below.

  • Predefined machine types: For micro machine types like db-f1-micro and db-g1-small, the vCPU count is 1.
  • Optimized machine types: For machine types like db-c4a-highmem-{vcpu} and db-perf-optimized-N-{vcpu}, vcpu represents the vCPU count.
  • Custom machine types: For machine types like db-custom-{vcpu}-{ram}, vcpu represents the vCPU count, and ram represents the memory size.

Middleware

Redis

-

Storage

  • Object storage
  • File storage

-

Networking

  • EIPs
  • Route tables
  • Security groups
  • VPCs

-

Azure

Servers

-

Only IPv4 addresses are supported.

Containers

-

-

Databases

  • SQL Server
  • MySQL Flexible Server
  • PostgreSQL Flexible Server

Collection of SSL connection status is not supported.

Storage

Object storage

  • For the object storage service of Azure, the data volume and number of files in a bucket (known as a container in Azure) cannot be collected.
  • The resource ID, access protocol, number of objects, capacity, bucket type, and storage policy of the object storage cannot be collected.

File storage

Collection of used storage capacity for file systems is not supported.

Middleware

Redis

-

Kafka

Collection of Kafka resource attributes, including AZ, version, disk capacity, and billing mode, is not supported.

Networking

EIPs

-

Security groups

Public NAT gateways

VPCs

Route tables

The VPC, associated subnets, and routes of route tables cannot be collected.

Load balancers (ELB)

The status, instance specification type, home VPC, and home subnet of load balancers cannot be collected.