Merge branch 'main' into alerting/experimental-overview

Author: nastasha-solomon

deploy-manage/_snippets/cc-license-and-payment.md

@@ -2,4 +2,4 @@ Each cloud connected service has its own licensing and payment requirements.
 
 * AutoOps for ECE, ECK, and self-managed clusters is available for free across all [self-managed license types](https://www.elastic.co/subscriptions). It does not consume ECUs.
 
-* The Elastic {{infer-cap}} Service (EIS) for ECE, ECK, and self-managed clusters requires a [self-managed Enterprise license](https://www.elastic.co/subscriptions) or a self-managed free trial. Note that [EIS pricing](/explore-analyze/elastic-inference/eis-supported-models.md#pricing) is usage-based. Using EIS consumes ECUs.
+* The Elastic {{infer-cap}} Service (EIS) for ECE, ECK, and self-managed clusters requires a [self-managed Enterprise license](https://www.elastic.co/subscriptions) or a self-managed free trial. Note that [EIS pricing](/explore-analyze/elastic-inference/eis.md#pricing) is usage-based. Using EIS consumes ECUs.

deploy-manage/deploy/_snippets/trial-limitations.md

@@ -3,7 +3,7 @@ During the free 14-day trial, Elastic provides access to one hosted deployment a
 **Hosted deployments**
 
 * You can only have one active deployment at a time.
-* The deployment size is limited to 8 GB RAM. The available storage depends on the selected hardware profile, cloud provider, and region. To compare profile trade-offs, refer to [Hardware profiles](/deploy-manage/deploy/elastic-cloud/ec-change-hardware-profile.md).
+* The deployment size is limited to 4 GB RAM per availability zone for {{es}} data nodes, up to 2 availability zones (8 GB total). The available storage depends on the selected hardware profile, cloud provider, and region. To compare profile trade-offs, refer to [Hardware profiles](/deploy-manage/deploy/elastic-cloud/ec-change-hardware-profile.md).
 * Storage in a trial deployment is not a fixed value and can vary significantly even with the same RAM allocation. For example, vector search-optimized profiles generally provide less storage than more storage-dense profile options.
 * {{ml-cap}} nodes are available up to 4GB RAM, or up to 8GB when using Reranker.
 * Custom {{es}} plugins are not enabled.

deploy-manage/deploy/cloud-enterprise/identify-deployment-scenario.md

@@ -34,14 +34,13 @@ You can proceed with this scenario and [install ECE](./install.md).
 
 This type of deployment is recommended for many production setups. You need:
 
-* 3 hosts with at least 32 GB RAM each for directors and coordinators (ECE management services)
+* 3 hosts with at least 32 GB RAM each for directors and coordinators (ECE management services), and proxies.
 * 3 hosts for allocators, each with one of the following RAM configurations:
 
     * 1 x 256 GB RAM
     * 2 x 128 GB RAM
     * 4 x 64 GB RAM
 
-* 3 hosts with 16 GB RAM each for proxies
 * 3 availability zones
 
 :::{image} /deploy-manage/images/cloud-enterprise-ece-pb-6.png
@@ -73,4 +72,4 @@ This type of deployment is recommended for deployments with significant overall
 
 Note that the large-sized {{ece}} installation separates the allocator and proxy roles from the director and coordinator roles (ECE management services).
 
-You can proceed with this scenario and [install ECE](./install.md).
+You can proceed with this scenario and [install ECE](./install.md).

deploy-manage/deploy/elastic-cloud/create-an-organization.md

@@ -37,7 +37,7 @@ Your free 14-day trial includes:
 
 **One hosted deployment**
 
-A deployment lets you explore Elastic solutions for Search, Observability, and Security. Trial deployments run on the latest version of the {{stack}}. They include 8 GB of RAM spread out over two availability zones, and storage capacity based on the selected hardware profile. If you’re looking to evaluate a smaller workload, you can scale down your trial deployment. Each deployment includes Elastic features such as Maps, SIEM, machine learning, advanced security, and much more. You have some sample data sets to play with and tutorials that describe how to add your own data.
+A deployment lets you explore Elastic solutions for Search, Observability, and Security. Trial deployments run on the latest version of the {{stack}}. They include two 4 GB RAM instances, one per availability zone, and storage capacity based on the selected hardware profile. If you’re looking to evaluate a smaller workload, you can scale down your trial deployment. Each deployment includes Elastic features such as Maps, SIEM, {{ml}}, advanced security, and much more. You have some sample data sets to play with and tutorials that describe how to add your own data.
 
 For more information, check the [{{ech}} documentation](cloud-hosted.md).
 

deploy-manage/security/elastic-cloud-static-ips.md

@@ -14,6 +14,9 @@ products:
 
 Static IP addresses are [subject to change](#ec-warning), and not all [cloud provider regions](#ec-regions) are currently fully supported for ingress and egress static IPs. For this reason, we generally do not recommend that you use firewall rules to allow or restrict certain IP ranges. Consider using [private connectivity](/deploy-manage/security/private-connectivity.md) for deployment endpoints on {{ech}}. However, in situations where using private connectivity services do not meet requirements (for example, secure traffic **from** {{ecloud}}), static IP ranges can be used.
 
+:::{admonition} Not available on Serverless
+Static IP addresses are not available for {{serverless-full}} projects.
+:::
 
 ## Ingress Static IPs: Traffic to {{ecloud}} [ec-ingress] 
 

explore-analyze/ai-features.md

@@ -53,18 +53,17 @@ This general-purpose API enables you to perform {{infer}} operations using EIS,
 
 Natural Language Processing (NLP) enables you to analyze natural language data and make predictions.  Elastic offers a range of [built-in NLP models](/explore-analyze/machine-learning/nlp/ml-nlp-built-in-models.md) such as the Elastic-trained [ELSER](/explore-analyze/machine-learning/nlp/ml-nlp-elser.md) or [Jina models](/explore-analyze/machine-learning/nlp/ml-nlp-jina.md). You can also [deploy custom NLP models](/explore-analyze/machine-learning/nlp/ml-nlp-overview.md).
 
-### AI-powered search
+### Vector search
 
-[AI-powered search](/solutions/search/ai-search/ai-search.md) helps you find data based on intent and contextual meaning using vector search technology, which uses {{ml}} models to capture meaning in content.
+[Vector search](/solutions/search/vector.md) uses embeddings and similarity matching to find related data in {{es}}. {{ml-cap}} models convert text, images, and other content into vectors. Use cases include recommendations, duplicate detection, fraud and anomaly detection, image similarity, and semantic search.
 
-#### Semantic and hybrid search
+For direct control over embeddings, field types, and queries, implement dense or sparse vector search with [`dense_vector`](https://www.elastic.co/docs/solutions/search/vector/dense-vector) and [`sparse_vector`](https://www.elastic.co/docs/solutions/search/vector/sparse-vector) field types. Refer to [Vector search in {{es}}](/solutions/search/vector.md) for concepts, field types, and tutorials.
 
-Depending on your team's technical expertise and requirements, you can choose from two broad paths for implementing semantic search:
+#### Semantic and hybrid search
 
-- For a minimal configuration, managed workflow use [semantic_text](https://www.elastic.co/docs/solutions/search/semantic-search/semantic-search-semantic-text).
-- For more control over the implementation details, implement dense or sparse [vector search](https://www.elastic.co/docs/solutions/search/vector) manually.
+When you want a managed workflow for text—embedding generation, field mapping, and similarity retrieval, use the [semantic search](/solutions/search/semantic-search.md) workflow. Start with the [`semantic_text`](https://www.elastic.co/docs/solutions/search/semantic-search/semantic-search-semantic-text) field type for the simplest setup.
 
-[Hybrid search](/solutions/search/hybrid-search.md) combines traditional full-text search with AI-powered search for more powerful search experiences that serve a wider range of user needs.
+[Hybrid search](/solutions/search/hybrid-search.md) combines full-text search with vector search in one request so results can match both exact terms and meaning.
 
 ### Semantic re-ranking
 

explore-analyze/ai-features/automatic-import.md

@@ -106,7 +106,13 @@ The integration creation flow changed in {{stack}} 9.4 to support multiple data
    - UDP
 
 8. Under **Logs**, either upload a sample of your data or select an existing index. Only indexes that include the `event.original` field are supported. Make sure your sample includes all the types of events that you want the integration to handle.
-9. Click **Analyze logs** and wait for processing to complete. This can take several minutes. The data stream(s) continue to process as shown by the status on the **Manage my integrations** menu, so you can navigate away and come back later. Only integrations created after using versions 9.4+ appear here.
+9. Click **Analyze logs** and wait for processing to complete. This can take several minutes. The data stream(s) continue to process as shown by the status on the **Manage my integrations** menu, so you can navigate away and come back later.
+
+   :::{note}
+   The **Manage my integrations** menu lists only integrations created with Automatic Import on versions 9.4+. 
+   
+   Manually created custom integration `.zip`s  get installed from the **Installed integrations** tab and aren't tracked on the **Manage my integrations** menu. For more information about user-created custom integrations, refer to [Upload a new integration](https://www.elastic.co/docs/extend/integrations/upload-new-integration).
+   :::
 
    :::{image} /solutions/images/security-auto-import-data-streams-status.png
    :alt: The New Integration page showing multiple data streams with Analyzing and Success statuses

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).
+EIS is billed per million tokens and consumes ECUs. For details on pricing and usage tracking, refer to [Pricing](eis.md#pricing) and [Monitor your token usage](eis.md#monitor-your-token-usage).

explore-analyze/elastic-inference/eis-rate-limits.md

@@ -0,0 +1,25 @@
+---
+navigation_title: Rate limits
+applies_to:
+  stack: ga
+  serverless: ga
+description: Learn about rate limits for Elastic Inference Service (EIS) models.
+---
+
+# Rate limits [eis-rate-limits]
+
+This page lists the rate limits that apply to Elastic {{infer-cap}} Service (EIS) models.
+
+Exceeding a limit results in HTTP 429 responses from the server until the sliding window moves on further and parts of the limit resets.
+
+| Model                                             | Request/minute  | Tokens/minute (ingest)  | Tokens/minute (search)  | Notes                    |
+|---------------------------------------------------|-----------------|-------------------------|-------------------------|--------------------------|
+| Elastic Managed LLMs {applies_to}`stack: ga 9.3+` | 2000            | -                       | -                       | No rate limit on tokens  |
+| ELSER {applies_to}`stack: ga 9.0+`                | 6,000           | 6,000,000               | 600,000                 | Limits are applied to both requests per minute and tokens per minute, whichever limit is reached first.  |
+| Jina Embeddings v5 Nano {applies_to}`stack: ga 9.3+`   | 6,000           | 6,000,000               | 600,000                 | Limits are applied to both requests per minute and tokens per minute, whichever limit is reached first.  |
+| Jina Embeddings v5 Small {applies_to}`stack: ga 9.3+`   | 6,000           | 6,000,000               | 600,000                 | Limits are applied to both requests per minute and tokens per minute, whichever limit is reached first.  |
+| Jina Embeddings v3 {applies_to}`stack: ga 9.3+`   | 6,000           | 6,000,000               | 600,000                 | Limits are applied to both requests per minute and tokens per minute, whichever limit is reached first.  |
+| Jina Embeddings v5 (Small) {applies_to}`stack: ga 9.3+`   | 6,000           | 6,000,000               | 600,000                 | Limits are applied to both requests per minute and tokens per minute, whichever limit is reached first.  |
+| Jina Embeddings v5 (Nano) {applies_to}`stack: ga 9.3+`   | 6,000           | 6,000,000               | 600,000                 | Limits are applied to both requests per minute and tokens per minute, whichever limit is reached first.  |
+| Jina Reranker v2 {applies_to}`stack: ga 9.3+`     | 600             | -                       | 6,000,000               | Limits are applied to both requests per minute and tokens per minute, whichever limit is reached first.  |
+| Jina Reranker v3 {applies_to}`stack: ga 9.3+`     | 600             | -                       | 6,000,000               | Limits are applied to both requests per minute and tokens per minute, whichever limit is reached first.  |

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]
+
+This page lists the {{aws}} and {{gcp}} regions where Elastic {{infer-cap}} Service (EIS) is available and explains how {{infer}} requests are routed.
+
+**{{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.