Elasticsearch Service regionsedit

A region is the geographic area where the data center of the cloud provider that hosts your deployment is located. Use the information listed here to decide which Elasticsearch Service region to use. Your choice should be based on:

  • Your geographic proximity to the region. Picking a region that is closer to you typically reduces latency for indexing and search requests.
  • The features that we support for the region. Not all regions support the same set of features.

Elasticsearch Service handles all hosting details for you, no additional accounts with the underlying cloud provider required. The region you select cannot be changed after you create a deployment. If you want to use a different region later on, you can create a new deployment and reindex your data into it.

For details about the available regions, including the deployment templates and instance configuratons available for each, see the list of available regions.

If you are not sure what to pick, choose a region that is geographically close to you to reduce latency. You should always use HTTPS to connect to the Elastic stack components of your deployment.

Amazon Web Services (AWS) regionsedit

The following AWS regions are available:

Region Name Supports

ap-northeast-1

Asia Pacific (Tokyo)

HTTPS, HTTP

ap-northeast-2

Asia Pacific (Seoul)

HTTPS, HTTP

ap-south-1

Asia Pacific (Mumbai)

HTTPS only

ap-southeast-1

Asia Pacific (Singapore)

HTTPS, HTTP

ap-southeast-2

Asia Pacific (Sydney)

HTTPS, HTTP

eu-central-1

EU (Frankfurt)

HTTPS only

eu-west-1

EU (Ireland)

HTTPS, HTTP

eu-west-2

EU (London)

HTTPS only

eu-west-3

EU (Paris)

HTTPS only

sa-east-1

South America (São Paulo)

HTTPS, HTTP

us-east-1

US East (N. Virginia)

HTTPS, HTTP

us-east-2

US East (Ohio)

HTTPS only

us-west-1

US West (N. California)

HTTPS, HTTP

us-west-2

US West (Oregon)

HTTPS, HTTP

ca-central-1

Canada (central)

HTTPS only

Google Cloud Platform (GCP) regionsedit

The following GCP regions are available:

Region Name Supports

gcp-asia-east1

Asia Pacific East 1 (Taiwan)

HTTPS only

gcp-asia-northeast1

Asia Pacific Northeast 1 (Tokyo)

HTTPS only

gcp-asia-south1

Asia Pacific South 1 (Mumbai)

HTTPS only

gcp-asia-southeast1

Asia Pacific Southeast 1 (Singapore)

HTTPS only

gcp-australia-southeast1

Asia Pacific Southeast 1 (Sydney)

HTTPS only

gcp-europe-north1

Europe North 1 (Finland)

HTTPS only

gcp-europe-west1

Europe West 1 (Belgium)

HTTPS only

gcp-europe-west2

Europe West 2 (London)

HTTPS only

gcp-europe-west3

Europe West 3 (Frankfurt)

HTTPS only

gcp-europe-west4

Europe West 4 (Netherlands)

HTTPS only

gcp-northamerica-northeast1

North America Northeast 1 (Montreal)

HTTPS only

gcp-southamerica-east1

South America East 1 (Sao Paulo)

HTTPS only

gcp-us-central1

US Central 1 (Iowa)

HTTPS only

gcp-us-east1

US East 1 (South Carolina)

HTTPS only

gcp-us-east4

US East 4 (N. Virginia)

HTTPS only

gcp-us-west1

US West 1 (Oregon)

HTTPS only

Azure regionsedit

The following Azure regions are available:

Region Name Supports

australiaeast

Australia East (New South Wales)

HTTPS only

centralus

US Central (Iowa)

HTTPS only

eastus2

East US 2 (Virginia)

HTTPS only

francecentral

France Central (Paris)

HTTPS only

japaneast

Japan East (Tokyo)

HTTPS only

northeurope

North Europe (Ireland)

HTTPS only

southeastasia

Southeast Asia (Singapore)

HTTPS only

uksouth

UK South (London)

HTTPS only

westeurope

West Europe (Netherlands)

HTTPS only

westus2

West US 2 (Washington)

HTTPS only