Add Infraless Cloud Security instructions as a guide #31214
Merged
+75
−14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
Preview links (active after the
|
|
@janine-c I'm going to add the Editorial Review label since you're already listed as a reviewer on the PR. |
janine-c
reviewed
Aug 21, 2025
There was a problem hiding this comment.
Looks great, thank you! I made some very minor suggestions. I also put a question into Slack about whether this would cause confusion with Setting Up Cloud Security without Infrastructure Monitoring - if we can either combine or clearly differentiate these pages from each other so they don't cause confusion, then we'll be good to publish 🙂
content/en/security/cloud_security_management/guide/infraless-cloud-security.md
Outdated
Show resolved
Hide resolved
content/en/security/cloud_security_management/guide/infraless-cloud-security.md
Outdated
Show resolved
Hide resolved
Comment on lines
37
to
41
| If you're using the Docker containerized Agent, add and set the following environment variables to `false` to the [Cloud Security configuration for Agent][4]: | ||
| - `DD_ENABLE_PAYLOADS_EVENTS` | ||
| - `DD_ENABLE_PAYLOADS_SERIES` | ||
| - `DD_ENABLE_PAYLOADS_SERVICE_CHECKS` | ||
| - `DD_ENABLE_PAYLOADS_SKETCHES` |
There was a problem hiding this comment.
Suggested change
| If you're using the Docker containerized Agent, add and set the following environment variables to `false` to the [Cloud Security configuration for Agent][4]: | |
| - `DD_ENABLE_PAYLOADS_EVENTS` | |
| - `DD_ENABLE_PAYLOADS_SERIES` | |
| - `DD_ENABLE_PAYLOADS_SERVICE_CHECKS` | |
| - `DD_ENABLE_PAYLOADS_SKETCHES` | |
| If you're using the Docker containerized Agent, add and set the following environment variables to the [Cloud Security configuration for Agent][4]: | |
| ```shell | |
| -e DD_ENABLE_PAYLOADS_EVENTS=false \ | |
| -e DD_ENABLE_PAYLOADS_SERIES=false \ | |
| -e DD_ENABLE_PAYLOADS_SERVICE_CHECKS=false \ | |
| -e DD_ENABLE_PAYLOADS_SKETCHES=false \ | |
| ``` |
…cloud-security.md Co-authored-by: Janine Chan <[email protected]>
…cloud-security.md Co-authored-by: Janine Chan <[email protected]>
janine-c
approved these changes
Aug 25, 2025
janine-c
deleted the
Cyril-Bouchiat/infraless-cloudsecurity-insrtructions
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes