We include a dedicated HA instance of Kibana automatically configured to connect to your Elasticsearch cluster. Kibana allows you to build rich visualizations of your Elasticseach data using charts and graphs.
The table below show what versions of Kibana you’ll have based on what version of Elasticsearch you’ve created.
|Elasticsearch Version||Kibana Version|
You can view the plain text and SSL URL addresses for Kibana under the Connect heading of the Control Panel. Before you can access Kibana you will need to add Kibana-specific ACLs under the Security heading.
All ObjectRocket for Elasticsearch clusters run on dedicated, single-tenant containers to provide isolation at the process and filesystem level.
SSL is enabled on all Elastic search clusters and we provide https connection strings for:
- ElasticSearch REST API via both public interfaces and Rackspace ServiceNet
ACLs / IP Whitelisting¶
All access to Elasticsearch clusters is gated by Access Control Lists (ACLs), so only the IPs or IP ranges specified will have access to the cluster. We allow separate ACLs for the Elasticsearch REST API, java transport client, and Kibana.
ObjectRocket for Elasticsearch clusters also require user authentication for all communications. We allow three different user roles on the platform:
- Admin: Full read/write access to Elasticsearch and Kibana
- Read only: Read-only access to Elasticsearch
- Kibana only: Access to Kibana only
Encryption at rest¶
Encryption at rest is offered as an optional add-on to ObjectRocket for Elasticsearch clusters. When encryption at rest is selected:
- Storage volumes on the cluster are encrypted on disk, using volume-level encryption
- ObjectRocket manages your encryption keys, so you don’t have to
- All backups/snapshots of that cluster are encrypted as well
Additional fees may apply. Please check out our plans and pricing for more information.
By default, we install a number of elasticsearch plugins on all ObjectRocket for Elasticsearch clusters. Due to changes in Elasticsearch across versions, not all of the default plugins will be supported on every version. A quick matrix of what’s supported on each version is below
|delete-by-query||✓||✓||(now in API)|
Descriptions of these plugins are listed below:
ElasticHQ is a plugin that provides a web interface for monitoring, management, and querying your Elasticsearch cluster. ElasticHQ is installed by default at
/_plugin/hq (2.1+ uses lowercase). You can also access hq, by selecting the button that says HQ on the instance details page.
Kopf is a plugin similar to HQ, however as HQ doesn’t support ES 2.x+. we install this as an alternative. Kopf is installed by default at
/_plugin/kopf. You can also access kopf, by selecting the button that says kopf on the instance details page.
Elasticsearch-head is another popular plugin for managing and monitoring Elasticsearch clusters. Elasticsearch-head is also installed by default and is located at
/_plugin/head. You can also access Elasticsearch-head, by selecting the button that says head on the instance details page.
AWS Direct Connect¶
We offer AWS Direct Connect so users connecting from AWS can connect to ObjectRocket datacenters via dedicated network connections. See the FAQ for details on where we offer Direct Connect links to AWS.
We offer Rackspace ServiceNet connectivity within Rackspace datacenters, which correspond to US-East-IAD1, US-Dallas-DFW, US-Chicago-ORD2, and EU-London-LON5.
The ObjectRocket platform can automatically retrieve IP addresses from your Rackspace Cloud or AWS environment, and create an ACL for each of those. This feature is currently limited to retrieving IP addresses from a single AWS region.