Skip to content

ECE links to current updated and fixed #1988

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 2, 2025
Merged

ECE links to current updated and fixed #1988

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a40a11b
ECE links to current updated and fixed
eedugon Jul 1, 2025
ff9beab
Merge branch 'main' into ece_current_links
eedugon Jul 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ Currently, autoscaling behavior is as follows:
* **Data tiers**

* Each {{es}} [data tier](../../manage-data/lifecycle/data-tiers.md) scales upward based on the amount of available storage. When we detect more storage is needed, autoscaling will scale up each data tier independently to ensure you can continue and ingest more data to your hot and content tier, or move data to the warm, cold, or frozen data tiers.
* In addition to scaling up existing data tiers, a new data tier will be automatically added when necessary, based on your [index lifecycle management policies](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-index-management.html).
* In addition to scaling up existing data tiers, a new data tier will be automatically added when necessary, based on your [index lifecycle management policies](/manage-data/lifecycle/index-lifecycle-management.md).
* To control the maximum size of each data tier and ensure it will not scale above a certain size, you can use the maximum size per zone field.
* Autoscaling based on memory or CPU, as well as autoscaling downward, is not currently supported. In case you want to adjust the size of your data tier to add more memory or CPU, or in case you deleted data and want to scale it down, you can set the current size per zone of each data tier manually.

Expand Down
5 changes: 4 additions & 1 deletion deploy-manage/deploy/cloud-enterprise/ece-configure-templates-index-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,11 @@ In a template that creates a hot-warm architecture, you can use index curation t

Configuring index management is part of the larger task of [creating deployment templates](ece-configuring-ece-create-templates.md) or editing them. The choices you make here determine which index management methods are available to your users when they create deployments.

You should configure all index management methods that you want your users to be able to choose from when they create their deployments from your template. You can configure index curation, index lifecycle management, or both. If you are not sure which index management methods to configure, take a look at how your users are asked to [configure index management](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-index-management.html) when they customize their deployments.
You should configure all index management methods that you want your users to be able to choose from when they create their deployments from your template. You can configure index curation, index lifecycle management, or both.

::::{note}
Index curation has been deprecated in favor of [index lifecycle management](/manage-data/lifecycle/index-lifecycle-management.md). For {{stack}} version 6.7 and later, any deployments using index curation will be prompted to [migrate to ILM](/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md).
::::
Comment on lines +23 to +27
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The removed paragraph didn't have much sense, more over when index curation is deprecated and we should recommend against it.

I've added the note that can be felt a bit repetitive because in the beginning of the doc we already mention that index curation is deprecated (i think it's beneficial also to remind it just before describing both options).


## Steps [ece_steps_2]

Expand Down
2 changes: 1 addition & 1 deletion deploy-manage/deploy/cloud-enterprise/ece-integrations-server-api-example.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ For more information on how to manage Integrations Server from the UI, check [Ma

Integrations Server can be enabled only on new deployments, starting with {{stack}} version 8.0.

It’s possible to enable Integrations Server on an existing deployment with version 8.0 only if [APM & Fleet Server](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-apm-and-fleet.html) hasn’t been previously enabled on the deployment.
It’s possible to enable Integrations Server on an existing deployment with version 8.0 only if the legacy [APM & Fleet Server](https://www.elastic.co/guide/en/cloud-enterprise/3.8/ece-manage-apm-and-fleet.html) hasn’t been previously enabled on the deployment.


## API request example [ece_api_request_example_2]
Expand Down
2 changes: 1 addition & 1 deletion deploy-manage/deploy/cloud-enterprise/manage-elastic-stack-versions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ products:
New or updated versions of the {{stack}} must be prepared to work with {{ece}} and are provided as packs that you can download.

::::{important}
{{es}} 7.8 and later comes with Index Lifecycle Management (ILM) always enabled. Before upgrading to 7.8 or later, to avoid any unpredictable behavior it is important to configure hot-warm clusters on {{ece}} with ILM rather than index curation. Check [migrate to index lifecycle management](../../../manage-data/lifecycle/index-lifecycle-management.md) for existing clusters, and [configure index management](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-index-management.html) for new clusters.
{{es}} 7.8 and later comes with Index Lifecycle Management (ILM) always enabled. Before upgrading to 7.8 or later, to avoid any unpredictable behavior it is important to configure hot-warm clusters on {{ece}} with ILM rather than index curation. Check [migrate to index lifecycle management](/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md) for existing clusters, and [configure index management](/manage-data/lifecycle/index-lifecycle-management.md) for new clusters.
Copy link
Contributor Author

@eedugon eedugon Jul 1, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The links were switched here, the migrate link was linking to manage ILM and the configure ILM was linking to a non redirected page, which we have fixed.
Now migrate goes to migrate and configure index management goes to manage ILM.

::::


Expand Down
2 changes: 1 addition & 1 deletion ...anage/deploy/cloud-enterprise/switch-from-apm-to-integrations-server-payload.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ products:

# Switch from APM to Integrations Server payload [ece-integrations-server-apm-switch]

This example shows how to use the {{ece}} RESTful API to switch from using [APM & Fleet Server](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-manage-apm-and-fleet.html) to [Integrations Server](manage-integrations-server.md).
This example shows how to use the {{ece}} RESTful API to switch from using the legacy [APM & Fleet Server](https://www.elastic.co/guide/en/cloud-enterprise/3.8/ece-manage-apm-and-fleet.html) to [Integrations Server](manage-integrations-server.md).


## Requirements [ece_requirements_5]
Expand Down
2 changes: 2 additions & 0 deletions manage-data/lifecycle/index-lifecycle-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,8 @@ mapped_pages:
- https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html
- https://www.elastic.co/guide/en/elasticsearch/reference/current/overview-index-lifecycle-management.html
- https://www.elastic.co/guide/en/elasticsearch/reference/current/ilm-concepts.html
- https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-index-management.html
- https://www.elastic.co/guide/en/cloud/current/ec-configure-index-management.html
Comment on lines +6 to +7
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One of them was missing (ece), and I moved the EC one to this doc as it shouldn't be in the migrate doc.

applies_to:
stack: ga
products:
Expand Down
1 change: 0 additions & 1 deletion manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,6 @@
---
mapped_pages:
- https://www.elastic.co/guide/en/cloud-enterprise/current/ece-migrate-index-management.html
- https://www.elastic.co/guide/en/cloud/current/ec-configure-index-management.html
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This "migrate" doc should only have mapped pages of the ECE / EC original migrate docs, not the manage ILM docs.

- https://www.elastic.co/guide/en/cloud/current/ec-migrate-index-management.html
applies_to:
stack: ga
Expand Down
Loading