Skip to content

Conversation

demers-eric
Copy link
Contributor

@demers-eric demers-eric requested a review from a team as a code owner July 16, 2025 18:56
@demers-eric demers-eric requested a review from shainaraskas July 16, 2025 18:56
@demers-eric
Copy link
Contributor Author

cc @yuvielastic

Copy link

github-actions bot commented Jul 16, 2025

🔍 Preview links for changed docs


When procuring Elastic Cloud through [AWS Marketplace](https://aws.amazon.com/marketplace/pp/prodview-voru33wi6xs7k), [Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/elastic.ec-azure-pp?tab=overview), or [GCP Marketplace](https://console.cloud.google.com/marketplace/product/elastic-prod/elastic-cloud), only the regions corresponding to the same hyperscaler can be used. This ensures that you can enjoy the benefits of the Marketplace, such as Elastic Cloud contributing towards your spend commitment with cloud providers.

You can support a multi-cloud strategy by subscribing to a separate Elastic Cloud organization, either from another Marketplace, or directly at cloud.elastic.co
Copy link
Collaborator

Choose a reason for hiding this comment

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

can you tell me more about what a multi-cloud strategy would be? is it for resilience?

is "subscribing to" the right phrase for the separate org? could it instead be "creating"?

url won't hyperlink unless we tell it to :)

Suggested change
You can support a multi-cloud strategy by subscribing to a separate Elastic Cloud organization, either from another Marketplace, or directly at cloud.elastic.co
You can support a multi-cloud strategy by subscribing to a separate {{ecloud}} organization, either from another marketplace, or directly at [cloud.elastic.co](https://cloud.elastic.co).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think the reasons for a multi-cloud strategy are many.

  • resilience can be one of them for sure
  • there might be technical reasons: for example, we recently ran into a very large AWS shop that needed to do o11y for thousands of Windows virtual workstations, so they
  • I imagine there can be commercial reasons as well, legacy/M&A considerations

Ok with "creating" 👍

Co-authored-by: shainaraskas <[email protected]>
@demers-eric demers-eric requested a review from ppf2 July 22, 2025 13:34
@demers-eric
Copy link
Contributor Author

@ppf2 you were involved in a number of customer cases related to serverless regions + MPs; can you please review this? TIA

@demers-eric demers-eric changed the title Clarify MP region availability Clarify MP region availability (serverless) Sep 12, 2025
Copy link
Collaborator

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

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

good to go

@demers-eric demers-eric enabled auto-merge (squash) September 12, 2025 19:45
@demers-eric demers-eric merged commit 4d788c6 into main Sep 12, 2025
6 of 7 checks passed
@demers-eric demers-eric deleted the mp-region-avail branch September 12, 2025 19:50
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