- Shield Reference for 2.x and 1.x:
- Introduction
- Getting Started with Shield
- How Shield Works
- Installing Shield
- Setting Up User Authentication
- Managing Users in an esusers Realm
- Configuring Role-based Access Control
- Configuring Auditing
- Securing Communications with Encryption and IP Filtering
- Configuring Clients and Integrations
- Managing Shield Licenses
- Example Shield Deployments
- Reference
- Limitations
- Troubleshooting
- Setting Up a Certificate Authority
- Release Notes
Using Elasticsearch for Apache Hadoop with Shield
editUsing Elasticsearch for Apache Hadoop with Shield
editElasticsearch for Apache Hadoop ("ES-Hadoop") is capable of using HTTP basic and PKI authentication and/or TLS/SSL when accessing an Elasticsearch cluster. For full details please refer to the ES-Hadoop documentation, in particular the Security section.
For authentication purposes, select the user for your ES-Hadoop client (for maintenance purposes it is best to create a dedicated user). Then, assign that user to a role with the privileges required by your Hadoop/Spark/Storm job. Configure ES-Hadoop to use the user name and password through the es.net.http.auth.user and es.net.http.auth.pass properties. If PKI authentication is enabled, setup the appropriate keystore and truststore instead through es.net.ssl.keystore.location and es.net.truststore.location (and their respective .pass properties to specify the password).
For secured transport, enable SSL/TLS through the es.net.ssl property by setting it to true. Depending on your SSL configuration (keystore, truststore, etc…) you might need to set other parameters as well - please refer to the ES-Hadoop documentation, specifically the Configuration and Security chapter.