Automatic resource transfer rules move matching resources to a specified resource group based on conditions such as resource names, tags, virtual private clouds (VPCs), or vSwitches. The system scans existing resources against the rules and checks resources again when new resources are created or resource properties change, so that every resource stays in the correct resource group.
Prerequisites
The automatic resource transfer feature is enabled. For instructions, see Enable automatic resource transfer.
Create a custom transfer rule
Log on to the Resource Management console.
In the left-side navigation pane, choose Resource Group > Automatic Resource Transfer.
On the Transfer Based on Custom Rules tab, click Create Rule.
Configure the transfer rule.
Parameter
Description
Rule Name
The name of the automatic transfer rule. The name can contain Chinese characters, letters, digits, hyphens (
-), and underscores (_), and can be up to 128 characters in length.Rule Description
The description of the automatic transfer rule. The description can be up to 512 characters in length.
Effective Scope
All Resources: All resources in the current account that support automatic transfers based on custom rules. For information about supported resource types, see Resource types that support automatic transfers based on custom rules.
NoteIf you select All Resources, newly supported resource types are included by default.
Custom Resource Scope: Specify the resource scope of the transfer rule by resource type, resource group, region, or resource. For an example, see Example 2 in this step.
Destination Resource Group
The resource group to which resources are automatically transferred.
Transfer Conditions
When a resource meets the transfer conditions, the resource is automatically transferred to the destination resource group.
A transfer condition consists of the following parts.
Resource property: Select the condition key used to find matching resources. You can filter resources by resource name, tag, VPC, or vSwitch.
NoteSome resource types do not support tag, VPC, or vSwitch properties and cannot be transferred based on these conditions. Before you configure an automatic transfer rule, check in Resource Center whether the resources to be transferred have the required properties.
Operator: Specify the comparison logic between the resource property and the expected value. Operators such as contains, does not contain, and regular expression match are supported.
Expected value: Specify the value to compare with the actual resource property. The required format varies based on the operator, such as regular expression match.
You can configure transfer conditions in the following ways:
Single condition: Suitable for simple resource filtering scenarios.
Combined conditions: Connect subconditions by using the
andandorlogical operators. Nested conditions are supported for more complex resource filtering scenarios.
Example 1: Automatically transfer all resources that have the
project:project Atag to the Project-A resource group. Configure the transfer condition as follows: select Tag for the resource property, select Contains for the operator, and enterproject:project Afor the expected value.Example 2: Automatically transfer ECS instances that have the
project:project Atag or whose resource names containprojectAto the Project-A resource group.After you select Custom Resource Scope, select the Specify Resource Type Scope check box, select Select by Effective Scope as the selection method, and select the destination resource type in the All Resource Types list on the left. For example, select Instance under Elastic Compute Service (ECS). The selected resource type appears in the Selected Resource Types section on the right.
Click View Matching Resources to preview the resources that match the rule and confirm that the results meet your expectations.
Resources that are created later and meet the conditions are also automatically transferred.
Click OK.
View custom transfer rules and transfer records
Log on to the Resource Management console.
In the left-side navigation pane, choose Resource Group > Automatic Resource Transfer.
On the Transfer Based on Custom Rules tab, click the name of the target rule, or click View in the Actions column.
View the rule details and transfer records.
On the Rule Information tab, view the rule details, including the basic information, rule content, and effective scope.
The Basic Information section includes the rule name, rule ID, rule type, creation time, and modification time. The Rule Content section includes the destination resource group and transfer conditions, such as tag-based matching conditions. The Effective Scope section includes the associated regions, resource groups, resource IDs, and resource types.
On the Transfer Records tab, view the records of successful resource transfers.
This tab provides filter conditions, including Product, Resource Group ID, Resource ID, and a time range. It displays transfer records in a table that includes the Resource ID, Resource Type, Region, Resource Group Name/ID, and Time columns.
Modify or delete a custom transfer rule
Log on to the Resource Management console.
In the left-side navigation pane, choose Resource Group > Automatic Resource Transfer.
On the Transfer Based on Custom Rules tab, find the target rule and click Modify or Delete in the Actions column.
Resource types that support automatic transfers based on custom rules
Cloud service | Resource type name | Resource type code |
Elastic Compute Service (ECS) | Instance | ACS::ECS::Instance |
Dedicated host (DDH) | ACS::ECS::DedicatedHost | |
Image | ACS::ECS::Image | |
Key pair | ACS::ECS::KeyPair | |
Instance launch template | ACS::ECS::LaunchTemplate | |
Security group | ACS::ECS::SecurityGroup | |
Snapshot policy | ACS::ECS::AutoSnapshotPolicy | |
Object Storage Service (OSS) | Bucket | ACS::OSS::Bucket |
Elasticsearch | Instance | ACS::Elasticsearch::Instance |
Logstash | ACS::Elasticsearch::Logstash | |
ApsaraDB for MongoDB | Instance | ACS::MongoDB::DBInstance |
Tair (Redis OSS-compatible) | Instance | ACS::Redis::DBInstance |
PolarDB | Cluster | ACS::PolarDB::DBCluster |
Application Load Balancer (ALB) | Load balancer | ACS::ALB::LoadBalancer |
Access control list | ACS::ALB::Acl | |
Security policy | ACS::ALB::SecurityPolicy | |
Server group | ACS::ALB::ServerGroup | |
Classic Load Balancer (CLB) | Load balancer | ACS::SLB::LoadBalancer |
Access control list | ACS::SLB::AccessControlList | |
Server certificate | ACS::SLB::ServerCertificate | |
CA certificate | ACS::SLB::CACertificate | |
Message Queue for Apache RocketMQ 5.0 | Instance | ACS::RocketMQ::Instance |
PolarDB-X 2.0 | Instance | ACS::DRDS::PolarDBXInstance |
Container Service for Kubernetes | Cluster | ACS::ACK::Cluster |
ApsaraDB RDS | Instance | ACS::RDS::DBInstance |
PolarDB-X 1.0 | Instance | ACS::DRDS::DBInstance |
Bastionhost | Instance | ACS::Bastionhost::Instance |
Microservices Engine (MSE) | Instance | ACS::MSE::Cluster |
Gateway | ACS::MSE::Gateway | |
Network Load Balancer (NLB) | Load balancer | ACS::NLB::LoadBalancer |
Security policy | ACS::NLB::SecurityPolicy | |
Server group | ACS::NLB::ServerGroup | |
Virtual Private Cloud (VPC) | VPC | ACS::VPC::VPC |
DHCP options set | ACS::VPC::DhcpOptionsSet | |
Flow log | ACS::VPC::FlowLog | |
Gateway endpoint | ACS::VPC::GatewayEndpoint | |
High availability (HA) virtual IP address | ACS::VPC::HaVip | |
VPC prefix list | ACS::VPC::PrefixList | |
Traffic mirror filter | ACS::VPC::TrafficMirrorFilter | |
Traffic mirror session | ACS::VPC::TrafficMirrorSession | |
VPN gateway | ACS::VPN::VpnGateway | |
AnalyticDB | Lakehouse cluster | ACS::ADB::DBClusterLakeVersion |
Alibaba Cloud DNS | Domain name resolution | ACS::Alidns::Domain |
Message Queue for Apache Kafka | Instance | ACS::AliKafka::Instance |
Application Real-Time Monitoring Service (ARMS) | Application monitoring app | ACS::ARMS::TraceApp |
Internet Shared Bandwidth | Shared bandwidth | ACS::CBWP::CommonBandwidthPackage |
Cloud Enterprise Network (CEN) | Bandwidth plan | ACS::CEN::CenBandwidthPackage |
CEN instance | ACS::CEN::CenInstance | |
ApsaraDB for ClickHouse | Cluster | ACS::ClickHouse::DBCluster |
Container Registry | Instance | ACS::CR::Instance |
Dynamic Route for CDN (DCDN) | Domain name | ACS::DCDN::Domain |
DataWorks | Workspace | ACS::DataWorks::Project |
Data Transmission Service (DTS) | Instance | ACS::DTS::Instance |
Elastic Container Instance | Container group | ACS::ECI::ContainerGroup |
Enterprise Distributed Application Service (EDAS) | Application | ACS::EDAS::Application |
Cluster | ACS::EDAS::Cluster | |
Intelligent Computing LINGJUN | Cluster | ACS::Eflo::Cluster |
E-MapReduce | Cluster | ACS::EMR::Cluster |
Auto Scaling | Scaling group | ACS::ESS::ScalingGroup |
Realtime Compute for Apache Flink | Workspace | ACS::RealtimeCompute::VvpInstance |
Global Accelerator (GA) | Access control list | ACS::Ga::Acl |
Bandwidth plan | ACS::Ga::BandwidthPackage | |
Basic instance | ACS::Ga::BasicAccelerator | |
AnalyticDB for PostgreSQL | Instance | ACS::GPDB::DBInstance |
Cloud Backup | SAP HANA instance | ACS::HBR::HanaInstance |
Backup vault | ACS::HBR::Vault | |
Lindorm | Instance | ACS::Lindorm::Instance |
Hologres | Instance | ACS::Hologram::Instance |
Simple Log Service | Project | ACS::SLS::Project |
ApsaraDB for HBase | Cluster | ACS::HBase::Cluster |
File Storage NAS | File system | ACS::NAS::FileSystem |
CloudOps Orchestration Service | Common parameter | ACS::OOS::Parameter |
Encrypted parameter | ACS::OOS::SecretParameter | |
Template | ACS::OOS::Template | |
Tablestore | Instance | ACS::OTS::Instance |
PrivateLink | Endpoint | ACS::PrivateLink::VpcEndpoint |
Endpoint service | ACS::PrivateLink::VpcEndpointService | |
Private Zone | Private Zone | ACS::PrivateZone::Zone |
Resource Orchestration Service (ROS) | Stack | ACS::ROS::Stack |