Skip to content

Commit f291763

Browse files
Merge branch 'main' of github.com:elastic/docs-content into dm-security-cleanup
2 parents 0181c9f + df8d196 commit f291763

File tree

541 files changed

+3518
-3820
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

541 files changed

+3518
-3820
lines changed

404.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
layout: not-found
3+
---
4+
5+
# Page not found

deploy-manage/api-keys.md

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
---
22
applies_to:
3-
stack: ga
43
deployment:
54
eck: ga
65
ess: ga
@@ -9,14 +8,7 @@ applies_to:
98
serverless: ga
109
---
1110

12-
# Manage API keys
13-
14-
% What needs to be done: Write from scratch
15-
16-
% GitHub issue: https://github.com/elastic/docs-projects/issues/349
17-
18-
% Scope notes: Elasticsearch & Kibana authentication API Keys
19-
11+
# API keys
2012

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

deploy-manage/api-keys/serverless-project-api-keys.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ You can manage your keys in **{{project-settings}} → {{manage-app}} → {{api-
1616

1717
:::{image} ../../images/serverless-api-key-management.png
1818
:alt: API keys UI
19-
:class: screenshot
19+
:screenshot:
2020
:::
2121

2222

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

2727
:::{image} ../../images/serverless-create-personal-api-key.png
2828
:alt: Create API key UI
29-
:class: screenshot
29+
:screenshot:
3030
:width: 50%
3131
:::
3232

deploy-manage/autoscaling.md

Lines changed: 34 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -1,70 +1,54 @@
11
---
22
mapped_urls:
3-
- https://www.elastic.co/guide/en/cloud-heroku/current/ech-autoscaling.html
4-
- https://www.elastic.co/guide/en/cloud/current/ec-autoscaling.html
5-
- https://www.elastic.co/guide/en/cloud-enterprise/current/ece-autoscaling.html
63
- https://www.elastic.co/guide/en/elasticsearch/reference/current/xpack-autoscaling.html
4+
applies_to:
5+
deployment:
6+
ece: ga
7+
ess: ga
8+
eck: ga
9+
serverless: all
710
---
811

912
# Autoscaling
1013

11-
% What needs to be done: Refine
14+
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.
1215

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

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

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

19-
% - [ ] ./raw-migrated-files/cloud/cloud-heroku/ech-autoscaling.md
20-
% Notes: 1 child
21-
% - [ ] ./raw-migrated-files/cloud/cloud/ec-autoscaling.md
22-
% Notes: 2 children
23-
% - [ ] ./raw-migrated-files/cloud/cloud-enterprise/ece-autoscaling.md
24-
% Notes: 2 children
25-
% - [ ] ./raw-migrated-files/elasticsearch/elasticsearch-reference/xpack-autoscaling.md
26+
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.
2627

27-
% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
28+
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.
2829

29-
$$$ec-autoscaling-intro$$$
30+
Cluster autoscaling supports:
31+
* Scaling machine learning nodes up and down.
32+
* Scaling data nodes up based on storage.
3033

31-
$$$ec-autoscaling-factors$$$
34+
## Trained model autoscaling
3235

33-
$$$ec-autoscaling-notifications$$$
36+
:::{admonition} Trained model auto-scaling for self-managed deployments
37+
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.
38+
:::
3439

35-
$$$ec-autoscaling-restrictions$$$
40+
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.
3641

37-
$$$ec-autoscaling-enable$$$
42+
Trained model autoscaling supports:
43+
* Scaling trained model deployments
3844

39-
$$$ec-autoscaling-update$$$
45+
::::{note}
46+
Autoscaling is not supported on Debian 8.
47+
::::
4048

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

43-
$$$ece-autoscaling-factors$$$
44-
45-
$$$ece-autoscaling-notifications$$$
46-
47-
$$$ece-autoscaling-restrictions$$$
48-
49-
$$$ece-autoscaling-enable$$$
50-
51-
$$$ece-autoscaling-update$$$
52-
53-
$$$ech-autoscaling-intro$$$
54-
55-
$$$ech-autoscaling-factors$$$
56-
57-
$$$ech-autoscaling-notifications$$$
58-
59-
$$$ech-autoscaling-restrictions$$$
60-
61-
$$$ech-autoscaling-enable$$$
62-
63-
$$$ech-autoscaling-update$$$
64-
65-
**This page is a work in progress.** The documentation team is working to combine content pulled from the following pages:
66-
67-
* [/raw-migrated-files/cloud/cloud-heroku/ech-autoscaling.md](/raw-migrated-files/cloud/cloud-heroku/ech-autoscaling.md)
68-
* [/raw-migrated-files/cloud/cloud/ec-autoscaling.md](/raw-migrated-files/cloud/cloud/ec-autoscaling.md)
69-
* [/raw-migrated-files/cloud/cloud-enterprise/ece-autoscaling.md](/raw-migrated-files/cloud/cloud-enterprise/ece-autoscaling.md)
70-
* [/raw-migrated-files/elasticsearch/elasticsearch-reference/xpack-autoscaling.md](/raw-migrated-files/elasticsearch/elasticsearch-reference/xpack-autoscaling.md)
51+
* [Autoscaling in {{ece}} and {{ech}}](/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md)
52+
* [Autoscaling in {{eck}}](/deploy-manage/autoscaling/autoscaling-in-eck.md)
53+
* [Autoscaling deciders](/deploy-manage/autoscaling/autoscaling-deciders.md)
54+
* [Trained model autoscaling](/deploy-manage/autoscaling/trained-model-autoscaling.md)

0 commit comments

Comments
 (0)