Merge branch 'main' into ga/rescore_vector

Author: benwtrent

.github/workflows/add-new-team-label.yml

@@ -0,0 +1,18 @@
+name: "Label new issues with needs-team"
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  add-needs-triage-label:
+    name: Add `needs-team` label
+    runs-on: ubuntu-latest
+    steps:
+      - name: Add the needs-team label
+        uses: actions-ecosystem/action-add-labels@v1
+        with:
+          labels: |
+            needs-team
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/add-to-board.yml

@@ -0,0 +1,43 @@
+name: Triage & route issues
+
+on:
+  issues:
+    types: [labeled]
+
+permissions:
+  issues: write
+  contents: read
+
+jobs:
+  route:
+    runs-on: ubuntu-latest
+    if: |
+      github.event.label.name == 'team:DocsEng' ||
+      github.event.label.name == 'team:Obs' ||
+      github.event.label.name == 'team:Platform' ||
+      github.event.label.name == 'team:Projects' ||
+      github.event.label.name == 'team:Search' ||
+      github.event.label.name == 'team:Security'
+    env:
+      PROJECT_ID_MAP: |
+        {
+          "team:DocsEng":   "1625",
+          "team:Obs":       "649",
+          "team:Platform":  "1232",
+          "team:Projects":  "1415",
+          "team:Search":    "726",
+          "team:Security":  "1034"
+        }
+    steps:
+      - name: Remove needs-team label
+        uses: actions-ecosystem/action-remove-labels@v1
+        with:
+          labels: needs-team
+
+      - name: Add issue to the right project
+        uses: actions/add-to-project@244f685bbc3b7adfa8466e08b698b5577571133e
+        with:
+          project-url: https://github.com/orgs/elastic/projects/${{ fromJson(env.PROJECT_ID_MAP)[github.event.label.name] }}
+          github-token: ${{ secrets.ADD_TO_BOARD_TOKEN }}
+          labeled: ${{ github.event.label.name }}
+          label-operator: OR

README.md

@@ -6,7 +6,7 @@ This repo contains source files for Elastic documentation.
 
 ## Contribute
 
-If you find any bugs in our documentation, or want to request an enhancement, please [open an issue](https://github.com/elastic/docs-content/issues). We also welcome contributions in the form of PRs. Before you submit a PR, make sure that you have signed our [Contributor License Agreement](https://www.elastic.co/contributor-agreement/).
+If you find any bugs in our documentation, or want to request an enhancement, [open an issue](https://github.com/elastic/docs-content/issues). We also welcome contributions in the form of PRs. Before you submit a PR, make sure that you have signed our [Contributor License Agreement](https://www.elastic.co/contributor-agreement/).
 
 We write our docs in markdown. See our [syntax guide](https://elastic.github.io/docs-builder/syntax/index.html) for examples and additional functionality.
 

archive.md

@@ -1,6 +1,6 @@
 ---
 layout: archive
-description: Browse the archived documentation for older Elastic product releases. Archived documentation is unmaintained and may be out-of-date.
+description: Browse the archive for legacy Elastic products and documentation. Archive documentation is unmaintained and may be out-of-date.
 ---
 
 # Documentation archive

deploy-manage/_snippets/ecloud-security.md

@@ -0,0 +1,11 @@
+{{ecloud}} has built-in security. For example, HTTPS communications between {{ecloud}} and the internet, as well as inter-node communications, are secured automatically, and cluster data is encrypted at rest.
+
+In {{ech}}, you can augment these security features in the following ways:
+* Configure [traffic filtering](/deploy-manage/security/traffic-filtering.md) to prevent unauthorized access to your deployments.
+* Encrypt your deployment with a [customer-managed encryption key](/deploy-manage/security/encrypt-deployment-with-customer-managed-encryption-key.md).
+* [Secure your settings](/deploy-manage/security/secure-settings.md) using {{es}} and {{kib}} keystores.
+* Use the list of [{{ecloud}} static IPs](/deploy-manage/security/elastic-cloud-static-ips.md) to allow or restrict communications in your infrastructure.
+
+{{ech}} doesn't support custom SSL certificates, which means that a custom CNAME for an {{ech}} endpoint such as *mycluster.mycompanyname.com* also is not supported.
+
+Refer to [{{ecloud}} security](https://www.elastic.co/cloud/security) for more details about Elastic security and privacy programs.

deploy-manage/api-keys/elasticsearch-api-keys.md

@@ -40,7 +40,7 @@ Refer to the [Create API key](https://www.elastic.co/docs/api/doc/elasticsearch/
 Refer to the [Create cross-cluster API key](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-create-cross-cluster-api-key) documentation to learn more about creating cross-cluster API keys.
 
 
-## Update an API key [udpate-api-key]
+## Update an API key [update-api-key]
 
 To update an API key, go to the **API Keys** management page using the navigation menu or the [global search field](../../explore-analyze/find-and-organize/find-apps-and-objects.md), and then click on the name of the key. You cannot update the name or the type of API key.
 

deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md

@@ -147,12 +147,11 @@ To help you better understand the available autoscaling settings, this example d
 
     1. Open the **Edit** page for your deployment to get the current and maximum size per zone of each {{es}} data tier. In this example, the hot data and content tier has the following settings:
 
-        |     |     |     |
-        | --- | --- | --- |
-        | **Current size per zone** | **Maximum size per zone** |  |
-        | 45GB storage | 1.41TB storage |  |
-        | 1GB RAM | 32GB RAM |  |
-        | Up to 2.5 vCPU | 5 vCPU |  |
+        | Current size per zone | Maximum size per zone |
+        | --- | --- |
+        | 45GB storage | 1.41TB storage |
+        | 1GB RAM | 32GB RAM |
+        | Up to 2.5 vCPU | 5 vCPU |
 
         The fault tolerance for the data tier is set to 2 availability zones.
 
@@ -166,11 +165,10 @@ To help you better understand the available autoscaling settings, this example d
 
     1. From the deployment **Edit** page you can check the minimum and maximum size of your deployment’s machine learning instances. In this example, the machine learning instance has the following settings:
 
-        |     |     |     |
-        | --- | --- | --- |
-        | **Minimum size per zone** | **Maximum size per zone** |  |
-        | 1GB RAM | 64GB RAM |  |
-        | 0.5 vCPU up to 8 vCPU | 32 vCPU |  |
+        | Minimum size per zone | Maximum size per zone |
+        | --- | --- |
+        | 1GB RAM | 64GB RAM |
+        | 0.5 vCPU up to 8 vCPU | 32 vCPU |
 
         The fault tolerance for the machine learning instance is set to 1 availability zone.
 

deploy-manage/autoscaling/autoscaling-in-eck.md

@@ -20,6 +20,14 @@ Configure autoscaling for {{es}} deployments in {{eck}}. Learn how to enable aut
 
 ECK can leverage the [autoscaling API](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-autoscaling) introduced in {{es}} 7.11 to adjust automatically the number of Pods and the allocated resources in a tier. Currently, autoscaling is supported for {{es}} [data tiers](/manage-data/lifecycle/data-tiers.md) and machine learning nodes.
 
+### Supported Resources for Autoscaling per Elasticsearch Tier
+
+| Tiers | Storage | Memory | CPU |
+| --- | ---| --- | --- |
+| Data Nodes (except Frozen) | Yes | Calculated proportionally to the required amount of storage | Calculated proportionally to the required amount of memory
+| Frozen Nodes | Yes | Yes | Calculated proportionally to the required amount of memory
+| Machine Learning | No | Yes | Calculated proportionally to the required amount of memory
+
 
 ### Enable autoscaling [k8s-enable]
 
@@ -47,7 +55,7 @@ kind: ElasticsearchAutoscaler
 metadata:
   name: autoscaling-sample
 spec:
-  ## The name of the {{es}} cluster to be scaled automatically.
+  ## The name of the Elasticsearch cluster to be scaled automatically.
   elasticsearchRef:
     name: elasticsearch-sample
   ## The autoscaling policies.
@@ -167,7 +175,7 @@ spec:
           max: 512Gi
 ```
 
-You can find [a complete example in the ECK GitHub repository](https://github.com/elastic/cloud-on-k8s/blob/2.16/config/recipes/autoscaling/elasticsearch.yaml) which will also show you how to fine-tune the [autoscaling deciders](/deploy-manage/autoscaling/autoscaling-deciders.md).
+You can find [a complete example in the ECK GitHub repository](https://github.com/elastic/cloud-on-k8s/blob/{{eck_release_branch}}/config/recipes/autoscaling/elasticsearch.yaml) which will also show you how to fine-tune the [autoscaling deciders](/deploy-manage/autoscaling/autoscaling-deciders.md).
 
 
 #### Change the polling interval [k8s-autoscaling-polling-interval]
@@ -301,7 +309,7 @@ You should adjust those settings manually to match the size of your deployment w
 
 ## Autoscaling stateless applications on ECK [k8s-stateless-autoscaling]
 
-::::{note} 
+::::{note}
 This section only applies to stateless applications. Check [{{es}} autoscaling](#k8s-autoscaling) for more details about automatically scaling {{es}}.
 ::::
 
@@ -345,4 +353,4 @@ spec:
         target:
           type: Utilization
           averageUtilization: 50
-```
+```

deploy-manage/autoscaling/trained-model-autoscaling.md

@@ -37,7 +37,7 @@ $$$nlp-model-adaptive-resources$$$
 
 Model allocations are independent units of work for NLP tasks. If you set the numbers of threads and allocations for a model manually, they remain constant even when not all the available resources are fully used or when the load on the model requires more resources. Instead of setting the number of allocations manually, you can enable adaptive allocations to set the number of allocations based on the load on the process. This can help you to manage performance and cost more easily. (Refer to the [pricing calculator](https://cloud.elastic.co/pricing) to learn more about the possible costs.)
 
-When adaptive allocations are enabled, the number of allocations of the model is set automatically based on the current load. When the load is high, a new model allocation is automatically created. When the load is low, a model allocation is automatically removed. You can explicitely set the minimum and maximum number of allocations; autoscaling will occur within these limits.
+When adaptive allocations are enabled, the number of allocations of the model is set automatically based on the current load. When the load is high, a new model allocation is automatically created. When the load is low, a model allocation is automatically removed. You can explicitly set the minimum and maximum number of allocations; autoscaling will occur within these limits.
 
 ::::{note}
 If you set the minimum number of allocations to 1, you will be charged even if the system is not using those resources.
@@ -68,7 +68,7 @@ You can enable adaptive resources for your models when starting or updating the
 
 You can choose from three levels of resource usage for your trained model deployment; autoscaling will occur within the selected level’s range.
 
-Refer to the tables in the [Model deployment resource matrix](#model-deployment-resource-matrix) section to find out the setings for the level you selected.
+Refer to the tables in the [Model deployment resource matrix](#model-deployment-resource-matrix) section to find out the settings for the level you selected.
 
 :::{image} /deploy-manage/images/machine-learning-ml-nlp-deployment-id-elser-v2.png
 :alt: ELSER deployment with adaptive resources enabled.

deploy-manage/cloud-organization/billing/billing-faq.md

@@ -69,7 +69,7 @@ $$$faq-payment$$$What are the available payment methods on {{ecloud}}?
 :   For month-to-month payments only credit cards are accepted. We also allow payments by bank transfer for annual subscriptions.
 
 $$$faq-contact$$$Who can I contact for more information?
-:   If you have any further questions about your credit card statement, billing, or receipts, please send an email to `[email protected]` or open a [Support case](../../../troubleshoot/index.md) using the *Billing issue* category.
+:   If you have any further questions about your credit card statement, billing, or receipts, send an email to `[email protected]` or open a [Support case](../../../troubleshoot/index.md) using the *Billing issue* category.
 
 $$$faq-charge$$$Why is my credit card charged?
 :   If you are on a monthly plan, the charge is a recurring fee for using {{ecloud}}. The fee is normally charged at the start of each month, but it can also be charged at other times during the month. If a charge is unsuccessful, we will try to charge your card again at a later date.
@@ -90,7 +90,7 @@ $$$faq-deleteaccount$$$How can I delete my {{ecloud}} account?
 :   To have your account removed, you can contact support through the {{ecloud}} [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) or use one of these [alternative contact methods](../../../troubleshoot/index.md). For details about our data erasure policy, check [Privacy Rights and Choices](https://www.elastic.co/legal/privacy-statement#privacy-rights-and-choices?page=docs&placement=docs-body) in our General Privacy Statement.
 
 $$$faq-refund$$$Can I get a refund?
-:   Charges are non-refundable, but once you delete a deployment we’ll stop charging you for that deployment immediately. You only pay for what you use and you can stop using the service at any time. For any special considerations warranting a potential refund, please use the {{ecloud}} Console [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) to open a support case and select *Billing issue* as the category. To ensure quick processing, be sure to provide detail about the reasons for the refund request as well as other matters pertaining to the issue. For other ways to open a Support case, check [Contact us](../../../troubleshoot/index.md).
+:   Charges are non-refundable, but once you delete a deployment we’ll stop charging you for that deployment immediately. You only pay for what you use and you can stop using the service at any time. For any special considerations warranting a potential refund, use the {{ecloud}} Console [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) to open a support case and select *Billing issue* as the category. To ensure quick processing, be sure to provide detail about the reasons for the refund request as well as other matters pertaining to the issue. For other ways to open a Support case, check [Contact us](../../../troubleshoot/index.md).
 
 $$$faq-included$$$What is included in my paid {{ech}} deployment?
 :   All subscription tiers for {{ech}} include the following free allowance: