Migrate ACM configuration data from EDAS/SAE to MSE Nacos - Microservices Engine

You can use the Microservices Engine (MSE) migration tool, MSE Sync, to easily synchronize configuration data from Application Configuration Management that is integrated into Enterprise Distributed Application Service (EDAS) or Serverless App Engine (SAE) to MSE Nacos instances. You can synchronize all configuration data by performing simple configuration operations. This topic describes how to migrate configuration data from Application Configuration Management that is integrated into EDAS or SAE to MSE Nacos instances

Prerequisites

An MSE Nacos instance is created. For more information, see Create a Nacos engine.
MSE Sync is deployed. For more information, see Migration solution based on MSE Sync.

Usage limits

If the MSE Sync tool breaks down, data synchronization is interrupted. Therefore, we recommend that you deploy the MSE Sync tool on at least two nodes. After the migration process starts, you must complete the migration at the earliest opportunity.
The networks among SAE or EDAS, MSE Sync, and MSE Nacos instance are interconnected.

Migration procedure

Step 1: Obtain the SAE or EDAS namespace ID

EDAS

Log on to the EDAS console.
In the navigation pane on the left, choose Resource Management > Microservices Space. In the top menu bar, select your target region.
On the Microservices Space page, obtain the ID of the target microservices namespace.

The ID is in the Microservices Namespace Name/ID column.

SAE

Log on to the SAE console.
In the navigation pane on the left, choose Configuration Management > Distributed Configuration (ACM). In the top menu bar, select your target region.
On the Distributed Configuration (ACM) page, click the Namespaces tab and copy the namespace ID.

Step 2: Create a migration task

In the navigation pane on the left of the MSE Sync tool, click Synchronization tasks.
On the Service Synchronization page, click Import Configuration. In the Import Config dialog box, enter the following configuration and click OK.
```
clusters:
  - clusterName: dst
    connectKeyList:
      - mse-xxxxxx-nacos-ans.mse.aliyuncs.com:8848
    clusterType: NACOS
  - clusterName: src
    clusterType: ACM
    product: EDAS
    namespaceId: namespaceId
    ak: ak
    sk: sk
    regionId: us-east-1
    userId: 1419633767709936
tasks:
  - source: src
    destination: dst
    type: Config
```
Note
- namespaceId is the ID of the namespace obtained from EDAS or SAE.
- ak and sk are the AccessKey ID and AccessKey secret of the RAM user that has read and write permissions on configuration data in Application Configuration Management.
After the import is successful, view the task progress on the task synchronization page.

Step 3: Verify the result

Log on to the MSE console and select a region in the top menu bar.
In the navigation pane on the left, choose Microservices Registry > Instances.
On the Instances page, click the name of the target instance.
In the navigation pane on the left, choose Configuration Management > Configurations to verify that your configuration data has been synchronized.