# Endpoint inconsistency in different regions of Elastic Cloud **URL:** \ **Category:** Elasticsearch\ **Created:** [May 17, 2021, 4:48pm UTC](https://discuss.elastic.co/t/endpoint-inconsistency-in-different-regions-of-elastic-cloud/273202 "2021-05-17T16:48:32Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Mkian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mkian/32/86705_2.png) [@Mkian](https://discuss.elastic.co/u/Mkian)\ **Post date:** [May 17, 2021, 4:48pm UTC](https://discuss.elastic.co/t/endpoint-inconsistency-in-different-regions-of-elastic-cloud/273202/1 "2021-05-17T16:48:32Z")
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 ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [May 17, 2021, 5:12pm UTC](https://discuss.elastic.co/t/endpoint-inconsistency-in-different-regions-of-elastic-cloud/273202/2 "2021-05-17T17:12:57Z")
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](https://bar.kb.us-east-2.aws.elastic-cloud.com:9243) ---
**Author:** ![Mkian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mkian/32/86705_2.png) [@Mkian](https://discuss.elastic.co/u/Mkian)\ **Post date:** [May 17, 2021, 8:39pm UTC](https://discuss.elastic.co/t/endpoint-inconsistency-in-different-regions-of-elastic-cloud/273202/3 "2021-05-17T20:39:52Z")
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` ---
**Author:** ![Mkian](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mkian/32/86705_2.png) [@Mkian](https://discuss.elastic.co/u/Mkian)\ **Post date:** [May 17, 2021, 9:25pm UTC](https://discuss.elastic.co/t/endpoint-inconsistency-in-different-regions-of-elastic-cloud/273202/4 "2021-05-17T21:25:16Z")
also fyi @stephenb , i just found a new format: `.eu-central-1.aws.cloud.es.io` ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [May 17, 2021, 9:58pm UTC](https://discuss.elastic.co/t/endpoint-inconsistency-in-different-regions-of-elastic-cloud/273202/5 "2021-05-17T21:58:43Z")
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 ``` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 14, 2021, 9:58pm UTC](https://discuss.elastic.co/t/endpoint-inconsistency-in-different-regions-of-elastic-cloud/273202/6 "2021-06-14T21:58:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.