Skip to content

Commit

Permalink
Merge branch 'main' into logs-explorer-removal
Browse files Browse the repository at this point in the history
  • Loading branch information
mdbirnstiehl committed Mar 7, 2025
2 parents 073bdde + 2ceed53 commit f7d9d08
Show file tree
Hide file tree
Showing 532 changed files with 3,475 additions and 3,672 deletions.
5 changes: 5 additions & 0 deletions 404.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
layout: not-found
---

# Page not found
10 changes: 1 addition & 9 deletions deploy-manage/api-keys.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
---
applies_to:
stack: ga
deployment:
eck: ga
ess: ga
Expand All @@ -9,14 +8,7 @@ applies_to:
serverless: ga
---

# Manage API keys

% What needs to be done: Write from scratch

% GitHub issue: https://github.com/elastic/docs-projects/issues/349

% Scope notes: Elasticsearch & Kibana authentication API Keys

# API keys

API keys are security mechanisms used to authenticate and authorize access to your deployments and {{es}} resources.

Expand Down
4 changes: 2 additions & 2 deletions deploy-manage/api-keys/serverless-project-api-keys.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ You can manage your keys in **{{project-settings}} → {{manage-app}} → {{api-

:::{image} ../../images/serverless-api-key-management.png
:alt: API keys UI
:class: screenshot
:screenshot:
:::


Expand All @@ -26,7 +26,7 @@ In **{{api-keys-app}}**, click **Create API key**:

:::{image} ../../images/serverless-create-personal-api-key.png
:alt: Create API key UI
:class: screenshot
:screenshot:
:width: 50%
:::

Expand Down
84 changes: 34 additions & 50 deletions deploy-manage/autoscaling.md
Original file line number Diff line number Diff line change
@@ -1,70 +1,54 @@
---
mapped_urls:
- https://www.elastic.co/guide/en/cloud-heroku/current/ech-autoscaling.html
- https://www.elastic.co/guide/en/cloud/current/ec-autoscaling.html
- https://www.elastic.co/guide/en/cloud-enterprise/current/ece-autoscaling.html
- https://www.elastic.co/guide/en/elasticsearch/reference/current/xpack-autoscaling.html
applies_to:
deployment:
ece: ga
ess: ga
eck: ga
serverless: all
---

# Autoscaling

% What needs to be done: Refine
The autoscaling feature adjusts resources based on demand. A deployment can use autoscaling to scale resources as needed, ensuring sufficient capacity to meet workload requirements. In {{ece}}, {{eck}}, and {{ech}} deployments, autoscaling follows predefined policies, while in {{serverless-short}}, it is fully managed and automatic.

% GitHub issue: https://github.com/elastic/docs-projects/issues/344
:::{{tip}} - Serverless handles autoscaling for you
By default, {{serverless-full}} automatically scales your {{es}} resources based on your usage. You don't need to enable autoscaling.
:::

% Scope notes: Creating a new landing page and subheadings/pages for different deployment types. Merge content when appropriate
## Cluster autoscaling

% Use migrated content from existing pages that map to this page:
::::{admonition} Indirect use only
This feature is designed for indirect use by {{ech}}, {{ece}}, and {{eck}}. Direct use is not supported.
::::

% - [ ] ./raw-migrated-files/cloud/cloud-heroku/ech-autoscaling.md
% Notes: 1 child
% - [ ] ./raw-migrated-files/cloud/cloud/ec-autoscaling.md
% Notes: 2 children
% - [ ] ./raw-migrated-files/cloud/cloud-enterprise/ece-autoscaling.md
% Notes: 2 children
% - [ ] ./raw-migrated-files/elasticsearch/elasticsearch-reference/xpack-autoscaling.md
Cluster autoscaling allows an operator to create tiers of nodes that monitor themselves and determine if scaling is needed based on an operator-defined policy. An Elasticsearch cluster can use the autoscaling API to report when additional resources are required. For example, an operator can define a policy that scales a warm tier based on available disk space. Elasticsearch monitors disk space in the warm tier. If it predicts low disk space for current and future shard copies, the autoscaling API reports that the cluster needs to scale. It remains the responsibility of the operator to add the additional resources that the cluster signals it requires.

% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
A policy is composed of a list of roles and a list of deciders. The policy governs the nodes matching the roles. The deciders provide independent estimates of the capacity required. See [Autoscaling deciders](../deploy-manage/autoscaling/autoscaling-deciders.md) for details on available deciders.

$$$ec-autoscaling-intro$$$
Cluster autoscaling supports:
* Scaling machine learning nodes up and down.
* Scaling data nodes up based on storage.

$$$ec-autoscaling-factors$$$
## Trained model autoscaling

$$$ec-autoscaling-notifications$$$
:::{admonition} Trained model auto-scaling for self-managed deployments
The available resources of self-managed deployments are static, so trained model autoscaling is not applicable. However, available resources are still segmented based on the settings described in this section.
:::

$$$ec-autoscaling-restrictions$$$
Trained model autoscaling automatically adjusts the resources allocated to trained model deployments based on demand. This feature is available on all cloud deployments (ECE, ECK, ECH) and {{serverless-short}}. See [Trained model autoscaling](/deploy-manage/autoscaling/trained-model-autoscaling.md) for details.

$$$ec-autoscaling-enable$$$
Trained model autoscaling supports:
* Scaling trained model deployments

$$$ec-autoscaling-update$$$
::::{note}
Autoscaling is not supported on Debian 8.
::::

$$$ece-autoscaling-intro$$$
Find instructions on setting up and managing autoscaling, including supported environments, configuration options, and examples:

$$$ece-autoscaling-factors$$$

$$$ece-autoscaling-notifications$$$

$$$ece-autoscaling-restrictions$$$

$$$ece-autoscaling-enable$$$

$$$ece-autoscaling-update$$$

$$$ech-autoscaling-intro$$$

$$$ech-autoscaling-factors$$$

$$$ech-autoscaling-notifications$$$

$$$ech-autoscaling-restrictions$$$

$$$ech-autoscaling-enable$$$

$$$ech-autoscaling-update$$$

**This page is a work in progress.** The documentation team is working to combine content pulled from the following pages:

* [/raw-migrated-files/cloud/cloud-heroku/ech-autoscaling.md](/raw-migrated-files/cloud/cloud-heroku/ech-autoscaling.md)
* [/raw-migrated-files/cloud/cloud/ec-autoscaling.md](/raw-migrated-files/cloud/cloud/ec-autoscaling.md)
* [/raw-migrated-files/cloud/cloud-enterprise/ece-autoscaling.md](/raw-migrated-files/cloud/cloud-enterprise/ece-autoscaling.md)
* [/raw-migrated-files/elasticsearch/elasticsearch-reference/xpack-autoscaling.md](/raw-migrated-files/elasticsearch/elasticsearch-reference/xpack-autoscaling.md)
* [Autoscaling in {{ece}} and {{ech}}](/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md)
* [Autoscaling in {{eck}}](/deploy-manage/autoscaling/autoscaling-in-eck.md)
* [Autoscaling deciders](/deploy-manage/autoscaling/autoscaling-deciders.md)
* [Trained model autoscaling](/deploy-manage/autoscaling/trained-model-autoscaling.md)
Loading

0 comments on commit f7d9d08

Please sign in to comment.