Skip to content

AWS billing account change - #9234

Open
demers-eric wants to merge 3 commits into
mainfrom
aws-billing-account-change
Open

demers-eric wants to merge 3 commits into
mainfrom
aws-billing-account-change

Conversation

@demers-eric

Copy link
Copy Markdown
Contributor

Summary

Added section on changing billing accounts for AWS Marketplace subscriptions.

Generative AI disclosure

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

Added section on changing billing accounts for AWS Marketplace subscriptions.
@demers-eric
demers-eric requested a review from a team as a code owner November 5, 2026 13:46
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

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

@github-actions

github-actions Bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

🔍 Preview links for changed docs

@github-actions

github-actions Bot commented Nov 5, 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.

Co-authored-by: Ramon Butter <ramon.butter@elastic.co>

@eedugon eedugon 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.

I've proposed an update to improve the reading flow.

But please let me know if my understanding is incorrect. I've assumed that we want the users to:

  • Subscribe with the new account to Elastic
  • Omit the rest of the signup process (complete step 3 with 4 substeps)
  • Then contact Elastic support.

I also assume that omitting the "follow the steps displayed to complete the signup process" will be something that the user will understand naturally. If the step 3 is part of a UX dialogue and they just need to stop handling it and contact Elastic support instead we should be clearer.

Co-authored-by: Edu González de la Herrán <25320357+eedugon@users.noreply.github.com>
@demers-eric

Copy link
Copy Markdown
Contributor Author

@eedugon I incorporated your changes, thanks

This branch was successfully deployed

1 active deployment
docs-preview — fb4a2a0c Deployed Nov 6, 2026 by github-actions[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants