[Website]: mark "Elastic Cloud audit trail" as tech preview

[rseldner]

Before you submit

• This issue is about a documentation page, flow, or piece of content.

Type of issue

Missing information

What documentation page or section is affected

https://www.elastic.co/docs/deploy-manage/monitor/log-delivery/cloud-audit-trail

What happened?

I think this doc should indicate the feature is in tech preview to align with the integration doc.
https://www.elastic.co/docs/reference/integrations/elastic_govcloud

Additional info

No response

[github-actions]

Elastic Docs AI Menu

Check one box to run an AI workflow for this issue.

• Scope the docs work (docs-scope). Status: completed. View progress.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

✅ ScopeBot finished. https://github.com/elastic/docs-content/actions/runs/36822575300

Generated from Gh Aw Issue Scope

[github-actions]

🟢 ScopeBot Results: Full assessment

Summary

The issue asks to identify Elastic Cloud audit trail as a technical-preview feature on the affected audit-trail page, consistent with the linked Elastic GovCloud integration documentation. The published audit-trail page currently states that the feature is limited to FedRAMP Moderate environments but does not identify it as technical preview; the integration page describes Elastic GovCloud integration v0.1.0 as technical preview.

Request accuracy

Not verifiable against code. The published documentation supports the requested documentation change, but no linked product-code change was provided.

Recommended docs targets

Page	URL	Action	Confidence	Why this page?
Elastic Cloud audit trail	https://www.elastic.co/docs/deploy-manage/monitor/log-delivery/cloud-audit-trail	Update existing page	Medium	This is the affected page. Its source currently scopes Elastic Cloud Hosted as GA in frontmatter and opens with a FedRAMP Moderate-only admonition, but does not state that the feature is technical preview. Align its lifecycle metadata and/or page notice with the integration's technical-preview status after confirming the repository's expected lifecycle tag.

How to tackle this

1. Confirm the lifecycle status and the canonical wording for Elastic Cloud audit trail with the owning product team, using the Elastic GovCloud integration page's “v0.1.0, technical preview” status as the current documentation evidence.
2. Update the audit-trail page's lifecycle metadata and visible notice as needed so readers see the technical-preview status, while preserving the existing FedRAMP Moderate limitation.
3. Check the rendered page and nearby lifecycle metadata for consistency; run the applicable docs style and build checks.

Scope boundary

No changes appear necessary to the Elastic GovCloud integration page, setup instructions, API examples, or other audit-log pages unless the product team confirms that their lifecycle status or wording is also incorrect.

Questions to go deeper

• Is “technical preview” the confirmed lifecycle status for the audit-trail feature itself, or only for the Elastic GovCloud integration package?
• What exact applies_to value and visible notice should the audit-trail page use for this lifecycle state?
• Should the audit-trail page retain ech: ga for any generally available subset, or should its entire Elastic Cloud Hosted scope be changed to technical preview?

Generated from Gh Aw Issue Scope · ◷

[consulthys]

@rseldner it's actually the other way, Elastic Cloud Audit trail went GA in GovCloud yesterday, it's the integration doc that should not show tech preview, I'll take care of it

[consulthys]

The integration is now 1.0.0 https://epr.elastic.co/package/elastic_govcloud/1.0.0/
The documentation and the integration now agree, no more technical preview