ddh-cpu-min-count-limit

If the number of VCPUs of an Alibaba Cloud DDH instance under your account is greater than or equal to the threshold you set, the ECS instance is deemed to be compliant.

Trigger type: configuration change

Resource: ACS:: ECS:: DedicatedHost

Request parameters:

CpuCount (number of CPU cores)

Solution: when the total CPU usage of the DDH instance under your account is smaller than the threshold value you set, the rule is not compliant.

  • Method 1: After a DDH is created, you cannot change its specification. You need to create a DDH that meets the rules. Config detects your changes within 10 minutes and automatically starts the audit.

    Solution to non-compliant old ddhs: Release the DDH (only pay-as-you-go ddhs are supported). You cannot manually release a subscription DDH.

    Risk: After a DDH is released, all its resources are no longer available. All data on ECS instances on a DDH is lost and cannot be recovered. You can migrate ECS instances between ddhs of your account before the DDH is released.

    To migrate ECS instances between different ddhs, see Migrate ECS instances between different dedicated hosts.

  • Method 2: modify the threshold of rule parameters, and click re-audit. Then, refresh the page for verification.

    View the CPU size when you create a host in the console:

    DDH_1

ddh-memory-min-size-limit

If the memory capacity of an Alibaba Cloud DDH instance under your account is greater than or equal to the threshold you set, it is deemed as compliance.

Trigger type: configuration change

Resource: ACS::ECS::DedicatedHost

Request parameters:

memorySize (memory size/GB)

Troubleshooting: when the memory capacity of the DDH instance under your account is smaller than the threshold value you set, the rule is not compliant.

  • Method 1: After a DDH is created, you cannot change its specification. Instead, you can create a DDH that meets the rules. Config detects your changes within 10 minutes and automatically starts the audit.

    To troubleshoot an invalid DDH, release the DDH. ( Only pay-as-you-go ddhs are supported. You cannot manually release a subscription DDH.

    Risk: After a DDH is released, all its resources are no longer available. All data on ECS instances on a DDH is lost and cannot be recovered.

    You can migrate ECS instances between ddhs of your account before the DDH is released.

    To migrate ECS instances between different ddhs, see Migrate ECS instances between different dedicated hosts.

  • Method 2: modify the threshold of rule parameters, and click re-audit. Then, refresh the page for verification.

    You can view the memory size when creating a DDH in the console as follows:

    DDH_2

ddh-socket-min-count-limit

If the physical CPU of an Alibaba Cloud DDH instance under your account is equal to the threshold you set, it is considered compliance.

Trigger type: configuration change

Resource: ACS::ECS::DedicatedHost

Request parameters:

socketCount (physical CPU cores)

Solution: when the number of sockets in the DDH instance under your account is smaller than the threshold that you set, the rule is not compliant.

  • Method 1: After a DDH is created, you cannot change its specification. Instead, you can create a DDH that meets the rules. Config detects your changes within 10 minutes and automatically starts the audit.

    To troubleshoot an invalid DDH, release the DDH. ( Only pay-as-you-go ddhs are supported. You cannot manually release a subscription DDH.

    Risk: After a DDH is released, all its resources are no longer available. All data on ECS instances on a DDH is lost and cannot be recovered.

    You can migrate ECS instances between ddhs of your account before the DDH is released.

    To migrate ECS instances between different ddhs, see Migrate ECS instances between different dedicated hosts.

  • Method 2: modify the threshold of rule parameters, and click re-audit. Then, refresh the page for verification.

    For more information about the number of sockets on a DDH, see:

    DDH_3