Skip to content

Update ECH minimum prod RAM - #7873

Open
stefnestor wants to merge 2 commits into
elastic:mainfrom
stefnestor:stef_prodMins
Open

Update ECH minimum prod RAM#7873
stefnestor wants to merge 2 commits into
elastic:mainfrom
stefnestor:stef_prodMins

Conversation

@stefnestor

Copy link
Copy Markdown
Member

Summary

👋 howdy, team! This modifies ECH's Minimum size recommendations for production use that

  • AFAIK we say "you should" not "we recommend"
  • sub-links all features
  • adds in info about 1GB Tiebreakers doesn't break the 4GB rule
  • sub-links about Fleet 👈 It's called "Integrations Server" ECH-level & not sure how y'all handle that

Related Support articles this tidies up into high-level statements

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes
  • No

@stefnestor
stefnestor requested a review from a team as a code owner August 7, 2026 21:58
@stefnestor stefnestor added the enhancement New feature or request label Aug 7, 2026
@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check 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.

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

🔍 Preview links for changed docs

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
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.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Docs review summary

Focus areas

  • Style and clarity: Good improvement overall — "we recommend" → "you should" aligns with active/second-person voice, and sub-linking features is a nice clarity win. Two inline naming-consistency issues flagged below.
  • Jargon: No unexplained Elastic-internal jargon introduced in the diff; linked terms (ILM, Watcher, Machine Learning) are all linked to their own pages for context.
  • Frontmatter and applies_to: Unchanged by this PR; frontmatter (applies_to, products, mapped_pages) is intact and not touched.
  • Content type fit: No change — this remains part of an overview-style page and the new bullets fit the existing list structure.
  • Parent issue satisfaction: Not applicable (no linked issue; PR body describes ad hoc improvements referencing internal support articles).

Nits

  • Pre-existing Vale findings on unchanged lines (mapped_pages caution on line 2, "Just" on line 25, "easy" on line 63, "may" on line 72) are outside this diff's scope and not introduced by this PR — no action needed here.

Notes

  • Verified terminology against docset.yml substitutions and sibling pages (ec-customize-deployment-components.md, example-kubernetes-fleet-managed-agent-helm.md) to confirm the "Integrations Server" vs. "Fleet"/"Integration Server" naming question raised in the PR description.

Generated by Docs review agent for #7873 · sonnet50 · 48.2 AIC · ⌖ 6.64 AIC · ⊞ 15.9K

Comment thread deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md Outdated
Comment thread deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md Outdated
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant