Been thinking that you spend too much of your time and effort running your homegrown Elasticsearch environment? If you’re like we were back in the day, there are times when you need some relief from the headaches that come along with the housekeeping and instability issues that you need to tackle.
Or you may be thinking that you’re quite happy with running Elasticsearch on your own. Well, we can certainly appreciate and admire such confidence. We’re willing to bet, however, that we can make you better. Read this short article to see if you don’t agree on at least a few of the points we make here.
You’ll enjoy many benefits when you offload hosting your Elasticsearch environment onto a third-party service, and we explain the top 6 benefits here in this article.
1. Easy management of your clusters
To learn about our simple, 6-step process for provisioning an Elasticsearch cluster, we invite you to read one of our blog articles, Easy How-to: Provisioning an Elasticsearch Cluster on Qbox. Qbox is available in 29 data centers that we maintain around the world. With a few clicks, you can secure your cluster and choose from a large array of plugins.
2. Smarter rebuilds with the Qbox dashboard
With a few clicks on the Qbox dashboard, it’s easy to vertically resize by migrating to bigger VMs that have more resources. This offers more flexibility beyond horizontal scaling—adding nodes to an existing cluster. Typically, it isn’t feasible to simply resize a typical cloud server: you’ve got to replace it. In comparison with other alternatives, Qbox gives you the speed and flexibility to perform quick migrations to a larger cluster. To learn more about resizing and to see how easy it is in a Qbox environment, we invite you to read through Thoughts on Launching and Scaling Elasticsearch.
3. Minimum downtime with built-in failover and automatic node recovery
Qbox gives you full reliability with built-in failover on multi-node clusters, and this translates into maximum uptime during cluster changes. You can expect considerably less downtime during migrations in our environment—typically 15 seconds at most. Also, users will experience even less downtime when removing nodes. Our users experience negligible downtime during these operations. Scaling down is difficult, but we make it way better. For most detrimental system causes and maintenance events, users can expect staggered, automatic node recovery. For other scenarios, easy restore tools are available for fast recovery. We show you how to do it in How-to: Quick-and-Easy Resizing of your Elasticsearch Cluster.
4. Monitors and alerts
We’ve got your back with devops-level support and diagnostics 24/7 365. Our system continuously monitors all clusters for potential problems, creates a trouble event when necessary, and then notifies users of issues. You can read more about how it works in our article Automatic Cluster Alerting Now Available on Qbox.
At Qbox, we manage many thousands of clusters—for thousands of customers—and we enable seamless integration of many excellent open source tools. We provide easy integration with a large number of plugins. Read Tools for Monitoring Elasticsearch Performance to learn about the most popular tools for our customers.
5. Automatic backup with selective restore
Here at Qbox we have wide flexibility to accommodate varying requirements of our customers and their cluster configurations because we fully exploit the Elasticsearch snapshot/restore API. Most importantly, we precisely tune the snapshot process to prevent any adverse impact to user operations.
All Qbox clusters get a daily snapshot, and we store all files in a remote, redundant repository for at least 7 days. You can use our cluster dashboard to easily perform a manual restore for any cluster to any state within the previous week. Read more in our article Better Backups for Qbox with Elasticsearch Snapshot/Restore.
6. Security — strong but flexible
We provide full yet simple security, right down to the network-level. We provide IP rules, SSL, HTTP authentication, and Amazon Virtual Private Cloud (VPC) peering.