This section provides an overview of the features available in the ObjectRocket hosted Elasticsearch offering.
All ObjectRocket Elasticsearch offerings include a dedicated HA instance of Kibana automatically configured to connect to your Elasticsearch cluster. Kibana lets you use charts and graphs to build rich visualizations of your Elasticsearch data.
The following table displays the Kibana versions associated with the different versions of Elasticsearch:
|Elasticsearch version||Kibana version|
View the plain text and Secure Socket Layer (SSL) addresses for Kibana in the Connect tab of the Control Panel. Before you can access Kibana, you must whitelist Kibana-specific IP addresses.
This section has information about security.
All ObjectRocket Elasticsearch clusters run on dedicated, single-tenant containers to give isolation at the process and filesystem level.
All Elasticsearch clusters have SSL encryption and offer https connection strings for the following:
- ElasticSearch REST API via both public interfaces and Rackspace ServiceNet
ACLs and IP whitelisting¶
Only authorized IPs or IP ranges can access the Elasticsearch cluster. You can use separate ACLs for the Elasticsearch REST API, Java TransportClient, and Kibana.
ObjectRocket for Elasticsearch clusters require user authentication for all communications. This platform has the following different user roles:
- Admin: Full read/write access to Elasticsearch and Kibana
- Read only: Read-only access to Elasticsearch
- Kibana: Similar to read only, but with added permissions to change Kibana dashboards
Encryption at rest¶
Encryption at rest is an optional add-on to ObjectRocket for Elasticsearch clusters. When you select encryption at rest, have have the following functionality:
- Volume-level encryption secures storage volumes on the cluster by encrypting them on the disk.
- ObjectRocket manages your encryption keys, so you don’t have to.
- This add-on also encrypts all backups and snapshots of that cluster.
Extra fees might apply. For more information, visit the plans and pricing page.
Dedicated master nodes¶
ObjectRocket for Elasticsearch includes three master nodes with every instance. You can assign cluster management tasks to a single node while creating your instance with the Mission Control interface. This increases stability across your entire cluster.
RocketScale™ in ObjectRocket monitors your cluster and automatically adds data nodes if you’re in danger of running out of storage space. This functionality ensures that your cluster stays out of yellow or red status and always has enough space to meet your data needs.
You can adjust the RocketScale settings to match your cluster to your needs by using the Mission Control interface.
ObjectRocket for Elasticsearch clusters include several default Elasticsearch plug-ins. Because of differences across Elasticsearch versions, not every version supports all plug-ins. The following table explains the various plug-ins supported by different Elasticsearch versions:
|mapper-attachments||✓||✓||(replaced by ingest-attachment)||(replaced by ingest-attachment)|
|delete-by-query||✓||✓||(now in API)||(now in API)|
Support for more plug-ins is available on a case by case basis. Contact firstname.lastname@example.org if you would like to install different plug-ins or turn off any of existing plug-ins.
The following sections provide descriptions of some available Elasticsearch plug-ins.
ElasticHQ provides a web interface for monitoring, managing, and querying your Elasticsearch cluster.
ObjectRocket installs ElasticHQ by default at
/_plugin/HQ or on version ES 2.1 at
/_plugin/hq. You can also access ElasticHQ by selecting HQ from the Instance Details page.
Kopf is similar to ElasticHQ, but it also supports ES 2.x+. Kopf is an alternative to ElasticHQ. By default, ObjectRocket installs Kopf at
/_plugin/kopf. You can also access kopf by selecting kopf from the Instance Details page.
Elasticsearch-head is a popular plug-in for managing and monitoring Elasticsearch clusters. By default, ObjectRocket installs Elasticsearch-head at
/_plugin/head. You can also access Elasticsearch-head by selecting head from the Instance Details page.
The delete-by-query plug-in returns the delete-by-query capability originally removed from Elasticsearch core.
AWS Direct Connect¶
AWS Direct Connect enables users connecting from AWS to access ObjectRocket data centers via dedicated network connections. See What is AWS Direct Connect? for more information.
Rackspace ServiceNet connectivity is available within Rackspace data centers, 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 cloud. This feature is currently limited to retrieving IP addresses from a single AWS region.