Creates a new page for EIS Region and hosting content

explore-analyze/elastic-inference/connect-self-managed-cluster-to-eis.md

@@ -180,6 +180,6 @@ For these models, you only need to create new {{infer}} endpoints if you want to
 
 ## Regions and billing
 
-For information about EIS regions and request routing, refer to [Region and hosting](/explore-analyze/elastic-inference/eis-supported-models.md#eis-regions).
+For information about EIS regions and request routing, refer to [Region and hosting](eis-region-and-hosting.md).
 
 EIS is billed per million tokens and consumes ECUs. For details on pricing and usage tracking, refer to [Pricing](/explore-analyze/elastic-inference/eis-supported-models.md#pricing) and [Monitor your token usage](/explore-analyze/elastic-inference/eis-supported-models.md#monitor-your-token-usage).

explore-analyze/elastic-inference/eis-region-and-hosting.md

@@ -0,0 +1,25 @@
+---
+navigation_title: Region and hosting
+applies_to:
+  stack: ga
+  serverless: ga
+description: Learn which regions host Elastic Inference Service (EIS) and how inference requests are routed.
+---
+
+# Region and hosting [eis-regions]
+
+Elastic {{infer-cap}} Service is currently available in these regions:
+
+**AWS:**
+
+* `us-east-1` (Virginia)
+
+**GCP:**
+
+* `asia-southeast1` (Singapore)
+* `europe-west1` (Belgium)
+* `us-east4` (Virginia)
+
+All {{infer}} requests sent through EIS are routed to the nearest region, regardless of where your {{es}} deployment or {{serverless-short}} project is hosted.
+
+Depending on the model being used, request processing may involve Elastic {{infer}} infrastructure and, in some cases, trusted third-party model providers. For example, ELSER and Jina requests are processed entirely within Elastic {{infer}} infrastructure. Other models, such as large language models or third-party embedding models, may involve additional processing by their respective model providers, which can operate in different cloud platforms or regions.

explore-analyze/elastic-inference/eis-supported-models.md

@@ -20,6 +20,8 @@ The corresponding {{kib}} connectors and {{infer}} endpoints for these models ar
 The **{{infer-cap}} Regions** column shows the regions where {{infer}} requests are processed and where data is sent.
 ::::
 
+For region availability and request routing, refer to [Region and hosting](eis-region-and-hosting.md).
+
 ### LLM chat models
 
 :::{csv-include} chat-models.csv
@@ -46,23 +48,7 @@ The **{{infer-cap}} Regions** column shows the regions where {{infer}} requests
 * Elastic makes every effort to use third party providers who do not use inputs to train models, and do not retain any data (zero data retention). Browse the tables on this page to double-check the status of a specific model.
 ::::
 
-## Region and hosting [eis-regions]
-
-Elastic {{infer-cap}} Service is currently available in these regions:
-
-**AWS:**
-
-* `us-east-1` (Virginia)
-
-**GCP:**
-
-* `asia-southeast1` (Singapore)
-* `europe-west1` (Belgium)
-* `us-east4` (Virginia)
-
-All {{infer}} requests sent through EIS are routed to the nearest region, regardless of where your {{es}} deployment or {{serverless-short}} project is hosted.
 
-Depending on the model being used, request processing may involve Elastic {{infer}} infrastructure and, in some cases, trusted third-party model providers. For example, ELSER and Jina requests are processed entirely within Elastic {{infer}} infrastructure. Other models, such as large language models or third-party embedding models, may involve additional processing by their respective model providers, which can operate in different cloud platforms or regions.
 
 ## Rate limits
 

explore-analyze/toc.yml

@@ -44,6 +44,7 @@ toc:
       - file: elastic-inference/eis.md
         children:
           - file: elastic-inference/eis-supported-models.md
+          - file: elastic-inference/eis-region-and-hosting.md
           - file: elastic-inference/connect-self-managed-cluster-to-eis.md
           - hidden: elastic-inference/ml-node-vs-eis.md
       - file: elastic-inference/external.md

redirects.yml

@@ -874,6 +874,12 @@ redirects:
       - to: 'explore-analyze/elastic-inference/eis-supported-models.md'
         anchors:
           'supported-models': 
+  'explore-analyze/elastic-inference/eis-supported-models.md':
+    to: 'explore-analyze/elastic-inference/eis-supported-models.md'
+    many:
+      - to: 'explore-analyze/elastic-inference/eis-region-and-hosting.md'
+        anchors:
+          'eis-regions': 'eis-regions'
 # Split off links to inference UI pages
   'explore-analyze/elastic-inference/inference-api.md':
     to: 'explore-analyze/elastic-inference/inference-api.md'