Technical FAQedit

This frequently-asked-questions list answers some of your more common questions about configuring Elasticsearch Service.

  • Can I implement a Hot-Warm architecture?
  • Can I run tribe nodes or cross-cluster search?
  • What about dedicated master nodes?
  • Can I use a Custom SSL certificate?
  • Do you support VPC peering to Elasticsearch Service?
  • Can Elasticsearch Service autoscale?
  • Do you support IP sniffing?
  • Does Elasticsearch Service support encryption at rest?
  • Can I find the static IP addresses for my endpoints on Elasticsearch Service?

    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 hot-warm architectures in all of the solutions provided by allowing you to add warm nodes to any of your deployments.
    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.
    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 Privatelink, Azure Private Link, and Google Private Service Connect. 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?
    Elasticsearch Service now supports autoscaling. To learn how to enable it through the console or the API, see Deployment autoscaling.
    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.
    We have requirements around restricting access by adding firewall rules to only allow access to certain IP addresses from our Infosec team. Do you provide static IP addresses for the endpoints on Elasticsearch Service?
    The IP addresses used for deployment endpoint access are not static because they map to the Network Load Balancers (NLBs) hosted by us in each region. IP addresses assigned to cloud resources can change without notice. This could be initiated by cloud providers with no knowledge to us. For this reason, we do not recommend that you use firewall rules to allow or restrict certain IP ranges. If you do wish to secure communication for deployment endpoints on Elasticsearch Service, please use Private Link. You can add firewall rules to allow the domains for your cluster and other deployment endpoints (for example Kibana and APM). The domains map to IP addresses, but this approach might also have risks depending on how recent the lookup is and on the Time To Live (TTL) for the DNS lookup.