Template ID
Supported regions
Hangzhou, Shenzhen, Shanghai
Template architecture

Parameter variables
Parameter variable types include String, etc., with relevant values passed through variables.
If not specified, the default value will be applied. For modifications to the template variable configuration, see:Template Variable Configuration.
Ordinal Number | Variable Name | Variable Type | Default Value | Description |
1 | Region | String | cn-hangzhou | Hangzhou Region |
2 | ${vpc_DMZ_name} | String | vpc_DMZ | DMZ area VPC name |
3 | ${vpc_DMZ_IP} | String | 172.16.0.0/16 | DMZ area VPC CIDR block |
4 | ${vsw_DMZ_APP_AZ1_name} | String | DMZ-vsw-J | DMZ area - application switch 1 name |
5 | ${vsw_DMZ_APP_AZ1_IP} | String | 172.16.0.0/24 | DMZ area - application switch 1 CIDR block |
6 | ${vsw_DMZ_APP_AZ2_name} | String | DMZ-vsw-K | DMZ area - application switch 2 name |
7 | ${vsw_DMZ_APP_AZ2_IP} | String | 172.16.1.0/24 | DMZ area - application switch 2 CIDR block |
8 | ${vsw_DMZ_tr_AZ1_name} | String | DMZ-tr-J | DMZ area - tr switch 1 name |
9 | ${vsw_DMZ_tr_AZ1_IP} | String | 172.16.3.0/24 | DMZ area - tr switch 1 CIDR block |
10 | ${vsw_DMZ_tr_AZ2_name} | String | DMZ-tr-K | DMZ area - tr switch 2 name |
11 | ${vsw_DMZ_tr_AZ2_IP} | String | 172.16.4.0/24 | DMZ area - tr switch 2 CIDR block |
12 | ${vpc_Prod_name} | String | vpc_Prod | Prod area VPC name |
13 | ${vpc_Prod_IP} | String | 172.17.0.0/16 | Prod area VPC CIDR block |
14 | ${vsw_Prod_APP_AZ1_name} | String | Prod-vsw-J | Prod area - application switch 1 name |
15 | ${vsw_Prod_APP_AZ1_IP} | String | 172.17.0.0/24 | Prod area - application switch 1 CIDR block |
16 | ${vsw_Prod_APP_AZ2_name} | String | Prod-vsw-K | Prod area - application switch 2 name |
17 | ${vsw_Prod_APP_AZ2_IP} | String | 172.17.1.0/24 | Prod area - application switch 2 CIDR block |
18 | ${vsw_Prod_tr_AZ1_name} | String | Prod-tr-J | Prod area - tr switch 1 name |
19 | ${vsw_Prod_tr_AZ1_IP} | String | 172.17.2.0/24 | Prod area - tr switch 1 CIDR block |
20 | ${vsw_Prod_tr_AZ2_name} | String | Prod-tr-K | Prod area - tr switch 2 name |
21 | ${vsw_Prod_tr_AZ2_IP} | String | 172.17.3.0/24 | Prod area - tr switch 2 CIDR block |
22 | ${vpc_Dev_name} | String | vpc_Dev | Dev area VPC name |
23 | ${vpc_Dev_IP} | String | 172.18.0.0/16 | Dev area VPC CIDR block |
24 | ${vsw_Dev_APP_AZ1_name} | String | Dev-vsw-J | Dev area - application switch 1 name |
25 | ${vsw_Dev_APP_AZ1_IP} | String | 172.18.1.0/24 | Dev area - application switch 1 CIDR block |
26 | ${vsw_Dev_APP_AZ2_name} | String | Dev-vsw-K | Dev area - application switch 2 name |
27 | ${vsw_Dev_APP_AZ2_IP} | String | 172.18.2.0/24 | Dev area - application switch 2 CIDR block |
28 | ${vsw_Dev_tr_AZ1_name} | String | Dev-tr-J | Dev area - tr switch 1 name |
29 | ${vsw_Dev_tr_AZ1_IP} | String | 172.18.3.0/24 | Dev area - tr switch 1 CIDR block |
30 | ${vsw_Dev_tr_AZ2_name} | String | Dev-tr-K | Dev area - tr switch 2 name |
31 | ${vsw_Dev_tr_AZ2_IP} | String | 172.18.4.0/24 | Dev area - tr switch 2 CIDR block |
32 | ${nlb_name} | String | nlb | nlb instance name |
33 | ${nat_name} | String | nat | nat instance name |
34 | ${eip_name} | String | eip-out | eip instance name |
Command line debugging
YAML file parameter configuration example (the default VPC, switch, security group,IPv4, route table are all newly created):
template_id: H1IH327YSFQ11L18
area_id: "cn-hangzhou"
variables:
${vpc_DMZ_name}: "vpc_DMZ"
${vpc_DMZ_IP}: "172.16.0.0/16"
${vsw_DMZ_APP_AZ1_name}: "DMZ-vsw-J"
${vsw_DMZ_APP_AZ1_IP}: "172.16.0.0/24"
${vsw_DMZ_APP_AZ2_name}: "DMZ-vsw-K"
${vsw_DMZ_APP_AZ2_IP}: "172.16.1.0/24"
${vsw_DMZ_tr_AZ1_name}: "DMZ-tr-J"
${vsw_DMZ_tr_AZ1_IP}: "172.16.3.0/24"
${vsw_DMZ_tr_AZ2_name}: "DMZ-tr-K"
${vsw_DMZ_tr_AZ2_IP}: "172.16.4.0/24"
${vpc_Prod_name}: "vpc_Prod"
${vpc_Prod_IP}: "172.17.0.0/16"
${vsw_Prod_APP_AZ1_name}: "Prod-vsw-J"
${vsw_Prod_APP_AZ1_IP}: "172.17.0.0/24"
${vsw_Prod_APP_AZ2_name}: "Prod-vsw-K"
${vsw_Prod_APP_AZ2_IP}: "172.17.1.0/24"
${vsw_Prod_tr_AZ1_name}: "Prod-tr-J"
${vsw_Prod_tr_AZ1_IP}: "172.17.2.0/24"
${vsw_Prod_tr_AZ2_name}: "Prod-tr-K"
${vsw_Prod_tr_AZ2_IP}: "172.17.3.0/24"
${vpc_Dev_name}: "vpc_Dev"
${vpc_Dev_IP}: "172.18.0.0/16"
${vsw_Dev_APP_AZ1_name}: "Dev-vsw-J"
${vsw_Dev_APP_AZ1_IP}: "172.18.1.0/24"
${vsw_Dev_APP_AZ2_name}: "Dev-vsw-K"
${vsw_Dev_APP_AZ2_IP}: "172.18.2.0/24"
${vsw_Dev_tr_AZ1_name}: "Dev-tr-J"
${vsw_Dev_tr_AZ1_IP}: "172.18.3.0/24"
${vsw_Dev_tr_AZ2_name}: "Dev-tr-K"
${vsw_Dev_tr_AZ2_IP}: "172.18.4.0/24"
${nlb_name}: "nlb"
${nat_name}: "nat"
${eip_name}: "eip-out"
configuration:
enableMonitor: "0"
enableReport: "0"Note:
1. If you change the region, replace the area_id field, such as Hangzhou "cn-hangzhou", with Shanghai "cn-shanghai".
For more information, see the referenced document.
2. The TR route table is configured with a custom route to the NAT Gateway. After deployment, manual routing configuration is not required.
Template Library Address:
Code Example Address:
Visualization Method
Batch create related Alibaba Cloud services, including 3 VPCs, 12 switches, and 1 NAT Gateway.
Create a new application based on the template. The default region is Hangzhou, and all cloud products are newly created.
Complete application saving, and perform verification and pricing separately. All related cloud products are billed on a pay-as-you-go basis.
After verification, confirm the protocol to start batch deployment and automatically complete the routing configuration.
Integrated API Invocation Method
Quickly complete usage through a set of openAPI interfaces with integrated API.
Initialize according to the command line tool in the referenced document.
Deploy and output directly according to the model YAML file.
If you change the region, replace the area_id field, such as Hangzhou "cn-hangzhou", with Shanghai "cn-shanghai".