Docs fix — frontmatter: shard 20/28 — 20 pages

[github-actions]

Generated by gh-aw-docs-frontmatter-sweep for elastic/docs-content on 2026-W19.

Shard 20/28 · 96 pages in slice · 0 recently-changed · 96 total in scope · corpus 2723 pages.

Findings (20)

- file: deploy-manage/api-keys/serverless-project-api-keys.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Reference for API key types in Elastic Cloud Serverless projects, including personal keys for external access and managed keys for background tasks."

- file: deploy-manage/cloud-organization/billing/manage-billing-notifications.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Set up spending budgets and email notifications in Elastic Cloud to track resource usage and receive alerts at defined cost thresholds."

- file: deploy-manage/deploy/cloud-enterprise/configure-operating-system.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Prepare Linux hosts for Elastic Cloud Enterprise installation by configuring Ubuntu, RHEL, Rocky Linux, or SLES operating systems."

- file: deploy-manage/deploy/cloud-on-k8s/connect-to-apm-server.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Connect to APM Server running in ECK, including service configuration, secret token setup, and API key authentication."

- file: deploy-manage/deploy/cloud-on-k8s/elastic-maps-server.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Deploy and configure Elastic Maps Server on Kubernetes with ECK as an alternative to the Elastic Maps Service."

- file: deploy-manage/deploy/cloud-on-k8s/service-meshes.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Integrate ECK and Elastic Stack applications with Istio and Linkerd service meshes in Kubernetes."

- file: deploy-manage/deploy/elastic-cloud/change-hardware.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Modify instance configurations for individual Elastic Cloud deployment components without changing the overall hardware profile."

- file: deploy-manage/deploy/elastic-cloud/fedramp.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Overview of Elastic FedRAMP authorized Cloud offerings for Platinum and Enterprise subscribers hosting regulated data on AWS GovCloud."

- file: deploy-manage/deploy/self-managed/setting-system-settings.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Reference for applying operating system limits and environment variables for Elasticsearch across different installation packages and init systems."

- file: deploy-manage/deploy/self-managed/system-config-tcpretries.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Configure the Linux TCP retransmission timeout to reduce wait times when Elasticsearch node communication is disrupted."

- file: deploy-manage/deploy/self-managed/tutorial-self-managed-secure.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Step-by-step tutorial for replacing auto-generated TLS certificates with custom ones across a self-managed Elastic Stack."

- file: deploy-manage/distributed-architecture/shard-allocation-relocation-recovery.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "How Elasticsearch allocates, relocates, and recovers shards across nodes, with configuration options to control placement and balancing behavior."

- file: deploy-manage/manage-spaces-fleet.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Configure space-aware Fleet to manage Agent policies and integrations per Kibana space, with role-based access control for agent management."

- file: deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Collect Elasticsearch monitoring data with Metricbeat and ship it to a separate monitoring cluster for stack observability."

- file: deploy-manage/production-guidance/kibana-in-production-environments.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Best practices for deploying Kibana in production, covering scalability, load balancing, memory configuration, and performance tuning."

- file: deploy-manage/security/enabling-cipher-suites-for-stronger-encryption.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Install the Java Cryptography Extension Unlimited Strength policy files to enable stronger TLS cipher suites for Elasticsearch."

- file: deploy-manage/tools/cross-cluster-replication/ccr-inspect-progress.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Monitor cross-cluster replication progress and inspect follower shard statistics to identify replication issues."

- file: deploy-manage/tools/snapshot-and-restore/ece-restore-snapshots-containing-searchable-snapshots-indices-across-clusters.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Restore Elasticsearch snapshots containing searchable snapshot indices across clusters in Elastic Cloud and ECE deployments."

- file: deploy-manage/users-roles/cluster-or-deployment-auth/manage-elastic-user-cloud.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Reset the built-in elastic user password for Elastic Cloud Hosted and Elastic Cloud Enterprise deployments."

- file: explore-analyze/machine-learning/anomaly-detection.md
  line: 1
  category: missing-description
  severity: high
  evidence: "frontmatter has no `description` field"
  suggested_fix: |
    description: "Overview of Elastic anomaly detection for identifying unusual patterns in time series data using machine learning."

+48 additional pages will surface in next sweep.

Done when

• All listed pages have a non-empty, <=200-character description field and required frontmatter keys present per the repo's frontmatter schema.
• A PR addressing this issue is merged.

Notes

• Snippet files (_snippets/ directories) and raw-migrated-files/ were excluded from findings as they do not require frontmatter.

Generated by Docs frontmatter sweep agent · ● 1M · ◷