Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 5 additions & 10 deletions manage-data/ingest/_snippets/agentless-integrations-faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -78,14 +78,9 @@ No, agentless integrations can not use a specific range of static IP addresses f

## Do agentless integrations work if I'm using traffic filtering?

::::{applies-switch}

:::{applies-item} serverless: ga
Agentless integrations do not support traffic filtering.
:::

:::{applies-item} stack: ga 9.1+
Agentless integrations support traffic filtering. No additional configuration is necessary.
:::
```{applies_to}
stack: ga 9.1+
serverless: ga
```

::::
Yes. Agentless integrations support traffic filtering, and no additional configuration is necessary.
1 change: 0 additions & 1 deletion manage-data/ingest/agentless/agentless-integrations.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,6 @@ During technical preview, there are no additional costs associated with deployin
* Agentless integrations are supported only on {{ech}}, {{sec-serverless}}, and {{obs-serverless}} deployments.
* On {{ech}}, agentless integrations require a working [{{fleet-server}}](/reference/fleet/fleet-server.md).
* To set up a new agentless integration, you need the `Actions and connectors: all` [{{kib}} privilege](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md).
* For {{serverless-short}} deployments, traffic filtering must be turned off.

## Generally available (GA) agentless integrations

Expand Down
Loading