This topic describes the managed rules that are related to Alibaba Cloud dedicated hosts (DDHs) and the rectification methods that target at non-compliant DDHs.

Rule name: ddh-cpu-min-count-limit

Checks whether the number of vCPUs of an DDH under your account is greater than or equal to the threshold that you set.

Trigger type: configuration change

Applicable resource type: ACS::ECS::DedicatedHost

Input parameter: cpuCount. It specifies the minimum number of vCPUs in a DDH.

Non-compliance description: The number of vCPUs of a DDH under your account is smaller than the threshold that you set. You can use one of the following methods to rectify resource non-compliance:
  • Rectification method 1: Create a DDH and select a specification that complies with the rule as you cannot change the specification of a DDH after it is created. Cloud Config detects your modification and automatically starts to evaluate the resource within 10 minutes.

    For a DDH that is evaluated as non-compliant, you can manually release the DDH if it adopts the pay-as-you-go billing method. If the DDH adopts the subscription billing method, you cannot manually release it.

    Risks: After a DDH is released, resources related to the DDH becomes unavailable. All data of the Elastic Compute Service (ECS) instances on the DDH will be lost and cannot be restored. Before you release a DDH, you can migrate the ECS instances on the DDH to another DDH under your account as required.

    For more information about how to migrate ECS instances between DDHs, see Migrate ECS instances between different dedicated hosts.

  • Rectification method 2: Change the value of the input parameter and click Re-evaluate on the details page of the rule.

    For more information about how to view the number of vCPUs of a DDH in the ECS console, see View the resources of a dedicated host.

Rule name: ddh-memory-min-size-limit

Checks whether the memory size of a DDH under your account is greater than or equal to the threshold that you set.

Trigger type: configuration change

Applicable resource type: ACS::ECS::DedicatedHost

Input parameter: memorySize. It specifies the minimum memory size. Unit: GiB.

Non-compliance description: The memory size of a DDH under your account is less than the threshold that you set. You can use one of the following methods to rectify resource non-compliance:
  • Rectification method 1: Create a DDH and select a specification that complies with the rule as you cannot change the specification of a DDH after it is created. Cloud Config detects your modification and automatically starts to evaluate the resource within 10 minutes.

    For a DDH that is evaluated as non-compliant, you can manually release the DDH if it adopts the pay-as-you-go billing method. If the DDH adopts the subscription billing method, you cannot manually release it.

    Risks: After a DDH is released, resources related to the DDH becomes unavailable. All data of the ECS instances on the DDH will be lost and cannot be restored.

    Before you release a DDH, you can migrate the ECS instances on the DDH to another DDH under your account as required.

    For more information about how to migrate ECS instances between DDHs, see Migrate ECS instances between different dedicated hosts.

  • Rectification method 2: Change the value of the input parameter and click Re-evaluate on the details page of the rule.

    For more information about how to view the memory size of a DDH in the ECS console, see View the resources of a dedicated host.

Rule name: ddh-socket-min-count-limit

Checks whether the number of physical CPUs, namely CPU sockets, of a DDH under your account is greater than or equal to the threshold that you set.

Trigger type: configuration change

Applicable resource type: ACS::ECS::DedicatedHost

Input parameter: socketCount. It specifies the minimum number of physical CPUs.

Non-compliance description: The number of physical CPUs of a DDH under your account is smaller than the threshold that you set. You can use one of the following methods to rectify resource non-compliance:
  • Rectification method 1: Create a DDH and select a specification that complies with the rule as you cannot change the specification of a DDH after it is created. Cloud Config detects your modification and automatically starts to evaluate the resource within 10 minutes.

    For a DDH that is evaluated as non-compliant, you can manually release the DDH if it adopts the pay-as-you-go billing method. If the DDH adopts the subscription billing method, you cannot manually release it.

    Risks: After a DDH is released, resources related to the DDH becomes unavailable. All data of the ECS instances on the DDH will be lost and cannot be restored.

    Before you release a DDH, you can migrate the ECS instances on the DDH to another DDH under your account as required.

    For more information about how to migrate ECS instances between DDHs, see Migrate ECS instances between different dedicated hosts.

  • Rectification method 2: Change the value of the input parameter and click Re-evaluate on the details page of the rule.

    For more information about how to view the number of physical CPUs of a DDH, see View the resources of a dedicated host.