Alibaba Cloud Elasticsearch adjusted its network architecture in October 2020. Instances created before this date use the old network architecture, and instances created on or after this date use the new network architecture.
Changes and timeline
Changes
-
In the new network architecture, Alibaba Cloud ES instances are deployed in a virtual private cloud (VPC) that belongs to an Alibaba Cloud service account and cannot access resources in other network environments.
-
In the old network architecture, Alibaba Cloud ES instances are deployed in your VPC, and their network access is not restricted.
Timeline
The network architecture adjustment took effect in October 2020.
-
Except for the China (Zhangjiakou) region and regions outside China, ES instances created before October 2020 use the old network architecture.
-
Except for the China (Zhangjiakou) region and regions outside China, ES instances created in or after October 2020 use the new network architecture.
-
The timeline for the network architecture adjustment in the China (Zhangjiakou) region and regions outside China is not yet determined.
To check for network connectivity, contact Alibaba Cloud Elasticsearch technical support by .
Impact of adjustment
-
Instances on the new network architecture cannot communicate with instances on the old architecture. This affects cross-cluster reindexing, cross-cluster search, and cross-cluster replication (CCR).
-
New network architecture
-
You can configure private connections for Elasticsearch clusters. This feature uses PrivateLink to connect the Elasticsearch service VPC to your VPC and resolve network connectivity issues. For more information, see Configure a private connection for an instance.
-
In the new network architecture, features such as X-Pack Watcher, reindex, Lightweight Directory Access Protocol (LDAP) authentication, and Active Directory (AD) authentication are restricted. You must use PrivateLink to access these features. For more information, see the following topics:
-
X-Pack Watcher in Alibaba Cloud Elasticsearch cannot communicate directly with the Internet and must use the private endpoint of the instance within a VPC. To enable Internet access, complete the following steps:
-
Configure a PrivateLink connection for the instance. For more information, see Configure a PrivateLink connection for an instance.
-
Associate an Elastic IP Address (EIP) with an Elastic Compute Service (ECS) instance or configure Source Network Address Translation (SNAT). For more information, see Associate an EIP or Configure SNAT.
-
-
-
Old network architecture
-
The PrivateLink feature is not supported.
-
LDAP and AD authentication are supported only in single-zone deployments, not in multi-zone deployments.
-