Document how to configure advanced SSL/TLS settings for the Fleet Server integration - #7657
Open
vishaangelova wants to merge 4 commits into
Open
Document how to configure advanced SSL/TLS settings for the Fleet Server integration#7657vishaangelova wants to merge 4 commits into
vishaangelova wants to merge 4 commits into
Conversation
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
Contributor
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Contributor
🔍 Preview links for changed docs |
Co-authored-by: Cursor <cursoragent@cursor.com>
vishaangelova
force-pushed
the
3573-fleet-server-advanced-ssl-configs
branch
from
July 30, 2026 13:29
c5d911f to
a167fd8
Compare
vishaangelova
marked this pull request as ready for review
July 30, 2026 13:31
Member
Author
|
Hey @ebeahan, could you direct me to an SME who can review the changes in this PR? Thank you! 🙏 |
vishaangelova
changed the title
ycombinator
approved these changes
Jul 30, 2026
AndersonQ
reviewed
Jul 30, 2026
Co-authored-by: Cursor <cursoragent@cursor.com>
vishaangelova
force-pushed
the
3573-fleet-server-advanced-ssl-configs
branch
from
July 30, 2026 19:51
450ac0f to
bf4ddc8
Compare
Add section headings for the common, client, and server SSL option groups, clarify the intro that explains when each group applies, fix a typo, and point the secure-connections cross-link at the new anchor. Co-authored-by: Cursor <cursoragent@cursor.com>
vishaangelova
force-pushed
the
3573-fleet-server-advanced-ssl-configs
branch
from
July 30, 2026 19:53
bf4ddc8 to
6398968
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
Documents how to configure the Fleet Server input's SSL/TLS settings (
cipher_suites,supported_protocols, and otherserver.ssloptions) using the Fleet Server integration policy's advanced YAML, adds a connectivity-risk warning, and clarifies that these settings have noelastic-agent installCLI flags.Resolves #3573
Changes
reference/fleet/secure-connections.md(primary): New "Configure advanced SSL/TLS settings for Fleet Server" section explaining thatsupported_protocolsandcipher_suitesaren't exposed as UI fields or install flags and must be set using aserver.sslblock in the Fleet Server integration policy's Custom fleet-server configurations (Advanced options).Includes the UI procedure, a YAML example, default behavior, a link to the full settings reference, and a connectivity-risk warning. Also adds a note in the CLI section clarifying no install flags exist for these settings.
reference/fleet/fleet-server-scalability.md: Adds a pointer from the "Advanced Fleet Server options" section to the new section.reference/fleet/elastic-agent-ssl-configuration.md: Adds a note at the server SSL options that these settings also apply to the Fleet Server input underserver.ssl, linking to the new section.Verification
Content was verified against the codebase in the
kibana,integrations,fleet-server, andelastic-agent-libsrepos:fleet_serverpackage exposes acustomYAML var that passesserver.sslthrough verbatim.fleet-server'sserver.sslmaps totlscommon.ServerConfig, and the defaultsupported_protocols(TLSv1.2,TLSv1.3) and cipher suite list match the documented reference values.Generative AI disclosure
Tool(s) and model(s) used: Cursor / Claude Opus 4.8 High