When you migrate applications between Alibaba Cloud environments or accounts, manually recreating deployment configurations is time-consuming and error-prone. Enterprise Distributed Application Service (EDAS) lets you export an application's configuration and deployment package from one environment, then import it into the destination environment or account to deploy the application with the original settings intact.
Prerequisites
Before you begin, make sure that you have:
An exported application JSON file from the source EDAS environment. See Export applications
(Conditional) The application deployment package, if you are migrating across different Alibaba Cloud environments
Migration scenarios
EDAS supports two migration scenarios. The scenario determines whether you need to upload a deployment package along with the configuration file.
| Migration path | Example | Deployment package required |
|---|---|---|
| Within the same Alibaba Cloud environment (cross-account or cross-region) | From a development account to a production account in public cloud | No |
| Across different Alibaba Cloud environments | From public cloud to Alibaba Finance Cloud | Yes |
Choose an import method
EDAS provides two import methods. Choose the method that matches your migration requirements.
| Method | When to use | What you configure |
|---|---|---|
| Quick import | Standard migrations where the default deployment settings are acceptable | Application name, microservices namespace, cluster, Kubernetes namespace, and replica count |
| Custom import | Migrations that require specific deployment packages, resource quotas, image settings, scheduling rules, or lifecycle hooks. Supports Java applications only. | Full deployment configuration including package source, pod resources, image settings, scheduling rules, and lifecycle hooks |
Quick import an application
Use quick import for straightforward migrations where you only need to specify basic deployment parameters.
Log on to the EDAS console.
In the left-side navigation pane, choose .
On the Applications page, click Import Application.
In the Select Common Files section of the Upload Application dialog box, upload the exported JSON file and click OK.
NoteIf you are migrating across Alibaba Cloud environments, you must also upload the deployment package. If the migration stays within the same environment, skip the package upload.
In the Import Confirmation dialog box, review the application details and click Quick Import.
In the Import dialog box, configure the following parameters and click OK.
Parameter Description Application Name Name of the imported application. Microservices Namespace Target microservices namespace for deployment. Cluster Name Target Kubernetes cluster. Kubernetes Namespace Kubernetes namespace for the application. Replica Number of pod replicas to deploy. Wait for the import to complete. To monitor progress, go to the Applications page and click Details to open the Import/Export Records panel.
Custom import an application
Use custom import when you need full control over deployment settings, including package source, resource quotas, and image configurations.
Custom import supports Java applications only. PHP and multi-language applications are not supported.
Upload the application configuration
Log on to the EDAS console.
In the left-side navigation pane, choose .
On the Applications page, click Import Application.
In the Select Common Files section of the Upload Application dialog box, upload the exported JSON file and click OK.
NoteIf the source and destination cloud environments differ, the Upload Offline Package section appears. Select Upload Local Package to upload a local file, or Offline Package URL to provide a download URL.
In the Import Confirmation dialog box, click Import.
Configure environment and basic settings
In the Configurations step of the Edit Imported Application wizard, configure the following settings and click Next.
Parameter Description Microservices Namespace Target microservices namespace. Defaults to Default if none is selected. To create a namespace, click Create Microservices Namespace. See Manage a microservices namespace. Cluster Container Service for Kubernetes (ACK) cluster for deployment. Select an imported cluster from the drop-down list. To use a cluster not yet imported to EDAS, select the first-time import option -- the cluster is imported when the application is created, which consumes additional time. Then, check whether Alibaba Cloud Service Mesh is activated. A cluster does not need to reside in the same microservices namespace as the application. K8s Namespace Kubernetes namespace for the application. Built-in values: default (used when an object does not belong to a specific namespace), kube-system (for objects created by the system), kube-public (automatically created by the system, readable by all users including unauthenticated users). To create a custom namespace, click Create Kubernetes Namespace. Names support digits, lowercase letters, and hyphens (-), must be 1 to 63 characters, and must start and end with a letter or digit. Application Name Name for the imported application. Must start with a letter, supports digits, letters, and hyphens (-), up to 36 characters. Application Description Optional description, up to 128 characters. Total Pods Number of pods for deployment. The range depends on cluster capacity. Single-pod Resource Quota CPU and memory limits per pod. The default value 0means no limit. If you do not specify quotas, the quotas vary based on the cluster performance.
Configure the deployment package (JAR or WAR)
The following parameters apply when you deploy with a JAR or WAR package.
| Parameter | Description |
|---|---|
| Source of Deployment Package | Package source. Defaults to Custom Program. If you modify the package, the updated package is used. Otherwise, the offline program package is used. |
| File Uploading Method | For JAR deployment: Upload JAR Package (upload a local file) or JAR Package Address (provide a URL). For WAR deployment: Upload WAR Package or WAR Package Address. High-speed Service Framework (HSF) applications use a WAR or FatJar package. |
| Version | Application version number. Enter a custom version or click Use Timestamp as Version Number to auto-generate one. |
Configure the container image
The following parameters apply when you deploy with a container image.
| Parameter | Description |
|---|---|
| Image Type | Fixed to Configure Image. |
| Alibaba Cloud Container Registry | If set to Current Account, configure Region, Container Registry, Image Repository Namespace, and Image Repository Name, then select an image version. If set to Other Alibaba Cloud Accounts, specify the Full Image Address for a public repository. For a private repository, use the aliyun-acr-credential-helper component to pull images. See Use the aliyun-acr-credential-helper component to pull images without using a secret. |
If a Resource Access Management (RAM) user deploys an application with an image from Container Registry Enterprise Edition, the RAM user must have the required permissions. See Configure policies for RAM users to access Container Registry.
Configure advanced settings (optional)
In the Advanced Settings step, configure the following settings as needed:
Complete the import
Click Complete Configuration, then click Confirm Import.
Wait for the import to complete. To monitor progress, go to the Applications page and click Details to open the Import/Export Records panel.