All Products
Search
Document Center

Application Real-Time Monitoring Service:Java Application Monitoring network configuration

Last Updated:Sep 15, 2025

The Application Real-Time Monitoring Service (ARMS) agent requires connectivity to the ARMS server to function correctly. This topic describes the ports, domain names, and IP addresses that must be accessible for Application Monitoring.

Probes of versions 3.x and later

Required destination ports

To use ARMS Application Monitoring, you must ensure that the following destination ports are accessible to the agent.

Port

Description

8080

Provided by the Application Configuration Management (ACM) service for application configuration.

8848

Provided by the ACM service for application configuration.

9990

Provided by the trace and metadata endpoint for metadata reporting.

80

Provided by the trace and metadata endpoint, metric endpoint, continuous profiling service, and probe self-monitoring service. Used to report trace, metric, continuous profiling, and probe self-monitoring data.

9092

Provided by the trace and metadata endpoint for application diagnostics.

9093

Provided by the trace and metadata endpoint for application security.

Required domain names

To use ARMS Application Monitoring, you must allow access to the ARMS endpoints and Application Configuration Management (ACM) domain names. The following table lists the ARMS endpoints and ACM domain names for each region. If your application is deployed in an Alibaba Cloud Virtual Private Cloud (VPC), including in scenarios where a leased line connects to an Alibaba Cloud VPC, use the ARMS internal endpoints and internal ACM domain names. If your application is deployed in an on-premises data center or on another cloud, use the ARMS public endpoints and public ACM domain names.

Click to view ARMS and ACM service network domain names for each region

Region

Public endpoint

Internal endpoint (VPC network)

China (Hangzhou)

  • arms-dc-hz.aliyuncs.com (Trace and metadata endpoint)

  • cn-hangzhou.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-cn-hangzhou.oss-cn-hangzhou.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-cn-hangzhou.cn-hangzhou.log.aliyuncs.com (Probe self-monitoring log reporting)

  • arms-dc-hz-internal.aliyuncs.com (Internal trace and metadata endpoint)

  • cn-hangzhou-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-cn-hangzhou.oss-cn-hangzhou-internal.aliyuncs.com (Continuous profiling service)

  • addr-hz-internal.edas.aliyun.com (ACM service)

  • end-side-logs-cn-hangzhou.cn-hangzhou-intranet.log.aliyuncs.com

China (Shanghai)

  • arms-dc-sh.aliyuncs.com (Trace and metadata endpoint)

  • cn-shanghai.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-cn-shanghai.oss-cn-shanghai.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-cn-shanghai.cn-shanghai.log.aliyuncs.com (Probe self-monitoring log reporting)

  • arms-dc-sh-internal.aliyuncs.com (Internal trace and metadata endpoint)

  • cn-shanghai-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-cn-shanghai.oss-cn-shanghai-internal.aliyuncs.com (Continuous profiling service)

  • addr-sh-internal.edas.aliyun.com (ACM service)

  • end-side-logs-cn-shanghai.cn-shanghai-intranet.log.aliyuncs.com

China (Qingdao)

  • arms-dc-qd.aliyuncs.com (Trace and metadata endpoint)

  • cn-qingdao.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-cn-qingdao.oss-cn-qingdao.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-cn-qingdao.cn-qingdao.log.aliyuncs.com (Probe self-monitoring log reporting)

  • arms-dc-qd-internal.aliyuncs.com (Internal trace and metadata endpoint)

  • cn-qingdao-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-cn-qingdao.oss-cn-qingdao-internal.aliyuncs.com (Continuous profiling service)

  • addr-qd-internal.edas.aliyun.com (ACM service)

  • end-side-logs-cn-qingdao.cn-qingdao-intranet.log.aliyuncs.com

China (Beijing)

  • arms-dc-bj.aliyuncs.com (Trace and metadata endpoint)

  • cn-beijing.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-cn-beijing.oss-cn-beijing.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-cn-beijing.cn-beijing.log.aliyuncs.com (Probe self-monitoring log reporting)

  • arms-dc-bj-internal.aliyuncs.com (Internal trace and metadata endpoint)

  • cn-beijing-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-cn-beijing.oss-cn-beijing-internal.aliyuncs.com (Continuous profiling service)

  • addr-bj-internal.edas.aliyun.com (ACM service)

  • end-side-logs-cn-beijing.cn-beijing-intranet.log.aliyuncs.com

China (Zhangjiakou)

  • arms-dc-zb.aliyuncs.com (Trace and metadata endpoint)

  • cn-zhangjiakou.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-cn-zhangjiakou.oss-cn-zhangjiakou.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-cn-zhangjiakou.cn-zhangjiakou.log.aliyuncs.com (Probe self-monitoring log reporting)

  • arms-dc-zb-internal.aliyuncs.com (Internal trace and metadata endpoint)

  • cn-zhangjiakou-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-cn-zhangjiakou.oss-cn-zhangjiakou-internal.aliyuncs.com (Continuous profiling service)

  • addr-cn-zhangjiakou-internal.edas.aliyun.com (ACM service)

  • end-side-logs-cn-zhangjiakou.cn-zhangjiakou-intranet.log.aliyuncs.com

China (Hohhot)

  • dc-cn-huhehaote.arms.aliyuncs.com (Trace and metadata endpoint)

  • cn-huhehaote.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-cn-huhehaote.oss-cn-huhehaote.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-cn-huhehaote.cn-huhehaote.log.aliyuncs.com (Probe self-monitoring log reporting)

  • dc-cn-huhehaote-internal.arms.aliyuncs.com (Internal trace and metadata endpoint)

  • cn-huhehaote-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-cn-huhehaote.oss-cn-huhehaote-internal.aliyuncs.com (Continuous profiling service)

  • end-side-logs-cn-huhehaote.cn-huhehaote-intranet.log.aliyuncs.com

China (Ulanqab)

  • dc-cn-wulanchabu.arms.aliyuncs.com (Trace and metadata endpoint)

  • cn-wulanchabu.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-cn-wulanchabu.oss-cn-wulanchabu.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-cn-wulanchabu.cn-wulanchabu.log.aliyuncs.com (Probe self-monitoring log reporting)

  • dc-cn-wulanchabu-internal.arms.aliyuncs.com (Internal trace and metadata endpoint)

  • cn-wulanchabu-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-cn-wulanchabu.oss-cn-wulanchabu-internal.aliyuncs.com (Continuous profiling service)

  • end-side-logs-cn-wulanchabu.cn-wulanchabu-intranet.log.aliyuncs.com

China (Shenzhen)

  • arms-dc-sz.aliyuncs.com (Trace and metadata endpoint)

  • cn-shenzhen.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-cn-shenzhen.oss-cn-shenzhen.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-cn-shenzhen.cn-shenzhen.log.aliyuncs.com (Probe self-monitoring log reporting)

  • arms-dc-sz-internal.aliyuncs.com (Internal trace and metadata endpoint)

  • cn-shenzhen-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-cn-shenzhen.oss-cn-shenzhen-internal.aliyuncs.com (Continuous profiling service)

  • addr-sz-internal.edas.aliyun.com (ACM service)

  • end-side-logs-cn-shenzhen.cn-shenzhen-intranet.log.aliyuncs.com

China (Heyuan)

  • dc-cn-heyuan.arms.aliyuncs.com (Trace and metadata endpoint)

  • cn-heyuan.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-cn-heyuan.oss-cn-heyuan.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-cn-heyuan.cn-heyuan.log.aliyuncs.com (Probe self-monitoring log reporting)

  • dc-cn-heyuan-internal.arms.aliyuncs.com (Internal trace and metadata endpoint)

  • cn-heyuan-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-cn-heyuan.oss-cn-heyuan-internal.aliyuncs.com (Continuous profiling service)

  • end-side-logs-cn-heyuan.cn-heyuan-intranet.log.aliyuncs.com

China (Guangzhou)

  • dc-cn-guangzhou.arms.aliyuncs.com (Trace and metadata endpoint)

  • cn-guangzhou.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-cn-guangzhou.oss-cn-guangzhou.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-cn-guangzhou.cn-guangzhou.log.aliyuncs.com (Probe self-monitoring log reporting)

  • dc-cn-guangzhou-internal.arms.aliyuncs.com (Internal trace and metadata endpoint)

  • cn-guangzhou-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-cn-guangzhou.oss-cn-guangzhou-internal.aliyuncs.com (Continuous profiling service)

  • end-side-logs-cn-guangzhou.cn-guangzhou-intranet.log.aliyuncs.com

China (Chengdu)

  • dc-cn-chengdu.arms.aliyuncs.com (Trace and metadata endpoint)

  • cn-chengdu.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-cn-chengdu.oss-cn-chengdu.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-cn-chengdu.cn-chengdu.log.aliyuncs.com (Probe self-monitoring log reporting)

  • dc-cn-chengdu-internal.arms.aliyuncs.com (Internal trace and metadata endpoint)

  • cn-chengdu-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-cn-chengdu.oss-cn-chengdu-internal.aliyuncs.com (Continuous profiling service)

  • end-side-logs-cn-chengdu.cn-chengdu-intranet.log.aliyuncs.com

China (Hong Kong)

  • arms-dc-hk.aliyuncs.com (Trace and metadata endpoint)

  • cn-hongkong.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-cn-hongkong.oss-cn-hongkong.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-cn-hongkong.cn-hongkong.log.aliyuncs.com (Probe self-monitoring log reporting)

  • arms-dc-hk-internal.aliyuncs.com (Internal trace and metadata endpoint)

  • cn-hongkong-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-cn-hongkong.oss-cn-hongkong-internal.aliyuncs.com (Continuous profiling service)

  • addr-hk-internal.edas.aliyun.com (ACM service)

  • end-side-logs-cn-hongkong.cn-hongkong-intranet.log.aliyuncs.com

Asia Pacific NE 1 (Tokyo)

  • arms-dc-jp.aliyuncs.com (Trace and metadata endpoint)

  • ap-northeast-1.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-ap-northeast-1.oss-ap-northeast-1.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-ap-northeast-1.ap-northeast-1.log.aliyuncs.com (Probe self-monitoring log reporting)

  • arms-dc-jp-internal.aliyuncs.com (Internal trace and metadata endpoint)

  • ap-northeast-1-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-ap-northeast-1.oss-ap-northeast-1-internal.aliyuncs.com (Continuous profiling service)

  • addr-ap-northeast-1-internal.edas.aliyun.com (ACM service)

  • end-side-logs-ap-northeast-1.ap-northeast-1-intranet.log.aliyuncs.com

Singapore

  • arms-dc-sg.aliyuncs.com (Trace and metadata endpoint)

  • ap-southeast-1.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-ap-southeast-1.oss-ap-southeast-1.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-ap-southeast-1.ap-southeast-1.log.aliyuncs.com (Probe self-monitoring log reporting)

  • arms-dc-sg-internal.aliyuncs.com (Internal trace and metadata endpoint)

  • ap-southeast-1-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-ap-southeast-1.oss-ap-southeast-1-internal.aliyuncs.com (Continuous profiling service)

  • addr-singapore-internal.edas.aliyun.com (ACM service)

  • end-side-logs-ap-southeast-1.ap-southeast-1-intranet.log.aliyuncs.com

Asia Pacific SE 3 (Kuala Lumpur)

  • dc-ap-southeast-3.arms.aliyuncs.com (Trace and metadata endpoint)

  • ap-southeast-3.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-ap-southeast-3.oss-ap-southeast-3.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-ap-southeast-3.ap-southeast-3.log.aliyuncs.com (Probe self-monitoring log reporting)

  • dc-ap-southeast-3-internal.arms.aliyuncs.com (Internal trace and metadata endpoint)

  • ap-southeast-3-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-ap-southeast-3.oss-ap-southeast-3-internal.aliyuncs.com (Continuous profiling service)

  • end-side-logs-ap-southeast-3.ap-southeast-3-intranet.log.aliyuncs.com

Asia Pacific SE 5 (Jakarta)

  • arms-dc-indonesia.aliyuncs.com (Trace and metadata endpoint)

  • ap-southeast-5.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-ap-southeast-5.oss-ap-southeast-5.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-ap-southeast-5.ap-southeast-5.log.aliyuncs.com (Probe self-monitoring log reporting)

  • arms-dc-indonesia-internal.aliyuncs.com (Internal trace and metadata endpoint)

  • ap-southeast-5-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-ap-southeast-5.oss-ap-southeast-5-internal.aliyuncs.com (Continuous profiling service)

  • end-side-logs-ap-southeast-5.ap-southeast-5-intranet.log.aliyuncs.com

EU Central 1 (Frankfurt)

  • arms-dc-frankfurt.aliyuncs.com (Trace and metadata endpoint)

  • eu-central-1.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-eu-central-1.oss-eu-central-1.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-eu-central-1.eu-central-1.log.aliyuncs.com (Probe self-monitoring log reporting)

  • arms-dc-frankfurt-internal.aliyuncs.com (Internal trace and metadata endpoint)

  • eu-central-1-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-eu-central-1.oss-eu-central-1-internal.aliyuncs.com (Continuous profiling service)

  • addr-eu-central-1-internal.edas.aliyun.com (ACM service)

  • end-side-logs-eu-central-1.eu-central-1-intranet.log.aliyuncs.com

UK (London)

  • dc-eu-west-1.arms.aliyuncs.com (Trace and metadata endpoint)

  • eu-west-1.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-eu-west-1.oss-eu-west-1.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-eu-west-1.eu-west-1.log.aliyuncs.com (Probe self-monitoring log reporting)

  • dc-eu-west-1-internal.arms.aliyuncs.com (Internal trace and metadata endpoint)

  • eu-west-1-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-eu-west-1.oss-eu-west-1-internal.aliyuncs.com (Continuous profiling service)

  • addr-eu-west-1-internal.edas.aliyun.com (ACM service)

  • end-side-logs-eu-west-1.eu-west-1-intranet.log.aliyuncs.com

US East 1 (Virginia)

  • dc-us-east-1.arms.aliyuncs.com (Trace and metadata endpoint)

  • us-east-1.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-us-east-1.oss-us-east-1.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-us-east-1.us-east-1.log.aliyuncs.com (Probe self-monitoring log reporting)

  • dc-us-east-1-internal.arms.aliyuncs.com (Internal trace and metadata endpoint)

  • us-east-1-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-us-east-1.oss-us-east-1-internal.aliyuncs.com (Continuous profiling service)

  • addr-us-east-1-internal.edas.aliyun.com (ACM service)

  • end-side-logs-us-east-1.us-east-1-intranet.log.aliyuncs.com

US West 1 (Silicon Valley)

  • arms-dc-usw.aliyuncs.com (Trace and metadata endpoint)

  • us-west-1.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-us-west-1.oss-us-west-1.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-us-west-1.us-west-1.log.aliyuncs.com (Probe self-monitoring log reporting)

  • dc-us-west-1-internal.arms.aliyuncs.com (Internal trace and metadata endpoint)

  • us-west-1-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-us-west-1.oss-us-west-1-internal.aliyuncs.com (Continuous profiling service)

  • arms-dc-usw.aliyuncs.com (ACM service)

  • end-side-logs-us-west-1.us-west-1-intranet.log.aliyuncs.com

SAU (Riyadh - Partner Region)

  • dc-me-central-1.arms.aliyuncs.com (Trace and metadata endpoint)

  • me-central-1.arms.aliyuncs.com (Metric endpoint)

  • arms-profiling-me-central-1.oss-me-central-1.aliyuncs.com (Continuous profiling service)

  • acm.aliyun.com (ACM service)

  • end-side-logs-me-central-1.me-central-1.log.aliyuncs.com (Probe self-monitoring log reporting)

  • dc-me-central-1-internal.arms.aliyuncs.com (Internal trace and metadata endpoint)

  • me-central-1-intranet.arms.aliyuncs.com (Internal metric endpoint)

  • arms-profiling-me-central-1.oss-me-central-1-internal.aliyuncs.com (Continuous profiling service)

  • arms-dc-me-central-1.aliyuncs.com (ACM service)

  • end-side-logs-me-central-1.me-central-1-intranet.log.aliyuncs.com

You can use the Curl command to test the network connectivity between the destination host and the ARMS endpoint and ACM service. For example, to test the connectivity in the China (Hangzhou) region, log on to the machine where your application is deployed and run the following commands:

# Test the trace and metadata endpoint. A return code of 200 indicates a successful connection.
curl -I -w "%{http_code}" http://arms-dc-hz.aliyuncs.com/api/checkHealth
# Test the metadata endpoint. A return code of 200 indicates a successful connection.
curl -I -w "%{http_code}" http://arms-dc-hz.aliyuncs.com:9990/api/checkHealth

# Test the metric endpoint. A return code of 200 indicates a successful connection.
curl -I -w "%{http_code}" http://cn-hangzhou.arms.aliyuncs.com/health/readiness
Note
  • Some regions do not provide an internal ACM service. In these regions, you must use the public ACM domain name, which requires your application to have Internet access.

  • By default, the ARMS agent automatically detects the network status and prioritizes internal endpoints for data reporting. If the internal network is unavailable, the agent uses public endpoints to report data.

Required IP address ranges

If your application is deployed in an Alibaba Cloud VPC, including in scenarios where a leased line connects to an Alibaba Cloud VPC, you must ensure connectivity to the internal domain names and allow access to the internal CIDR blocks for each service. If your application is deployed in an on-premises data center or on another cloud, ARMS does not provide the CIDR block details for public endpoints. In this case, you must ensure connectivity to the public domain names.

Required ACM DPI engine IP addresses

The ARMS agent needs to connect to the ACM DPI engine to obtain configuration information. The IP addresses of the ACM DPI engine are static and can be retrieved by accessing the HTTP interface that is provided by ACM. To retrieve the IP addresses, query them based on the ACM domain name of the corresponding region.

curl 'acm.aliyun.com:8080/diamond-server/diamond'

You must configure your firewall to allow the ACM DPI engine IP addresses that are returned by the curl command. You can run the following command to verify the connectivity.

curl -X GET "http://139.196.XX.XX:8080/diamond-server/config.co?dataId=com.ali.art.logicregion.flow.control.icbu&group=art-control-service" -i

If no content is returned, the access failed.

Probe version 2.x

Required destination ports

To use ARMS Application Monitoring, you must ensure that the following destination ports are accessible to the agent.

Port

Description

8080

Provided by the ACM service for application configuration.

8442

Provided by the ARMS endpoint for metadata reporting.

8443

Provided by the ARMS endpoint for statistics reporting.

8883

Provided by the ARMS endpoint for detailed data reporting.

8848

Provided by the ARMS endpoint for microservice-related data reporting.

9092

Provided by the ARMS endpoint for application diagnostics.

9093

Provided by the ARMS endpoint for application security.

Required domain names

To use ARMS Application Monitoring, you must allow access to the ARMS endpoints and ACM domain names. The following table lists the ARMS endpoints and ACM domain names for each region. If your application is deployed in an Alibaba Cloud VPC, including in scenarios where a leased line connects to an Alibaba Cloud VPC, use the ARMS internal endpoints and internal ACM domain names. If your application is deployed in an on-premises data center or on another cloud, use the ARMS public endpoints and public ACM domain names.

Click to view ARMS and ACM network domain names for each region

Region

Public endpoint

Internal endpoint (VPC network)

China (Hangzhou)

  • arms-dc-hz.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

  • arms-dc-hz-internal.aliyuncs.com (ARMS)

  • addr-hz-internal.edas.aliyun.com (ACM)

China (Shanghai)

  • arms-dc-sh.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

  • arms-dc-sh-internal.aliyuncs.com (ARMS)

  • addr-sh-internal.edas.aliyun.com (ACM)

China (Qingdao)

  • arms-dc-qd.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

  • arms-dc-qd-internal.aliyuncs.com (ARMS)

  • addr-qd-internal.edas.aliyun.com (ACM)

China (Beijing)

  • arms-dc-bj.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

  • arms-dc-bj-internal.aliyuncs.com (ARMS)

  • addr-bj-internal.edas.aliyun.com (ACM)

China (Zhangjiakou)

  • arms-dc-zb.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

  • arms-dc-zb-internal.aliyuncs.com (ARMS)

  • addr-cn-zhangjiakou-internal.edas.aliyun.com (ACM)

China (Hohhot)

  • dc-cn-huhehaote.arms.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

dc-cn-huhehaote-internal.arms.aliyuncs.com (ARMS)

China (Ulanqab)

  • dc-cn-wulanchabu.arms.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

dc-cn-wulanchabu-internal.arms.aliyuncs.com (ARMS)

China (Shenzhen)

  • arms-dc-sz.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

  • arms-dc-sz-internal.aliyuncs.com (ARMS)

  • addr-sz-internal.edas.aliyun.com (ACM)

China (Heyuan)

  • dc-cn-heyuan.arms.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

dc-cn-heyuan-internal.arms.aliyuncs.com (ARMS)

China (Guangzhou)

  • dc-cn-guangzhou.arms.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

dc-cn-guangzhou-internal.arms.aliyuncs.com (ARMS)

China (Chengdu)

  • dc-cn-chengdu.arms.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

dc-cn-chengdu-internal.arms.aliyuncs.com (ARMS)

China (Hong Kong)

  • arms-dc-hk.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

  • arms-dc-hk-internal.aliyuncs.com (ARMS)

  • addr-hk-internal.edas.aliyun.com (ACM)

Asia Pacific NE 1 (Tokyo)

  • arms-dc-jp.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

  • arms-dc-jp-internal.aliyuncs.com (ARMS)

  • addr-ap-northeast-1-internal.edas.aliyun.com (ACM)

Singapore

  • arms-dc-sg.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

  • arms-dc-sg-internal.aliyuncs.com (ARMS)

  • addr-singapore-internal.edas.aliyun.com (ACM)

Asia Pacific SE 3 (Kuala Lumpur)

  • dc-ap-southeast-3.arms.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

dc-ap-southeast-3-internal.arms.aliyuncs.com (ARMS)

Asia Pacific SE 5 (Jakarta)

  • arms-dc-indonesia.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

arms-dc-indonesia-internal.aliyuncs.com (ARMS)

EU Central 1 (Frankfurt)

  • arms-dc-frankfurt.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

  • arms-dc-frankfurt-internal.aliyuncs.com (ARMS)

  • addr-eu-central-1-internal.edas.aliyun.com (ACM)

UK (London)

  • dc-eu-west-1.arms.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

  • dc-eu-west-1-internal.arms.aliyuncs.com (ARMS)

  • addr-eu-west-1-internal.edas.aliyun.com (ACM)

US East 1 (Virginia)

  • dc-us-east-1.arms.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

  • dc-us-east-1-internal.arms.aliyuncs.com (ARMS)

  • addr-us-east-1-internal.edas.aliyun.com (ACM)

US West 1 (Silicon Valley)

  • arms-dc-usw.aliyuncs.com (ARMS)

  • acm.aliyun.com (ACM)

  • dc-us-west-1-internal.arms.aliyuncs.com (ARMS)

  • arms-dc-usw.aliyuncs.com (ACM)

You can use the Telnet command to test the network connectivity between the destination host and the ARMS endpoint and ACM service. For example, to test the connectivity in the China (Hangzhou) region, log on to the machine where your application is deployed and run the following commands:

telnet arms-dc-hz-internal.aliyuncs.com 8442
telnet arms-dc-hz-internal.aliyuncs.com 8443
telnet arms-dc-hz-internal.aliyuncs.com 8883
telnet arms-dc-hz-internal.aliyuncs.com 9092
telnet arms-dc-hz-internal.aliyuncs.com 9093
telnet addr-hz-internal.edas.aliyun.com 8080
Note

Some regions do not provide an internal ACM service. In these regions, you must use the public ACM domain name, which requires your application to have Internet access.

Required IP address ranges

If your application is deployed in an Alibaba Cloud VPC, including in scenarios where a leased line connects to an Alibaba Cloud VPC, you must ensure connectivity to the internal domain names and allow access to the internal CIDR blocks for each service. If your application is deployed in an on-premises data center or on another cloud, ARMS does not provide the CIDR block details for public endpoints. In this case, you must ensure connectivity to the public domain names.

Required ACM DPI engine IP addresses

The ARMS agent needs to connect to the ACM DPI engine to obtain configuration information. The IP addresses of the ACM DPI engine are static and can be retrieved by accessing the HTTP interface that is provided by ACM. To retrieve the IP addresses, query them based on the ACM domain name of the corresponding region.

curl 'acm.aliyun.com:8080/diamond-server/diamond'

You must configure your firewall to allow the ACM DPI engine IP addresses that are returned by the curl command. You can run the following command to verify the connectivity.

curl -X GET "http://139.196.XX.XX:8080/diamond-server/config.co?dataId=com.ali.art.logicregion.flow.control.icbu&group=art-control-service" -i

If no content is returned, the access failed.

References

For more information about networking issues, see Networking.