On our AWS and GCP cloud-native platform, we offer a number of different Elasticsearch plan sizes. Though all plans are not listed on this page, below we outline the construction of plans. You can find the latest plans and pricing in Mission Control.
Elasticsearch Plans and Configuration¶
In general, you have two main choices when sizing an Elasticsearch cluster on our service:
- How much storage you want: The primary number we tell you is how much raw storage we provide in the Elasticsearch cluster. Since replication is configurable by the user, we don’t account for replication in this number. It is the total storage available to you before any replication.
- Performance and usage profile: On our platform, we offer a selection called “flavor” that determines the performance characteristics of the nodes in your cluster. The main difference at this time is the amount of memory and CPU offered per GB of storage. However, in the future, we may use flavor to specify other criteria, like storage type.
The Standard Flavor offers a good all-a-around cluster for search, metrics, and logging. The standard flavor includes 16GB of storage per 1GB of RAM.
All sizes in the table below only refer to resources used in the Elasticsearch cluster. Other services, like Kibana and Cerebro have their own dedicated resources.
|Plan Size (GB)||Number of Nodes||Storage per Node||RAM per Node|
What happens when I run out of storage space in my existing Elasticsearch cluster?¶
Our support team monitors the health of your cluster and will take action to ensure the cluster does not fill up. The most common action is to add a data node at the current plan size.
There are, however, scenarios where performing a plan resize (changing the plan size of all data nodes) is a better solution. In those cases, our support team will contact you via a ticket and present the options. If you approve the plan resize, we will perform it for you, without downtime, and right-size the number of resulting data nodes to the data in your cluster.