The following table describes the endpoints of the OpenSearch API in different regions.
Region | Endpoint |
China (Qingdao) | Public endpoint: http://opensearch-cn-qingdao.aliyuncs.com Internal endpoint: http://intranet.opensearch-cn-qingdao.aliyuncs.com |
China (Beijing) | Public endpoint: http://opensearch-cn-beijing.aliyuncs.com Internal endpoint: http://intranet.opensearch-cn-beijing.aliyuncs.com |
China (Hangzhou) | Public endpoint: http://opensearch-cn-hangzhou.aliyuncs.com Internal endpoint: http://intranet.opensearch-cn-hangzhou.aliyuncs.com |
China (Shanghai) | Public endpoint: http://opensearch-cn-shanghai.aliyuncs.com Internal endpoint: http://intranet.opensearch-cn-shanghai.aliyuncs.com |
China (Shenzhen) | Public endpoint: http://opensearch-cn-shenzhen.aliyuncs.com Internal endpoint: http://intranet.opensearch-cn-shenzhen.aliyuncs.com |
Singapore | Public endpoint: http://opensearch-ap-southeast-1.aliyuncs.com Internal endpoint: http://intranet.opensearch-ap-southeast-1.aliyuncs.com |
China (Zhangjiakou) | Public endpoint: http://opensearch-cn-zhangjiakou.aliyuncs.com Internal endpoint: http://intranet.opensearch-cn-zhangjiakou.aliyuncs.com |
Germany (Frankfurt) | Public endpoint: http://opensearch-eu-central-1.aliyuncs.com Internal endpoint: http://intranet.opensearch-eu-central-1.aliyuncs.com |
Public endpoints are used to connect to OpenSearch over the Internet. Internal endpoints are used to connect to OpenSearch in an internal network, such as a virtual private cloud (VPC).