-
Notifications
You must be signed in to change notification settings - Fork 113
Clarify MP region availability #2163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
cc @yuvielastic |
🔍 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 |
There was a problem hiding this comment.
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 :)
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). |
There was a problem hiding this comment.
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 <58563081+shainaraskas@users.noreply.github.com>
When procuring {{ecloud}} 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 cloud service provider can be used. This ensures that you can enjoy the benefits of the marketplace, such as {{ecloud}} contributing towards your spend commitment with cloud providers. | ||
|
||
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). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
based on the info you shared:
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). | |
You can implement a multi-cloud strategy by creating a separate {{ecloud}} organization, either from another marketplace, or directly at [cloud.elastic.co](https://cloud.elastic.co). |
I prefer 'implement' over 'support' because it feels more actionable
Also see https://github.com/elastic/cloud/pull/143797