Run the DTS workshop in your own Alibaba Cloud account

Use this page when you are signing in as the Alibaba Cloud account owner instead of using a facilitator-provided RAM user. You create, purchase and remove the source ECS, target RDS and DTS migration instance before following Modules 1 to 5.

Use a disposable training account

The account owner can purchase and delete resources throughout the account. Do not run this lab in an account containing production databases or unrelated DTS tasks.

Incremental migration is billable while Running

Schema and full migration do not incur DTS instance charges, but incremental migration continues running and billing until you pause or release it. ECS and RDS are billed separately. Estimate current Manila pricing and create a budget alert before buying.

Before you start

You have an Alibaba Cloud International account with a valid payment method.
The account can create one pay-as-you-go ECS instance, one RDS MySQL instance and one DTS Data Migration instance in Philippines (Manila).
You downloaded this workshop project and can open scripts/source-server-setup.sh.
In the website sidebar, set the participant ID to ws01. Use that name for the resources below.
You have recorded a strong ECS root password. Database passwords will be created during Modules 1 and 2.

Step 1 - Activate services and authorize DTS

Sign in with the Alibaba Cloud account owner and select Philippines (Manila).
Open ECS, VPC, ApsaraDB RDS for MySQL, Data Transmission Service and RAM. If a service asks for activation, review the terms and activate it.
In DTS, open its quick-authorization or service-authorization page.
Review and authorize the service role for dts.aliyuncs.com.
Open RAM Identities > Roles. Confirm AliyunDTSDefaultRole exists and has AliyunDTSRolePolicy attached.
In ECS, choose Connect > Workbench on any available instance. If prompted, authorize the ECS Workbench service-linked role.

Expected: DTS opens without an authorization prompt, the default role is visible in RAM and Workbench opens its connection page.

Step 2 - Choose an RDS-supported zone

Open ApsaraDB RDS and click Create Instance, but do not submit the purchase.
Select Philippines (Manila), MySQL 8.0, Basic Edition and cloud ESSD.
Record a zone where that combination and a small training class are available, then cancel the wizard.

Instance types and stock change. The zone chosen here must also be used by the vSwitch and source ECS instance.

Step 3 - Create the private network

In VPC, select Philippines (Manila), then open VPC > Create VPC.
Create VPC ws-vpc with CIDR 10.10.0.0/16.
Create vSwitch ws-vsw-a with CIDR 10.10.1.0/24 in the RDS-supported zone selected above.
In ECS Network & Security > Security Groups, create the basic security group ws-sg in ws-vpc. Set its inner access policy to Accept.
Do not add TCP 3306 from 0.0.0.0/0. DTS adds its service CIDRs during the connectivity test; ECS-to-RDS validation uses an RDS private whitelist entry.

If you already completed the own-account SMC setup and these three network resources exist, reuse them instead of creating duplicates.

Step 4 - Create and initialize the source ECS instance

If wsNN-source already exists from the own-account SMC setup and its readiness checks pass, reuse it and skip to Step 5.

Open ECS Instances & Images > Instances and click Create Instance.

Choose:

Setting	Value
Billing	Pay-as-you-go
Region / zone	Philippines (Manila) / the `ws-vsw-a` zone
Instance type	Available general-purpose type with 2 vCPU and 4 GiB RAM
Image	Alibaba Cloud Linux 3, x86_64
System disk	40 GiB ESSD or an available equivalent
Network	`ws-vpc`, `ws-vsw-a`, `ws-sg`
Name / hostname	`wsNN-source`
Credential	Your strong root password

Open Advanced Options > User Data. Paste the complete contents of scripts/source-server-setup.sh.
Set PARTICIPANT_ID to wsNN and replace the default DB_ROOT_PASSWORD. Follow the script comment: do not use spaces, quotes or backslashes in that password.
Create the instance and record its instance ID and private IP.

After 5-10 minutes, connect through Workbench as root and run:

test -f /opt/workshop/.setup-complete && echo READY
systemctl is-active mysqld
mysql shopdb -N -e "SELECT COUNT(*) FROM orders;"
mysql -N -e "SELECT @@log_bin, @@binlog_format, @@binlog_row_image, @@server_id, @@binlog_expire_logs_seconds;"

Expected: READY, active, 10000, then 1, ROW, FULL, a server ID greater than 1 and retention of at least 604800. If not, inspect /var/log/workshop-setup.log and do not purchase DTS yet.

Step 5 - Create the RDS destination

In ApsaraDB RDS, click Create Instance.

Choose:

Setting	Value
Billing	Pay-as-you-go
Region / zone	Philippines (Manila) / the selected supported zone
Engine / version	MySQL 8.0
Edition	Basic Edition
Storage	cloud ESSD, 20 GiB
Instance class	Smallest available class suitable for this training workload
Network	`ws-vpc`, `ws-vsw-a`
Name	`wsNN-rds`

Confirm the current hourly price, create the instance and wait until its status is Running.
Do not create shopdb; DTS creates it during schema migration. Do not request a public endpoint.
Record the RDS instance ID and internal endpoint.

Step 6 - Purchase one DTS migration instance

Open DTS and choose Data Migration.
Click Create Task or Purchase Instance, depending on the current console label.
Choose pay-as-you-go Data Migration, source database MySQL, destination database MySQL, source region Philippines (Manila), destination region Philippines (Manila), one-way architecture and class small.
Review the order and buy exactly one instance. Do not configure its endpoints in the purchase wizard if the console allows you to purchase first.
Return to Data Migration, select Philippines (Manila) and locate the new task by its DTS instance ID.
If its default name is similar to philippines-small, open Configure Task and set Task Name to wsNN-dts-migration.

Expected: one migration task is listed with your DTS instance ID and status Not Configured. Stop if the order created more than one task.

Step 7 - Continue with the workshop

You do not need the RAM-user Getting Started page. Continue to Module 1 - Prepare the source MySQL, then complete Modules 2 to 5.

Differences in owner mode

You can see purchase, release and configuration actions that are denied to workshop RAM users. Use only the actions named in the modules.
You created the ECS, RDS and DTS instance yourself; there is no credential sheet or facilitator.
During connectivity testing, allow DTS to add its service CIDRs. Never replace private connectivity with a public MySQL endpoint.

Step 8 - Pause and clean up

After Module 5, open wsNN-dts-migration and click Pause Task. Confirm its status becomes Paused so incremental billing stops.
Record any result you need, then release/delete the DTS migration instance from the DTS console. Confirm it disappears from the Philippines (Manila) task list.
In RDS, release wsNN-rds after deciding whether any backup must be retained. Check the recycle bin and retained backups for continuing charges.
Release wsNN-source and its disks if it is not still required by the SMC workshop.
Delete ws-sg, then ws-vsw-a, then ws-vpc only after no SMC or DTS resource uses them.
Audit DTS, RDS, ECS instances, disks, snapshots and the billing console. Check other regions for accidental resources.

Ready

The source MySQL prerequisites pass, RDS is Running, exactly one unconfigured DTS task exists and you understand that you must pause and release it yourself.