[Jul 31] Add cloud region info

[shainaraskas]

Adds information about available cloud regions: cloud regions

links to cloud region docs in ES project creation docs: link

Added links in obs and sec project creation docs as well:
elastic/observability-docs#4093
elastic/security-docs#5604

[elasticdocs]

🚀 Built elastic-dot-co-docs-preview-docs successfully!

• https://elastic-dot-co-docs-production-6a14jqx0t-elastic-dev.vercel.app

• Built with commit ffb8025

Issues? Visit #next-docs in Slack

[florent-leborgne]

Nice addition!

[yuvielastic]

I also see a couple of references of region in the docs; would it make sense to link the new region page to that?

• https://www.elastic.co/docs/current/serverless/observability/create-an-observability-project (Region: The region where your project will live. The region should be as close as possible to the location of your data.)
• https://www.elastic.co/docs/current/serverless/security/create-project (Region: The cloud platform’s region where your project will live. The region should be as close as possible to the location of your data. )

Also, for O11y & Security - Is there a reason why we added the following line:

The region should be as close as possible to the location of your data.

I don't see a reason for this to be mentioned as it's customer choice to choose the region which can be far away from the location of their data. I will recommend to remove this line.

Thoughts?

[shainaraskas]

I also see a couple of references of region in the docs; would it make sense to link the new region page to that?

• https://www.elastic.co/docs/current/serverless/observability/create-an-observability-project (Region: The region where your project will live. The region should be as close as possible to the location of your data.)
• https://www.elastic.co/docs/current/serverless/security/create-project (Region: The cloud platform’s region where your project will live. The region should be as close as possible to the location of your data. )

Also, for O11y & Security - Is there a reason why we added the following line:

The region should be as close as possible to the location of your data.

I don't see a reason for this to be mentioned as it's customer choice to choose the region which can be far away from the location of their data. I will recommend to remove this line.

Thoughts?

hi @yuvielastic - I've taken care of the link additions in these PRs, which depend on this PR to merge before they can pass CI:

elastic/observability-docs#4093
elastic/security-docs#5604

I'll remove the guidance around proximity from those two pages in those PRs as well.

[KOTungseth]

I don't see a reason for this to be mentioned as it's customer choice to choose the region which can be far away from the location of their data. I will recommend to remove this line.

Thoughts?

Yes, this is a customer choice, but we should provide guidance on the best possible region option they should choose. I think we should keep this in.

[yuvielastic]

Yes, this is a customer choice, but we should provide guidance on the best possible region option they should choose. I think we should keep this in.
@KOTungseth But this statement isn't correct as there are multiple factors that customers can look at to identify the best possible region.

Reasons could be:

• Data residency requirements
• Regulatory compliance
• Latency
• Cost
• Disaster recovery needs
• Proximity (location)

Some of these reasons are something that's not guided by us but chosen by customers (based on their preferences) that we are not privy to.

So either we add these bunch of possible reasons (which would confuse customers more as they may not be necessary thinking from this guidance POV) or to keep things simple, I would suggest simply not to mention. My vote is to keep things simple and not mention the guidance at all.

[shainaraskas]

@KOTungseth + @yuvielastic in the new region page in this PR, we give them limited guidance:

If you aren't sure which region to pick, choose one that is geographically close to you to reduce latency.

it's a little less prescriptive than the statements that appear in the observability and security docs. We can assume that people who need guidance will click through and read the less prescriptive recommendation there.

[KOTungseth]

@KOTungseth + @yuvielastic in the new region page in this PR, we give them limited guidance:

If you aren't sure which region to pick, choose one that is geographically close to you to reduce latency.

it's a little less prescriptive than the statements that appear in the observability and security docs. We can assume that people who need guidance will click through and read the less prescriptive recommendation there.

I'm good with this if @yuvielastic is good with this.

[yuvielastic]

LGTM - Thanks for improvising on it 😊

[yuvielastic]

Added 2 small comments to remove confusion. Rest LGTM

Added 2 small comments; to make changes before merging/approving.

[kilfoyle]

LGTM! 🐎

[yuvielastic]

As the regions have been launched, can we please merge the documentation?