When comparing IntelliJ Elasticsearch vs ElasticHQ, the Slant community recommends ElasticHQ for most people. In the question“What are the best Elasticsearch GUI clients?” ElasticHQ is ranked 2nd while IntelliJ Elasticsearch is ranked 12th. The most important reason people chose ElasticHQ is:
Can be deployed on AWS, Azure and any other cloud service.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Query DSL and REST API Autocomplete
Pro Simple search with Kibana query language
Pro Built-in Elasticsearch doumentation
Pro SSL, SSH and AWS request signing
Pro Displays basic cluster and index information
Pro Supports all versions
Pro Friendly interface
Pro Export to csv and json
Pro Cross-platform
Pro Cloud ready
Can be deployed on AWS, Azure and any other cloud service.
Pro Most comprehensive set of tools
Can manage and keep track of ES Datasets in real time, is cloud-ready and has been battle-tested by multiple large companies.
Pro Installation is easy
ElasticHQ is easy to install and accessible from your browser. Can be installed in just 2 commands and will remain running until shutdown. Installation docs can be found here.
Pro Real-Time Monitoring
ElasticHQ allows you to view real-time threads, individual cluster nodes, cluster runtime metrics, and configurations.
Pro Open source
Licensed under Apache 2 can be used and re-distributed without complications.
Pro Cluster management
Complete control over clusters, nodes, indexes, and mappings.
Cons
Con Not maintained anymore
Con Error when using SSL and Python 3.6+
This bug is under investigation but is not close to being solved. See here.