Cross-cloud deployment lets you package nodes, functions, resources, and script templates in a source workspace and deploy them to a destination workspace in a different account, region, or cloud platform — such as Alibaba Finance Cloud or Alibaba Gov Cloud. The process has three stages: create a deployment package in the source workspace, download it to your machine, then import and deploy it in the destination workspace.
Permissions
Different operations require different roles:
| Operation | Required role |
|---|---|
| Create a deployment environment | Workspace Administrator |
| Deploy tasks to the production environment of the source workspace | O&M, Deploy, or Workspace Administrator |
| Create a deployment package | Development |
| Deploy a package (in both source and destination workspaces) | O&M, Deploy, or Workspace Administrator |
To add workspace members or adjust roles, see Manage permissions on workspace-level services.
Limitations
Supported environment combinations
Cross-cloud deployment supports specific source–destination workspace combinations. Standard mode workspaces are not supported as either source or destination.
| Source workspace mode | Source DataStudio version | Destination: basic mode, DataStudio (new version) | Destination: basic mode, DataStudio (legacy version) | Destination: standard mode, DataStudio (new version) | Destination: standard mode, DataStudio (legacy version) |
|---|---|---|---|---|---|
| Basic mode | DataStudio (new version) |  | Unsupported | | Unsupported |
| Basic mode | DataStudio (legacy version) | Unsupported | | Unsupported | |
| Standard mode | — | Unsupported | Unsupported | Unsupported | Unsupported |
Cross-workspace vs. cross-cloud deployment
Cross-workspace deployment moves objects between workspaces within the same Alibaba Cloud account and the same region. It does not support cross-region scenarios. To deploy across regions, use Deploy Center instead.
How it works
Cross-cloud deployment moves objects from a source workspace to a destination workspace through three stages:
Create a deployment package — Select the committed nodes, functions, resources, and script templates you want to deploy, choose a cross-cloud deployment environment, and generate a deployment package.
Download the package — Download the deployment package from the source workspace to your machine.
Import and deploy — Upload the package to the destination workspace, preview the contents, and deploy.
For the detailed logic behind each stage, see Logic description.
Create a deployment package in the source workspace
In the left-side navigation pane of Deploy Center, click Deployment Package Creation.
NoteThe Deployment Package Creation page lists all committed nodes in the current workspace. Only committed nodes can be packaged. A node can be repackaged only when the status of its existing deployment package is Deployed or Failed.
On the Deployment Package Creation page, select a cross-cloud deployment environment for the package.
Use the search filters — Solution, Workflow, and Node Type — to find the objects you want to deploy.
Select the objects and click Batch Add to Deployment Package to add them to the deployment queue. The count of pending objects appears in the upper-right corner of the Nodes to Deploy button.
NoteTo deploy a small number of objects individually, find each object in the list and click Deploy in the Actions column. Follow the prompts in the Deployment Confirmation dialog box.
Click Nodes to Deploy to review the objects in the queue. Check the ID, Node Type, Change Type, and Node Status for each object. To inspect or remove an object, click View Details or Remove in the Actions column.
Click Deployment Package Creation. In the Deployment Confirmation dialog box, enter a name in the Deployment Package Name field, then confirm the deployment environment and the list of objects.
Click Deployment Package Creation to generate the package.
After the package is created, go to the Deployment Packages page to download it before proceeding.
Deployment packages expire after 30 days. Download and save the package immediately after creation. After 30 days, the package can no longer be downloaded and you must create a new one.
When does the deployment take effect?
The deployment schedule depends on the instance generation mode of each node:
Next Day mode:
Deployed before 23:30 — takes effect on the instance generated the next day.
Deployed after 23:30 — takes effect on the instance generated on the third day.
Immediately After Deployment mode:
Scheduling time is at least 10 minutes after deployment — the updated instance is generated as scheduled.
Scheduling time is within 10 minutes after deployment, or you deploy after 23:30 — the updated instance is generated on the third day.
Download the deployment package from the source workspace
In the left-side navigation pane of Deploy Center, click Deployment Packages.
On the Deployment Packages page, find the package you want to download. Use the filters — Deployed By, Deployed On, Deployment Status, and Deployment Environment — to narrow the list.
Click Download in the Actions column.
In the confirmation message, verify the package details and click OK.
Deployment packages expire after 30 days. Download the package immediately after creation. After 30 days, the package is no longer available for download and you must create a new one.
Import the deployment package to the destination workspace
Log in to the destination workspace and go to Deploy Center > Deployment Package Creation.
In the upper-right corner, click Import Deployment Package.
Enter a name in the Deployment Package Name field, then select an upload method:
Upload On-premises File — Upload the package directly from your machine. Use this method when the package size is 30 MB or smaller.
Upload from OSS — Upload the package to Object Storage Service (OSS) first, then provide the OSS URL. Use this method when the package exceeds 30 MB. For upload instructions, see Upload objects. For URL instructions, see Use object URLs.
Click Preview Deployment Package to review the deployment environment and the list of objects.
Click Deploy to deploy the package.
ImportantIf a deployment package with the same name already exists in the destination workspace, the new package overwrites it on first deployment. Verify the package name before proceeding.
What's next
After deployment, go to the Deployment Packages page of the current workspace to view the deployment results. See View the deployment packages.