Improve and regroup agentless costs mentions #27539
Open
+10
−11
Conversation
This file contains 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
aviat
added
the
under_review
Preview links (active after the
|
cyrbouchiat
approved these changes
Feb 11, 2025
aviat
removed
the
under_review
|
/merge |
Devflow running:
|
maycmlee
reviewed
Feb 11, 2025
| When using Agentless Scanning, there are additional costs for running scanners in your cloud environments. To optimize on costs while being able to reliably scan every 12 hours, Datadog recommends setting up [Agentless Scanning with Terraform][6] as the default template, as this also avoids cross-region networking. | ||
| When using Agentless Scanning, there are additional cloud provider costs for running scanners and analyzing your cloud environments. | ||
|
|
||
| Cloud provider costs are under $1 per scanned host per year for accounts following the [recommended configuration][13]. Reach out to your [Datadog Customer Success Manager][7] if you have more questions. |
There was a problem hiding this comment.
We usually don't talk about costs in the docs, and usually link to the pricing page. In this situation, can we just have customers reach out to CSM about costs? So something like:
Suggested change
| Cloud provider costs are under $1 per scanned host per year for accounts following the [recommended configuration][13]. Reach out to your [Datadog Customer Success Manager][7] if you have more questions. | |
| Reach out to your [Datadog Customer Success Manager][7] if you have questions about Cloud provider costs for the [recommended configuration][13]. |
| [1]: mailto:[email protected] | ||
| [2]: /security/cloud_security_management/agentless_scanning#cloud-storage-scanning | ||
| [1]: /security/cloud_security_management/agentless_scanning#cloud-storage-scanning | ||
| [1]: /security/cloud_security_management/agentless_scanning#cloud-service-provicer-cost |
There was a problem hiding this comment.
Suggested change
| [1]: /security/cloud_security_management/agentless_scanning#cloud-service-provicer-cost | |
| [2]: /security/cloud_security_management/agentless_scanning#cloud-service-provicer-cost |
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:
Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the
<yourname>/descriptionnaming convention) and then add the following PR comment:Additional notes