Difference between revisions of "ElasticSearch Administration"
Jump to navigation
Jump to search
(Created page with "To help with Elasticsearch development, Archivematica comes with a plugin for Elasticsearch, called [http://mobz.github.com/elasticsearch-head/ Elasticsearch Head], that provi...") |
|||
(One intermediate revision by the same user not shown) | |||
Line 2: | Line 2: | ||
Elasticsearch Head will allow you to delete an index, if need be. | Elasticsearch Head will allow you to delete an index, if need be. | ||
+ | |||
+ | [[File:Elasticsearch_head_delete.png|Using ElasticSearch Head to delete an index]] | ||
+ | |||
+ | ==Access Control== | ||
+ | |||
+ | The only way to limit access to ElasticSearch, currently, is using your server's firewall configuration. You'll likely want to configure your server's firewall to limit access to ElasticSearch's TCP/IP port (9200). It is recommended to only allow access by 127.0.0.1 (the server itself) and the IPs of any other servers or workstations that should be able to access it. |
Latest revision as of 17:00, 24 June 2013
To help with Elasticsearch development, Archivematica comes with a plugin for Elasticsearch, called Elasticsearch Head, that provides a web application for browsing and administering Elasticsearch data. It can be accessed at http://your.host.name:9200/_plugin/head/.
Elasticsearch Head will allow you to delete an index, if need be.
Access Control[edit]
The only way to limit access to ElasticSearch, currently, is using your server's firewall configuration. You'll likely want to configure your server's firewall to limit access to ElasticSearch's TCP/IP port (9200). It is recommended to only allow access by 127.0.0.1 (the server itself) and the IPs of any other servers or workstations that should be able to access it.