Elasticsearch Service FAQ

Openness and transparency are important to us, so we put together this frequently asked questions list to answer some of your more common questions about specific features in Elasticsearch Service.

Getting started FAQ

Billing FAQ

Technical FAQ

Getting started

What is Elasticsearch Service?
Elasticsearch Service is hosted and managed Elasticsearch and Kibana brought to you by the creators of Elasticsearch. Elasticsearch Service is part of Elastic Cloud and ships with features that you can only get from the company behind Elasticsearch, Kibana, Beats, and Logstash. Elasticsearch is a full text search engine that suits a range of uses, from search on websites to big data analytics and more.
Is Elasticsearch Service the same as Amazon’s Elasticsearch Service?
Elasticsearch Service is not the same as the Amazon Elasticsearch service. To learn more about the differences, see our AWS Elasticsearch Service comparison.
Can I run the full Elastic Stack in Elasticsearch Service?
Many of the products that are part of the Elastic Stack are readily available in Elasticsearch Service, including Elasticsearch, Kibana, X-Pack features such as monitoring and security, and others, including plugins. Other Elastic Stack products you can use directly with Elasticsearch Service, even if they don’t currently run there. For example, both Logstash and Beats can send their data to Elasticsearch Service, just as you would send data to any other Elasticsearch cluster. What you can run is also determined by your subscription level.
Can I try Elasticsearch Service for free?

Yes, you can sign up for a 14-day trial. The trial starts the moment you create a cluster.

During the free trial period, you get access to a free deployment with the latest Elasticsearch and Kibana versions, security features, machine learning, and much more.

What if I need to change the size of my Elasticsearch cluster at a later time?
You can scale your clusters both up and down from the user console, whenever you like. The resizing of the cluster is transparently done in the background, without any downtime. Beware, however, that if you scale your cluster down, you must ensure that the downsized cluster can handle your Elasticsearch memory requirements. Read more about sizing and memory in our articles Sizing Elasticsearch and Elasticsearch in Production.
Do you offer support?
Yes, all subscription levels for Elasticsearch Service include support, handled by email or through the Elastic Support Portal. Different subscription levels include different levels of support. For the Standard subscription level, there is no service-level agreement (SLA) on support response times. Gold and Platinum subscription levels include an SLA on response times to tickets and dedicated resources. To learn more, see Getting Help.
Where is Elasticsearch Service hosted?
We host our Elasticsearch clusters on Amazon Web Services (AWS), Google Cloud Platform (GCP) and Microsoft Azure. Check out which regions we support and what hardware we use. New data centers get added all the time.
What is the difference between Elasticsearch Service and the Amazon Elasticsearch Service?

Elasticsearch Service is the only hosted and managed Elasticsearch service built, managed, and supported by the company behind Elasticsearch, Kibana, Beats, and Logstash. With Elasticsearch Service, you always get the latest versions of the software. Our service is built on best practices and years of experience hosting and managing thousands of Elasticsearch clusters in the cloud and on premise. More infromation is available in the following Amazon and Elastic Elasticsearch Service comparison page.

Please note that there is no formal partnership between Elastic and Amazon Web Services (AWS), and Elastic does not provide any support on the AWS Elasticsearch Service.

Can I use Elasticsearch Service on platforms other than AWS?
Yes, you can create Elasticsearch Service deployments on the Google Cloud Platform and Microsoft Azure.
Do you offer Elastic’s commercial products?

Yes, all Elasticsearch Service customers get access to basic authentication and role-based access control, in addition to monitoring capability.

Elasticsearch Service Gold and Platinum customers get complete access to all the capabilities in X-Pack:

  • Security
  • Alerting
  • Monitoring
  • Reporting
  • Graph Analysis & Visualization

Contact us to learn more.

As a gesture to startups and small businesses using Elasticsearch Service, you are also entitled to use some X-Pack features that are part of the Gold and Platinum subscription levels, as long as your clusters are using less than a combined 64GB of memory in total. This means that you get to enjoy access to field- and document-level security features and to graph capabilities.

Is my Elasticsearch cluster protected by X-Pack?
Yes, X-Pack security features give you the full power to protect your Elasticsearch Service deployment with basic authentication and role-based access control.
Is there a limit on the number of documents or indexes I can have in my cluster?

No. We do not enforce any artificial limit on the number of indexes or documents you can store in your cluster.

That said, there is a limit to how many indexes Elasticsearch can cope with. Every shard of every index is a separate Lucene index, which in turn comprises several files. A process cannot have an unlimited number of open files. Also, every shard has its associated control structures in memory. So, while we will let you make as many indexes as you want, there are limiting factors. Our larger plans provide your processes with more dedicated memory and CPU-shares, so they are capable of handling more indexes. The number of indexes or documents you can fit in a given plan therefore depends on their structure and use.


Is there a way for me to estimate how much Elasticsearch Service will cost?
Yes, there is: Try our Elasticsearch Service Pricing Calculator.
Why is my card charged?

The charge is a recurring fee for using our hosted Elasticsearch service. The fee is normally charged at the start of each month, but it can also be charged at other times during the month. If a charge is unsuccessful, we will try to charge your card again at a later date.

To locate the charge, please look for ELASTIC charge.elastic.co on the credit card statement from your card issuer.

If you still do not recognize the charge on your the credit card statement, the service is probably purchased by someone else in your company. A good guess would be someone from the development or operations team. Please ask someone there and see if they know about Elasticsearch Service or Found, as the service was previously named.

How do I view previous receipts and billing history?
See the billing history, where you can view and download receipts for all previous charges. If you do not have the login details, ask the person or department in your company who is responsible for handling the Elasticsearch Service billing details.
How can I change who receives receipts and billing notifications?
The account owner can change who receives receipts and billing notifications by changing the email details.
Can I get a refund?
Charges are non-refundable, but once you delete a deployment, we’ll stop charging you for that deployment immediately. You only pay for what you use and you can stop using the service at any time.
What are the available payment methods on Elasticsearch Service?
For month-to-month payments only credit cards are accepted. We also do allow payments by bank transfer for annual subscriptions. Please contact ar@elastic.co for more details.
Who can I contact for more information?
If you have any further questions about your credit card statement, billing, or receipts, please send an email to ar@elastic.co.
Why is the expiry date of my License API not same as my subscription end date?
The expiry date that you see is only informational and for Elastic internal usage. Elasticsearch Service manages the cluster licenses so that you don’t have to take care of it.


Can I implement a hot-warm architecture?
hot-warm architecture refers to an Elasticsearch setup for larger time-data analytics use cases with two different types of nodes, hot and warm. Elasticsearch Service supports creating your own hot-warm architecture through a ready-made deployment template that you can configure for your own use case.
Can I run tribe nodes or cross-cluster search?
Tribe nodes act as federated clients across multiple clusters, meaning they can issue read and write operations against the nodes in all clusters. Cross-cluster search allows any node to act as a federated client across multiple clusters, without joining those clusters as a node. Elasticsearch Service supports cross-cluster search, which is our newer feature and preferred over tribe nodes.
What about dedicated master nodes?
Master nodes are responsible for cluster-wide actions, such as creating or deleting an index, tracking which nodes are part of the cluster, and deciding which shards to allocate to which nodes. Elasticsearch Service supports dedicated master nodes through our deployment templates.
Can I use a Custom SSL certificate?
We don’t support custom SSL certificates, which means that a custom CNAME for an Elasticsearch Service endpoint such as mycluster.mycompanyname.com also is not supported.
Do you support VPC peering to Elasticsearch Service?
VPC peering is a type of connection between virtual private networks that is used to route network traffic. We support secure peering using AWS Private Link. To run Elasticsearch Service in a dedicated VPC with a secure connection from your environment, use the Elasticsearch Service Private subscription. For more information, see Set up Elasticsearch Service Private.
Can Elasticsearch Service autoscale?

We don’t support autoscaling, but it is extremely easy for you to scale your Elasticsearch cluster via the Elasticsearch Service Console without interrupting the availability of your cluster. It’s as easy as moving a slider and saving your changes.

True autoscaling would require a fairly close analysis of the load on your cluster and would have to be performed preemptively, before your cluster is loaded up, so as to allow time for the new nodes to be operational before they can help reduce load or request times. Clusters scaling up automatically could also negatively affect your billing. We don’t want you to receive an unexpectedly large bill for a cluster that got scaled up automatically without your consent.

Do you support IP sniffing?
IP sniffing is not supported by design and will not return the expected results. We prevent IP sniffing from returning the expected results to improve the security of our underlying Elasticsearch Service infrastructure.
Does Elasticsearch Service support encryption at rest?
Yes, encryption at rest (EAR) is enabled in Elasticsearch Service by default. We support EAR for both the data stored in your clusters and the snapshots we take for backup, on all cloud platforms and across all regions.