All Products
Search
Document Center

Cloud Monitor:CloudMonitor agent fails to be automatically installed on an ECS instance

Last Updated:Feb 28, 2026

If the CloudMonitor agent fails to be automatically installed on an Elastic Compute Service (ECS) instance, follow these steps to identify and resolve the issue.

Prerequisites

Before you begin, ensure that you have:

  • Access to the affected ECS instance (SSH, VNC, or other method)

  • Administrator account credentials (the root user on Linux or the Administrator user on Windows)

Important

You can manage the Cloud Monitor agent only by using the root user account (an administrator account). However, using an administrator account may introduce certain risks, such as system stability or data security issues. Proceed with caution.

Step 1: Log on to the ECS instance

Log on to the ECS instance as the root user.

Step 2: Check whether the region ID is available

Run the following command to get the region ID from the metadata service:

curl http://100.100.100.200/latest/meta-data/region-id
  • Region ID returned (for example, cn-hangzhou): The metadata service is working. Go to Step 3.

  • No output or error: The instance cannot reach the metadata service. Automatic installation is not supported. Manually install the CloudMonitor agent instead.

Step 3: Check OSS network connectivity

The CloudMonitor agent installation package is hosted on Object Storage Service (OSS). Run the following command to test connectivity to the OSS endpoint:

ping cms-agent-${region-id}.oss-${region-id}.aliyuncs.com

Replace ${region-id} with the value returned in Step 2. For example, if the region ID is cn-hangzhou:

ping cms-agent-cn-hangzhou.oss-cn-hangzhou.aliyuncs.com
  • Ping succeeds: The network is normal. The issue may be caused by CloudMonitor. Submit a ticket to CloudMonitor technical support.

  • Ping fails or times out: The network is abnormal. The issue may be caused by OSS. Submit a ticket to OSS technical support.

Troubleshooting decision summary

StepCheckResultAction
1Log on as root--Required before running diagnostic commands
2Get region ID from metadata serviceSuccessGo to Step 3
2Get region ID from metadata serviceFailureManually install the agent
3Ping the OSS endpointSuccessSubmit a ticket to CloudMonitor support
3Ping the OSS endpointFailureSubmit a ticket to OSS support

See also