Resource Orchestration Service:CreateTemplateScratch

Limits

Only specific resource types support the resource scenario feature. For more information, refer to Resource types that support scenarios.

Description

Resource Orchestration Service (ROS) provides the resource scenario feature. You can select a resource scope in the UI and perform operations such as replication or management of a group of resources, helping simplify resource management. For more information about resource scenarios, refer to Overview.

Resource replication scenario

If you want to replicate a collection of resources and dependencies between the resources, you can create a resource replication scenario. This type of scenario lets you replicate all existing resources within the specified scope and generate a collection of resources that have the same architecture as the existing resources. For more information, refer to Resource replication scenario.

Resource profiling scenario

If the relationships between resources that you want to create are complicated, you can create a resource profiling scenario to preview the overall resource architecture or the architecture starting from a specific resource. This helps simplify resource management. For more information, refer to Resource detection scenario.

Resource management scenario

If you need to import a collection of existing resources into a new resource stack for unified management, you can create a resource management scenario. For more information, refer to Resource management scenario.

Resource migration scenario

If you want to migrate a collection of resources and dependencies between the resources, you can create a resource migration scenario. When you migrate the resources, ROS generates a stack. You can view the migration progress on the Stacks tab of the scenario details page. After you migrate the resources, you can delete source resources. For more information, refer to Resource migration scenario.

This topic provides an example of how to create a resource replication scenario in the China (Hangzhou) region to replicate a virtual private cloud (VPC) with the ID of vpc-bp1m6fww66xbntjyc****.

Additional notes on request parameters

For more information, refer to Common parameters.

When you specify different values for the TemplateScratchType parameter, the valid values of ParameterKey and ParameterValue also differ.

Resource replication scenario

The following table describes the valid values of ParameterKey and ParameterValue when you set TemplateScratchType to ArchitectureReplication.

• false: does not replicate ECS instance data. | | InstancePeriod | The subscription duration of the destination subscription ECS instance. By default, the subscription duration of the source instance is used. | | InstancePeriodUnit | The unit of the subscription duration of the destination subscription ECS instance. By default, the subscription duration unit of the source instance is used. Valid values:* Week

• Month

• Year | | InstanceAmount | The number of ECS instances to be replicated. This parameter takes effect only when the source resource is a single ECS instance. | | RamAttachedPolicyReplication | Specifies whether to replicate the RAM policy associated with RAM users, user groups, and roles. Default value: false. Valid values:* true

• false | | AlbLoadBalancerEdition | The edition of the ALB instance. The features and billing rules vary based on the edition. Valid values:* Basic: Basic Edition

• Standard: Standard Edition

• StandardWithWaf: Web Application Firewall (WAF)-enabled EditionExample: Standard. | | AlbAddressType | The type of the address of the ALB instance. Valid values:* Internet: The ALB instance has a public IP address. The Domain Name System (DNS) domain name is resolved to the public IP address. Therefore, the ALB instance can be accessed over the Internet.

• Intranet: The ALB instance has only a private IP address. The DNS domain name is resolved to the private IP address. Therefore, the ALB instance can be accessed only within the VPC where the ALB instance is deployed.Example: Internet. | | AlbAddressIpVersion | The IP version. Valid values:* IPv4: IPv4

• DualStack: dual stackExample: IPv4. | | AlbZoneMappings | The mappings between zones and vSwitches. You can specify at most 10 zones. If the selected region supports two or more zones, select at least two zones to ensure the high availability of your service. The value is a JSON string that has the same structure as the ZoneMappings parameter in the ALB CreateLoadBalancer operation. Example: [{"ZoneId": "cn-bejing-g": "VSwitchId": "vsw-gersdf****"}, {"ZoneId": "cn-bejing-f": "VSwitchId": "vsw-fersdf****"}] | | SlbListenerProtocols | The listener protocol of a CLB instance. Specifies the listener protocols to be included in the replication. You can set one or more protocols, separated by commas. By default, no restriction is applied. Valid values:* tcp

• udp

• http

• httpsExample: tcp,udp. |

Resource profiling scenario

The following table describes the valid values of ParameterKey and ParameterValue when you set TemplateScratchType to ArchitectureDetection.

Resource management scenario

The following table describes the valid values of ParameterKey and ParameterValue when you set TemplateScratchType to ResourceImport.

• udp

• http

• httpsExample: tcp,udp. |

Resource migration scenario

The following table describes the valid values of ParameterKey and ParameterValue when you set TemplateScratchType to ResourceMigration.