Skip to content

[8.18]Cloud section updates #6712

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Conversation

benironside
Copy link
Contributor

Twin PR of elastic/docs-content#1034

Minor updates related to agentless integrations.

@benironside benironside self-assigned this Apr 7, 2025
@benironside benironside requested a review from a team as a code owner April 7, 2025 17:07
Copy link

github-actions bot commented Apr 7, 2025

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@benironside benironside changed the title [8.18[]Cloud section updates [8.18]Cloud section updates Apr 7, 2025
Copy link
Contributor

@nastasha-solomon nastasha-solomon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple of small edits, but overall looks good!

To learn more about agentless CSPM deployments, refer to the getting started guides for CSPM on <<cspm-get-started, AWS>>, <<cspm-get-started-azure, Azure>>, or <<cspm-get-started-gcp, GCP>>.

## Beta agentless integrations
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this supposed to be a L2 header? In the preview, it's appearing as a sub-section with in the GA agentless integration's section.

Suggested change
## Beta agentless integrations
== Beta agentless integrations


WARNING: Agentless deployment for the following integrations is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit and optional edit ofc: bullets seem more appropriate for the following list since it's unordered.

Each agentless integration deployment counts towards the maximum number of agentless integrations you can have in the same project. When you reach the maximum, you'll see an error message similar to `You have deployed the maximum number of agentless integrations. To continue, remove some or use agent-based deployment.` You won't be able to deploy another agentless integration until you remove an existing one. All <<agentless-integrations>> count towards this limit.




[discrete]
== KSPM FAQ
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this is outside of the scope of the PR, but did want to note these entries are formatted slightly differently because they're not preceded by an empty line.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, but I'm going to save this and your other comment for the future since this is a twin PR.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

works for me : )

benironside added a commit to elastic/docs-content that referenced this pull request Apr 7, 2025
Twin PR of elastic/security-docs#6712

Removes reference to Elastic's native LLM, which won't be present in
this release.
@benironside
Copy link
Contributor Author

will be fixed here #6714

@benironside benironside closed this Apr 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants