Run the SMC 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, pay for and remove the two lab instances, then follow Modules 1 to 4 to import the source and run the migration yourself.

Before you start

• You have an Alibaba Cloud International account with a valid payment method.
• The account can create two pay-as-you-go ECS instances 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 every resource below.
• You recorded a strong ECS root password. Do not put it in screenshots or workshop notes.

Step 1 - Activate and authorize the required services

1. Sign in with the Alibaba Cloud account owner and select Philippines (Manila).
2. Open the ECS, VPC, Server Migration Center and Snapshot Service consoles. If a service displays an activation page, review the terms and activate it.
3. In Server Migration Center, click Go to authorize if it appears. Confirm creation of the SMC service-linked role, return to SMC and verify that Migrate to Cloud > Server Migration opens normally.
4. Open ECS Snapshot Service once and activate it if prompted.
5. In ECS, open any available instance and choose Connect > Workbench. If prompted, authorize the ECS Workbench service-linked role.

Expected: SMC opens without an authorization banner, Snapshot Service is active and Workbench can open its connection page.

Step 2 - Choose a zone and create the network

1. In the VPC console, select Philippines (Manila), then open VPC > Create VPC.
2. Create VPC ws-vpc with CIDR 10.10.0.0/16.
3. Create vSwitch ws-vsw-a with CIDR 10.10.1.0/24 in a Manila zone that currently offers a general-purpose 2-vCPU/4-GiB ECS type.
4. In ECS, open Network & Security > Security Groups. Create the basic security group ws-sg in ws-vpc and set its inner access policy to Accept.
5. Add private inbound rules for TCP 8080 and TCP 8703 from 10.10.0.0/16. Keep outbound HTTPS allowed so the SMC client can reach Alibaba Cloud service endpoints.
6. Use Workbench private connectivity for administration. Do not expose SSH or the sample website to 0.0.0.0/0.

Expected: the VPC contains one vSwitch and one security group; no public inbound rule is required for the lab.

Step 3 - Create and initialize the source ECS instance

1. Open ECS Instances & Images > Instances and click Create Instance.
2. 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
   Public IP	Assign a public IPv4 address, pay-by-traffic. The SMC client needs outbound internet access in Module 2.
   Name / hostname	wsNN-source
   Credential	Your strong root password

3. Open Advanced Options > User Data. Copy the complete contents of scripts/source-server-setup.sh.
4. At the top of the copied script, 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 database password.
5. Create the instance and record its instance ID and private IP.
6. After 5-10 minutes, choose Connect > Workbench, sign in as root and run:

   test -f /opt/workshop/.setup-complete && echo READY
   systemctl is-active nginx mysqld
   mysql shopdb -N -e "SELECT COUNT(*) FROM orders;"
   curl -s http://localhost | grep "Legacy Shop"

Expected: READY, two active service results, 10000 orders and a Legacy Shop line containing your participant ID. If the marker is absent, inspect /var/log/workshop-setup.log before continuing.

Step 4 - Create the empty SMC destination

1. Create a second pay-as-you-go Alibaba Cloud Linux 3 ECS instance in the same region, zone, VPC, vSwitch and security group.
2. Use a compatible 2-vCPU/4-GiB class and a system disk of at least 40 GiB.
3. Name it wsNN-smc-target. Do not add user data or important files; SMC replaces its operating system and disks.
4. Record its instance ID and confirm that it is Running.

Step 5 - Continue with the workshop

You do not need the RAM-user Getting Started page. Continue directly to Module 1 - Explore the source server. Module 2 imports the source into SMC and Module 3 creates and runs the job.

Step 6 - Clean up your account

1. After validation, delete wsNN-smc-job. Wait until it disappears, then delete the wsNN-source migration source.
2. Release wsNN-smc-target and wsNN-source after confirming that no retained data is required.
3. In ECS Images, delete the custom image named IMAGE_FROM_SMC_<job-id>, then delete its backing snapshot.
4. Delete any unattached SMC_Temp_Disk that belongs to this job.
5. After no SMC job remains, delete No_Delete_SMC_Transition_SecurityGroup if SMC created it in ws-vpc.
6. Delete ws-sg, then ws-vsw-a, then ws-vpc if they are not used by the DTS workshop.
7. Check ECS Images, Snapshots, Disks, Instances and the billing console one final time.