[Website]: Add missing prerequisites to AWS Billing integration docs

Open Beginner friendly
#7,127 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
aws
Domain
documentation

Research direction

Start with the AWS Billing integration page at https://www.elastic.co/docs/reference/integrations/aws/billing and locate the “What do I need to use this integration?” section. Add the us-east-1 region requirement and the requirement to enable AWS billing alerts, preserving the CloudWatch reference; done means both prerequisites appear in that section.

Written by the indexing model from the issue text.

Description

documentation source:web Team:Ingest triaged

Page: https://www.elastic.co/docs/reference/integrations/aws/billing

The What do I need to use this integration? section is missing two prerequisites that are easy to overlook:

  • AWS billing metrics are stored in the US East (N. Virginia) (us-east-1) region only. The integration's region must include us-east-1 to collect data.
  • Billing alerts must be enabled in AWS. See [Enabling billing alerts]((docs.aws.amazon.com/redacted) in the AWS CloudWatch documentation.

Definition of done: Both prerequisites are added to the "What do I need to use this integration?" section of the AWS Billing integration page.

🤖 Refined by RefineBot on 2026-06-26. Original intent preserved.

RefineBot changes

What changed:

  • Fixed title grammar ("requirement" → "requirements") and added integration name for specificity
  • Removed empty list item between the two requirements
  • Added explicit definition of done
  • Restructured body with page link at top for scanability

What was preserved:

  • Both requirement bullet points and their content
  • Author's link to AWS CloudWatch documentation
  • Specific section URL target
Previous version
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/reference/integrations/aws/billing

What happened?

This integration needs two more very important requirement to collect data that any user can easily miss:

  • As the metrics are stored in the US East (N. Virginia) region only, the integration's region should include us-east-1 region
  • To collect the billing metrics, the user should enable the billing alerts by following this AWS reference: (docs.aws.amazon.com/redacted)

Add these two bullet points into the section https://www.elastic.co/docs/reference/integrations/aws/billing#what-do-i-need-to-use-this-integration.

Thanks!

Additional info

No response

TriageBot — Needs refinement
2026-06-26

Type: documentation

Section check:

  • ✅ What's missing/unclear: both missing prerequisites described with specific section URL
  • ❌ Definition of done: not explicitly stated (added in rewrite)

Ambiguity / scope notes:

  • Title grammar: "requirement" should be "requirements"; title lacked the integration name
  • Empty bullet point between the two requirements was a formatting artifact

Cross-references:

Next step: Rewritten above

Generated by Gh Aw Issue Triage for issue #7127 · 35.7 AIC · ⌖ 9.7 AIC · ⊞ 9.1K · ◷

Dominant language
No language data
Stars
47
Forks
262
Avg merge
3d 8h
Merged PRs (30d)
127

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/docs-content

All issues in elastic/docs-content

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.