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

You can use MSE Sync to synchronize configuration data from Application Configuration Management (ACM) that is integrated into Enterprise Distributed Application Service (EDAS) or Serverless App Engine (SAE) to a Microservices Engine (MSE) Nacos instance. This topic describes how to configure and run the migration.

How it works

MSE Sync connects to both systems simultaneously and transfers configuration data in real time:

EDAS/SAE (ACM)  ──>  MSE Sync  ──>  MSE Nacos instance
   source             bridge           destination

Prerequisites

Before you begin, ensure that you have:

An MSE Nacos instance (Create a Nacos engine)
MSE Sync deployed (Migration solution based on MSE Sync). We recommend that you deploy MSE Sync on at least two nodes.
Network connectivity between EDAS or SAE, MSE Sync, and the MSE Nacos instance
The AccessKey ID and AccessKey secret of a RAM user with read and write permissions on ACM configuration data

Limitations

If MSE Sync goes down during migration, synchronization stops. We recommend that you deploy it on at least two nodes to reduce this risk.
After the migration process starts, you must complete the migration at the earliest opportunity.

Step 1: Get the source namespace ID

Get the namespace ID from either EDAS or SAE, depending on where your ACM configuration data is managed.

From EDAS

Log on to the EDAS console.
In the left-side navigation pane, choose Resource Management > Microservice Namespace. In the top navigation bar, select a region.
On the Microservices Namespace page, find and copy the namespace ID.

From SAE

Log on to the SAE console.
In the left-side navigation pane, choose Configuration Management > Distributed Configuration (ACM). In the top navigation bar, select a region.
On the Distributed Configuration (ACM) page, select a namespace and copy the namespace ID.

Step 2: Create a migration task

In the MSE Sync console, in the left-side navigation pane, click Service Synchronization.
Click Import Config.
In the Import Config dialog box, paste the following YAML configuration. Replace the placeholder values with your actual environment details, then click OK.

clusters:
  - clusterName: dst
    connectKeyList:
      - <mse-nacos-endpoint>:8848
    clusterType: NACOS
  - clusterName: src
    clusterType: ACM
    product: <EDAS-or-SAE>
    namespaceId: <namespace-id>
    ak: <access-key-id>
    sk: <access-key-secret>
    regionId: <region-id>
    userId: <user-id>
tasks:
  - source: src
    destination: dst
    type: Config

Parameter reference

Parameter	Description	Example
`clusterName`	A user-defined label that identifies each cluster in the task definition. Use `src` for the source and `dst` for the destination.	`src`, `dst`
`connectKeyList`	The endpoint of the MSE Nacos instance, including port 8848.	`mse-xxxxxx-nacos-ans.mse.aliyuncs.com:8848`
`clusterType`	The type of cluster. Use `NACOS` for the destination and `ACM` for the source.	`NACOS`, `ACM`
`product`	The Alibaba Cloud product where ACM is integrated. Set to `EDAS` or `SAE`.	`EDAS`
`namespaceId`	The namespace ID obtained in Step 1.	`cn-hangzhou:my-namespace`
`ak`	The AccessKey ID of the RAM user with ACM read and write permissions.	`LTAI5tXxx`
`sk`	The AccessKey secret of the RAM user.	`xXxXxXx`
`regionId`	The region where the source ACM data is hosted.	`us-east-1`
`userId`	The Alibaba Cloud account ID (UID) of the ACM resource owner. Find this on the Account Management page.	`1419633767709936`

Important

Store AccessKey credentials securely. Do not share them in plain text or commit them to version control.

Step 3: Verify the migration

After the task completes, confirm that the configuration data was synchronized to MSE Nacos.

Log on to the MSE console.
In the top navigation bar, select the region of the MSE Nacos instance.
In the left-side navigation pane, choose Microservices Registry > Instances.
On the Instances page, click the name of the target instance.
In the left-side navigation pane, choose Configuration Management > Configurations.
Verify that the configuration entries from ACM appear in the list.

Tip: Compare the total number of configurations in MSE Nacos against the source ACM namespace to confirm all entries were migrated.

Troubleshooting

Symptom	Likely cause	Action
Task shows no progress	Network connectivity issue between MSE Sync and the source or destination	Verify that MSE Sync can reach both the ACM endpoint and the MSE Nacos endpoint.
Partial data synchronized	MSE Sync node went down mid-migration	Restart MSE Sync and re-run the task. Deploying on at least two nodes prevents this issue.
Authentication error	Incorrect AccessKey ID, AccessKey secret, or insufficient permissions	Verify the RAM user credentials and confirm read and write permissions on ACM.
Namespace not found	Wrong `namespaceId` or `regionId`	Double-check the namespace ID from Step 1 and confirm the region matches.