What deployment settings are available?edit

The following deployment settings are available:

Cloud provideredit

Selects a cloud platform where your Elasticsearch clusters and Kibana instances will be hosted. Elasticsearch Service currently supports Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure.

Regionedit

Regions represent data centers in a geographic location, where your deployment will be located. When choosing a region, the general rule is to choose one as close to your application servers as possible in order to minimize network delays.

You can select your cloud platform and region only when you create a new deployment, so pick ones that works for you. They cannot be changed later. Different deployments can use different platforms and regions.

Versionedit

Elasticsearch versions are denoted as X.Y.Z, where X is the major version, Y is the minor version, and Z is the patch level or maintenance release. The default version is the latest, stable version. At any given time, the two latest minor versions are guaranteed to be available for deployments of new clusters, such as Elasticsearch 5.5.1 and 5.4.3. Only the latest patch level within a minor version is usually available for new deployments, such as 2.4.5.

All versions listed in the user interface can be deployed, including release candidate builds.

To deliver new features and keep complexity manageable, we need to discontinue old versions. When a version nears its end-of-life point, you are given six months notice to upgrade to one of the available minor versions.

To learn more about how we support Elasticsearch versions in Elasticsearch Service, see Version Policy.

You can always upgrade Elasticsearch versions, but you cannot downgrade. To learn more about upgrading versions of Elasticsearch and best practices for major version upgrades, see Version Upgrades.

Snapshot sourceedit

To create a deployment from a snapshot, select the snapshot source. You need to configure snapshots and establish a snapshot lifecycle management policy and repository before you can restore from a snapshot. The snapshot options depend on the stack version the deployment is running.

Nameedit

This setting allows you to assign a more human-friendly name to your cluster which will be used for future reference in the Elasticsearch Service Console. Common choices are dev, prod, test, or something more domain specific.