| applies_to |
|
|||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| navigation_title | Add IP filters | |||||||||||||||||||||
| products |
|
This section covers filtering network traffic by IP address or CIDR block.
The way you configure IP filters, and how filtering is enforced, depends on your deployment type.
:::{tip} If you use {{ech}} or {{eck}}, then other network security methods are also available. :::
In {{serverless-full}} and {{ech}}, IP filters are a type of network security policy. They are created at the organization level, and then applied at the deployment level. Follow these guides to learn how to create, apply, and manage these filters using your preferred method:
To learn how multiple IP filters are processed, and how IP filters and private connections work together in ECH, refer to .
:::{note} {{serverless-short}} Observability and Security projects must belong to a specific feature tier to apply IP filter policies:
- Observability: Observability Complete
- Security: Security Analytics Complete
:::
In {{ece}}, filter rules are created at the platform level, and then applied at the deployment level. Follow these guides to learn how to create, apply, and manage these policies using your preferred method:
To learn how multiple rules are processed, refer to .
In {{eck}} and self-managed clusters, IP filters are applied at the cluster level using elasticsearch.yml. Learn how to configure IP filters at the cluster level.