Restricting connections with IP filtering


Restricting connections with IP filteringedit

You can apply IP filtering to application clients, node clients, or transport clients, in addition to other nodes that are attempting to join the cluster.

If a node’s IP address is on the blacklist, the Elasticsearch security features allow the connection to Elasticsearch but it is be dropped immediately and no requests are processed.

Elasticsearch installations are not designed to be publicly accessible over the Internet. IP Filtering and the other capabilities of the Elasticsearch security features do not change this condition.

Enabling IP filteringedit

The Elasticsearch security features contain an access control feature that allows or rejects hosts, domains, or subnets. If the operator privileges feature is enabled, only operator users can update these settings.

You configure IP filtering by specifying the and settings in elasticsearch.yml. Allow rules take precedence over the deny rules.

Unless explicitly specified,* settings default to the corresponding* setting’s value. "" ""

The _all keyword can be used to deny all connections that are not explicitly allowed. [ "", "", "", "" ] _all

IP filtering configuration also support IPv6 addresses. "2001:0db8:1234::/48" "1234:0db8:85a3:0000:0000:8a2e:0370:7334"

You can also filter by hostnames when DNS lookups are available. localhost '*'

Disabling IP Filteringedit

Disabling IP filtering can slightly improve performance under some conditions. To disable IP filtering entirely, set the value of the setting in the elasticsearch.yml configuration file to false. false

You can also disable IP filtering for the transport protocol but enable it for HTTP only. false true

Specifying TCP transport profilesedit

TCP transport profiles enable Elasticsearch to bind on multiple hosts. The Elasticsearch security features enable you to apply different IP filtering on different profiles. _all _all

When you do not specify a profile, default is used automatically.

HTTP filteringedit

You may want to have different IP filtering for the transport and HTTP protocols. localhost '*' _all

Dynamically updating IP filter settingsedit

In case of running in an environment with highly dynamic IP addresses like cloud based hosting, it is very hard to know the IP addresses upfront when provisioning a machine. Instead of changing the configuration file and restarting the node, you can use the Cluster Update Settings API. For example:

PUT /_cluster/settings
  "persistent" : {
    "" : ""

You can also dynamically disable filtering completely:

PUT /_cluster/settings
  "persistent" : {
    "" : false

In order to avoid locking yourself out of the cluster, the default bound transport address will never be denied. This means you can always SSH into a system and use curl to apply changes.