Add cross-region docs for aws

[shainaraskas]

• Fixes https://github.com/elastic/docs-content-internal/issues/303

Adds procedure for cross-region support for AWS privatelink

this is the core change:
https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/3128/deploy-manage/security/private-connectivity-aws#ec-aws-inter-region-private-link

I've also

• removed the consideration that we don't support cross-region privatelink
• indicated the endpoint "type" to select (privatelink ready partner services, according to the screenshots in jira [internal])
• updated a screenshot where there was a significant ui change in aws

question for reviewers

question about AZs in this new world. we have a consideration about AZs:

however, in the tutorial explaining the XR feature, amazon indicates that there is a change to the way AZs impact your configuration:

right now, we don't talk about selecting AZs that match the service provider availability. we do explain how to check your VPC endpoint availability, but we don't tell people to use this info in the setup. is this missing from the core setup procedure for non cross-region VPC endpoints?

[github-actions]

🔍 Preview links for changed docs

• deploy-manage/security/private-connectivity-aws.md

[alxchalkias]

@shainaraskas I think there's something that needs clarifying in the example:

VPC is in region 1, VPC endpoint is pointed to region 2 service name and enable cross region endpoint is also for region 2. If users were to follow the steps in "Create your VPC endpoint and DNS entries in AWS" there's a risk they will not be clear which service name the vpce should point to.

[shainaraskas]

VPC is in region 1, VPC endpoint is pointed to region 2 service name and enable cross region endpoint is also for region 2. If users were to follow the steps in "Create your VPC endpoint and DNS entries in AWS" there's a risk they will not be clear which service name the vpce should point to.

@alxchalkias this would explain why my verification failed when I tested. tested again with this approach and got a 🟢

I'll fix this.

[kilfoyle]

LGTM! ⛵

[alxchalkias]

LGTM! 🚀