Endpoint inconsistency in different regions of Elastic Cloud

[Mkian (Mehdi Kianpour)]

In Elastic Cloud a custom endpoint alias is recently added which is good and it helps in some automations BUT I see an inconsistency in different regions when I get the endpoints which makes the automation unnecessarily more difficult.
I'm not sure if it's on purpose but in AWS us-east-1 region, kibana endpoints end with:
.aws.found.io:9243
for example:
https://foo.kb.us-east-1.aws.found.io:9243

But in other regions it ends with:
.aws.elastic-cloud.com:9243
example:
https://bar.kb.us-east-2.aws.elastic-cloud.com:9243

I really don't understand the logic behind it. Is it something specific to my deployments? anyone else noticing it?

Regards
Mehdi

[stephenb (Stephen Brown)]

Hi @Mkian

We are iterating towards the below notation / naming, I just don't think we have made it through all the regions yet. The references you still see with found is the original company we joined forces with to operate Elastic Cloud. Apologies, I do not have an exact time table for all the naming to be consistent.

@Mkian

https://bar.kb.us-east-2.aws.elastic-cloud.com:9243

[Mkian (Mehdi Kianpour)]

Thanks, good to know what I should use as default value of the new variable I have in code
apparently it's elastic-cloud.com

[Mkian (Mehdi Kianpour)]

also fyi @stephenb , i just found a new format:
.eu-central-1.aws.cloud.es.io

[stephenb (Stephen Brown)]

Keep Looking you might find more

Although I think that is it for AWS combos

I think most gcp follow this pattern at this time.
nnnn.kb.us-west1.gcp.cloud.es.io

Edit : Nope just noticed a few of the new GCP regions also have the new

elastic-cloud.com