[8.16] Doc incompatibility between agentless integration and traffic filtering (backport #6549) #6552
+12
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #500
Updates the agentless intergation FAQ and the CSPM getting started guides for AWS, Azure, and GCP, to inform users that agentless integrations don't work in environments where traffic filtering is present.
Previews: Agentless FAQ (new FAQ item)
Get started with CSPM for AWS (new note at the end of the agentless deployment section — changes to Azure and GCP guides are identical)
This is an automatic backport of pull request #6549 done by Mergify.