ALIBABA CLOUD ECS → STACKIT COMPUTE ENGINE
Alibaba Cloud ECS to STACKIT Compute Engine
An Alibaba Cloud ECS instance becomes a STACKIT server: the instance type becomes a STACKIT flavor, the image is rebuilt or imported, and the attached disks and interfaces become volumes and network interfaces. StackToIT reads this from your Alibaba Cloud Terraform and gives the vSwitch, security group and elastic IP around the server a target and a reason as well.
An ECS instance with a data disk, assessed
A small Alibaba Cloud estate written for this page and assessed by StackToIT on 4 November 2026. Left: the input. Right: the result StackToIT recorded for it, an excerpt of assessment.json with the values exactly as the run wrote them.
resource "alicloud_instance" "crm" {
instance_name = "crm-app-01"
instance_type = "ecs.g7.xlarge"
image_id = "ubuntu_22_04_x64_20G_alibase_20240926.vhd"
vswitch_id = alicloud_vswitch.app.id
security_groups = [alicloud_security_group.app.id]
system_disk_category = "cloud_essd"
system_disk_size = 40
data_disks {
name = "crm-data"
category = "cloud_essd"
size = 200
}
}
resource "alicloud_eip_address" "crm" {
address_name = "crm"
bandwidth = "10"
internet_charge_type = "PayByTraffic"
}{
"id": "alicloud_instance.crm",
"result": {
"class": "RECONFIGURE",
"confidence": "MEDIUM",
"target": {
"service": "STACKIT Compute Engine"
},
"reason": "An ECS instance becomes a STACKIT server. The instance type becomes a STACKIT flavor, the image is rebuilt or imported, and the attached disks and interfaces become volumes and network interfaces."
}
}Instance type to flavor
ecs.g7.xlarge becomes a STACKIT flavor. Compute Engine was found in the STACKIT catalogues of eu01 and eu02, with 176 and 58 machine types to choose from.
Data disks read with the instance
The data_disks block is part of the instance unit: the report lists data_disks.category, data_disks.size and data_disks.name among the 10 settings your team carries over.
Elastic IP gets a new address
An elastic IP becomes a STACKIT public IP. The address itself changes, so DNS records and allow lists that name it change too.
Owner per package
The instance goes to the Platform Architect; VPC, vSwitch, security group and elastic IP go to the Network Architect.
The security group, with its rule
From the same run. Left: the input. Right: the result StackToIT recorded for it, an excerpt of assessment.json with the values exactly as the run wrote them.
resource "alicloud_security_group" "app" {
security_group_name = "crm-app"
vpc_id = alicloud_vpc.main.id
}
resource "alicloud_security_group_rule" "https" {
type = "ingress"
ip_protocol = "tcp"
port_range = "443/443"
security_group_id = alicloud_security_group.app.id
cidr_ip = "0.0.0.0/0"
}{
"id": "alicloud_security_group.app",
"result": {
"class": "RECONFIGURE",
"confidence": "LOW",
"target": {
"service": "STACKIT security groups"
},
"reason": "A security group becomes a STACKIT security group. STACKIT rules only allow traffic, so a deny rule or a priority order of the source needs a decision."
}
}Allow rules carry over
STACKIT security group rules only allow traffic, so an ingress rule for tcp 443 has a direct counterpart.
Deny and priority are a decision
A deny rule or a priority order of the source needs a decision, because STACKIT rules only allow traffic. The rule’s cidr_ip, ip_protocol and port_range are listed under the group.
How the ECS estate maps
| Alibaba Cloud resource | STACKIT target | Migration class |
|---|---|---|
| ECS instance with its data disk | STACKIT Compute Engine: server, volumes and network interfaces | Reconfigure |
| Elastic IP | STACKIT public IP | Reconfigure |
| Security group with its rule | STACKIT security groups | Reconfigure |
| VPC | STACKIT network, with a Network Area where routing is needed | Reconfigure |
| vSwitch | STACKIT network with its own address range | Reconfigure |
Classes as the run decided them for 6 resources in 5 units. Waves: VPC and elastic IP first, then vSwitch and security group, then the instance.
Zones and networks
A vSwitch is bound to a zone
crm-app sits in eu-central-1a. It becomes a STACKIT network with the range 10.50.1.0/24, and the assessment asks you to review the zone placement of the workloads on it.
The VPC has no one-to-one counterpart
Its vSwitches become STACKIT networks, and routing between them is planned with a STACKIT Network Area where it is needed.
Core services covered
ECS, cloud disks, VPC and vSwitch, security groups, elastic IPs, CLB, NLB, ALB, ACK, ApsaraDB, OSS, NAS and the message queues each get a STACKIT target. Any other resource goes to your architects as MANUAL_REVIEW.
Proven on a real AWS estate
The AWS Retail Store Sample App, a public Terraform project from AWS, assessed by StackToIT and published in full, exactly as the run wrote it.
View Case Study- 282
- Terraform resource declarations analyzed
- 44
- migration units identified
- 38
- target units generated, from 52 considered
- 331
- plan steps written
Questions infrastructure teams ask
Does StackToIT connect to our Alibaba Cloud account?
No. It reads Terraform and OpenTofu root modules that use the aliyun/alicloud provider. Nothing connects to your Alibaba Cloud account.
What becomes of the ECS instance type?
It becomes a STACKIT flavor. The run checks Compute Engine against the STACKIT catalogues of eu01 and eu02 and names instance_type among the settings your team carries over.
How do the cloud disks move?
A cloud disk becomes a STACKIT volume. The performance category does not carry over: you choose a STACKIT performance class and move the data at the host level or with the server image.
Sources
Your next move: STACKIT.
Tell us about your estate. We show you what StackToIT delivers for it: target architecture, Terraform artifacts and a structured migration plan.