What deployment settings are available?

The following deployment settings are available:

Selects a cloud platform where your Elasticsearch clusters, Kibana instance, and other Elastic Stack components will be hosted. Elasticsearch Add-On for Heroku currently supports Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure.

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.

Elastic Stack uses a versions code that is constructed of three numbers separated by dots: the leftmost number is the number of the major release, the middle number is the number of the minor release and the rightmost number is the number of the maintenance release (e.g., 8.3.2 means major release 8, minor release 3 and maintenance release 2).

You might sometimes notice additional versions listed in the user interface beyond the versions we currently support and maintain, such as release candidate builds and older versions. If a version is listed in the Elasticsearch Add-On for Heroku console, it can be deployed.

To learn about how we support Elasticsearch versions in Elasticsearch Add-On for Heroku, check 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, check Version Upgrades.

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.

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