Merge branch 'main' into autoscale-migration-344

Author: charlotte-hoblik

deploy-manage/toc.yml

@@ -827,5 +827,4 @@ toc:
     children:
       - file: uninstall/uninstall-elastic-cloud-enterprise.md
       - file: uninstall/uninstall-elastic-cloud-on-kubernetes.md
-      - file: uninstall/uninstall-a-self-managed-cluster.md
       - file: uninstall/delete-a-cloud-deployment.md

deploy-manage/uninstall.md

@@ -1,7 +1,29 @@
+---
+applies_to:
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
+  serverless:
+---
+
 # Uninstall
 
-% What needs to be done: Write from scratch
+Uninstalling Elastic components, such as {{es}} clusters, deployments, or orchestrators, may be necessary for several reasons. You might need to decommission a host, scale down a self-managed cluster, recover from an installation issue that can't be resolved, or start fresh with a clean setup.
+
+Different Elastic environments require different uninstallation steps. Choose the guide that matches your setup:
+
+* Uninstall an orchestrator:
+  * [Uninstall an {{ece}} host](/deploy-manage/uninstall/uninstall-elastic-cloud-enterprise.md)
+  * [Uninstall {{eck}} operator](/deploy-manage/uninstall/uninstall-elastic-cloud-on-kubernetes.md)
+
+* Delete an orchestrated deployment:
+  * [{{ech}} deployments](/deploy-manage/uninstall/delete-a-cloud-deployment.md#elastic-cloud-hosted)
+  * [Serverless projects](/deploy-manage/uninstall/delete-a-cloud-deployment.md#serverless)
+  * [{{ece}} deployments](/deploy-manage/uninstall/delete-a-cloud-deployment.md#ece)
 
-% GitHub issue: https://github.com/elastic/docs-projects/issues/362
+:::{note}
+You can uninstall {{es}} nodes or {{kib}} instances on self-managed clusters, but step-by-step instructions are not currently available. For more details on the implications of removing {{es}} nodes, refer to [](/deploy-manage/maintenance/add-and-remove-elasticsearch-nodes.md).
+:::
 
-⚠️ **This page is a work in progress.** ⚠️

deploy-manage/uninstall/delete-a-cloud-deployment.md

@@ -1,35 +1,85 @@
 ---
-mapped_urls:
-  - https://www.elastic.co/guide/en/cloud-heroku/current/ech-delete-deployment.html
-  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-delete-deployment.html
-  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-terminate-deployment.html
-  - https://www.elastic.co/guide/en/cloud/current/ec-delete-deployment.html
-  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-restore-deployment.html
-  - https://www.elastic.co/guide/en/cloud/current/ec-billing-stop.html
-  - https://www.elastic.co/guide/en/serverless/current/general-billing-stop-project.html
+navigation_title: "Delete a cloud deployment"
+applies_to:
+  deployment:
+    ess:
+    ece: 
+  serverless:
 ---
 
-# Delete a cloud deployment
+# Delete an Enterprise or Hosted deployment or a Serverless project
 
-% What needs to be done: Refine
+This page provides instructions for deleting several types of cloud deployments, and outlines key considerations before proceeding.
 
-% Use migrated content from existing pages that map to this page:
+## {{ech}} [elastic-cloud-hosted]
 
-% - [ ] ./raw-migrated-files/cloud/cloud-heroku/ech-delete-deployment.md
-% - [ ] ./raw-migrated-files/cloud/cloud-enterprise/ece-delete-deployment.md
-% - [ ] ./raw-migrated-files/cloud/cloud-enterprise/ece-terminate-deployment.md
-% - [ ] ./raw-migrated-files/cloud/cloud/ec-billing-stop.html
-% - [ ] ./raw-migrated-files/cloud/cloud/ec-delete-deployment.md
-% - [ ] ./raw-migrated-files/docs-content/serverless/general-billing-stop-project.html
-% - [ ] ./raw-migrated-files/cloud/cloud-enterprise/ece-restore-deployment.md
-%      Notes: if you need to restore a deleted deployment ...
+To delete an {{ech}} deployment: 
 
-⚠️ **This page is a work in progress.** ⚠️
+1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
+2. On the deployment overview page, select **Actions**, then select **Delete deployment** and confirm the deletion.
 
-The documentation team is working to combine content pulled from the following pages:
+When you delete your deployment, billing stops immediately, rounding up to the nearest hour.
+
+:::{{warning}}
+When deployments are deleted, we erase all data on disk, including snapshots. Snapshots are retained for very a limited amount of time post deletion and we cannot guarantee that deleted deployments can be restored from snapshots for this reason. If you accidentally delete a deployment, please contact support as soon as possible to increase the likelihood of restoring your deployment.
+:::
+
+:::{{tip}}
+If you want to keep the snapshot for future purposes even after the deployment deletion, you should [use a custom snapshot repository](/deploy-manage/tools/snapshot-and-restore/elastic-cloud-hosted.md).
+:::
+
+## Serverless
+
+To delete a {{serverless-full}} project:
+
+1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
+2. Find your project on the home page in the **Serverless Projects** card and select **Manage** to access it directly. Or, select **Serverless Projects** to go to the projects page to view all of your projects.
+3. Select **Actions**, then select **Delete project** and confirm the deletion.
+
+:::{warning}
+All data is lost. Billing for usage is by the hour and any outstanding charges for usage before you deleted the project will still appear on your next bill.
+:::
+
+## {{ece}}
+
+### Delete a deployment
+
+To delete an {{ece}} deployment:
+
+1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
+2. On the **Deployments** page, select your deployment.
+
+    Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
+
+3. Terminate the deployment.
+4. Select **Delete deployment** and follow the steps to delete the deployment permanently.
+
+:::{warning}
+Deleting a deployment cannot be undone.
+:::
+
+### Terminate a deployment
+
+Terminating a deployment stops all running instances and **deletes all data**. Only configuration information is saved so that you can restore the deployment in the future. If there is [a snapshot repository associated](/deploy-manage/tools/snapshot-and-restore/cloud-enterprise.md) with the Elasticsearch cluster and at least one snapshot has been taken, you can restore the cluster with the same indices later.
+
+To terminate an {{ece}} deployment,
+
+1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
+2. On the **Deployments** page, select your deployment.
+
+    Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
+
+3. In the **Deployment Management** section, select **Terminate deployment**.
+
+
+### Restore a deployment
+
+You can restore a deployment that was previously terminated to its original configuration. Note that the data that was in the deployment is not restored, since it is deleted as part of the termination process. If you have a snapshot, you can [restore it](/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md) to recover the {{es}} indices.
+
+To restore a terminated deployment,
+
+1. [Log into the Cloud UI](/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui.md).
+2. On the **Deployments** page, select your deployment.
+    Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
+3. In the **Deployment Management** section, select **Restore** and then acknowledge the confirmation message.
 
-* [/raw-migrated-files/cloud/cloud-heroku/ech-delete-deployment.md](/raw-migrated-files/cloud/cloud-heroku/ech-delete-deployment.md)
-* [/raw-migrated-files/cloud/cloud-enterprise/ece-delete-deployment.md](/raw-migrated-files/cloud/cloud-enterprise/ece-delete-deployment.md)
-* [/raw-migrated-files/cloud/cloud-enterprise/ece-terminate-deployment.md](/raw-migrated-files/cloud/cloud-enterprise/ece-terminate-deployment.md)
-* [/raw-migrated-files/cloud/cloud/ec-delete-deployment.md](/raw-migrated-files/cloud/cloud/ec-delete-deployment.md)
-* [/raw-migrated-files/cloud/cloud-enterprise/ece-restore-deployment.md](/raw-migrated-files/cloud/cloud-enterprise/ece-restore-deployment.md)

deploy-manage/uninstall/uninstall-a-self-managed-cluster.md

@@ -1,41 +1,39 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-uninstall.html
+applies_to:
+  deployment:
+    ece: 
 ---
 
-# Uninstall Elastic Cloud Enterprise [ece-uninstall]
+# Uninstall {{ece}} [ece-uninstall]
 
-You might need to remove Elastic Cloud Enterprise for one of the following reasons:
+This guide provides instructions for uninstalling {{ece}} from a specific host within an {{ece}} platform. This process removes the {{ece}} software from the host but does not uninstall the entire {{ece}} platform.
 
-* If the installation process does not complete successfully and you cannot troubleshoot the issue.
-* If you are de-provisioning a host and want to remove the installed Elastic Cloud Enterprise software.
+You might need to remove {{ece}} for one of the following reasons:
 
-You remove Elastic Cloud Enterprise by removing all containers on the host:
-
-* If using Docker
-
-::::{admonition} 
-```sh
-docker rm -f frc-runners-runner frc-allocators-allocator $(docker ps -a -q); sudo rm -rf /mnt/data/elastic/ && docker ps -a
-```
+* The installation process does not complete successfully and you can't troubleshoot the issue.
+* You are de-provisioning a host and want to remove the installed {{ece}} software.
 
+::::{important}
+If the {{ece}} host you are uninstalling has the allocator role and is running instances from orchestrated deployments, all containers will be deleted, causing the instances to appear unhealthy on the Deployments page. To avoid disruptions, it is recommended to [vacate the host](/deploy-manage/maintenance/ece/move-nodes-instances-from-allocators.md) before uninstalling {{ece}}.
 ::::
 
+You can remove {{ece}} by removing all containers on the host:
 
-* If using Podman
+* If using Docker:
 
-::::{admonition} 
-```sh
-sudo podman rm -f frc-runners-runner frc-allocators-allocator $(sudo podman ps -a -q); sudo rm -rf /mnt/data/elastic && sudo podman ps -a
-```
+  ```sh
+  docker rm -f frc-runners-runner frc-allocators-allocator $(docker ps -a -q); sudo rm -rf /mnt/data/elastic/ && docker ps -a
+  ```
 
-::::
+* If using Podman:
 
+  ```sh
+  sudo podman rm -f frc-runners-runner frc-allocators-allocator $(sudo podman ps -a -q); sudo rm -rf /mnt/data/elastic && sudo podman ps -a
+  ```
 
-If you plan to reinstall Elastic Cloud Enterprise on the host, make sure you [delete the host](../maintenance/ece/delete-ece-hosts.md) from the Cloud UI first. Reinstallation can fail if the host is still associated with your old Elastic Cloud Enterprise installation.
+If you plan to reinstall {{ece}} on the host, make sure you [delete the host](../maintenance/ece/delete-ece-hosts.md) from the Cloud UI first. Reinstallation can fail if the host is still associated with your old {{ece}} installation.
 
 ::::{warning} 
-During installation, the system generates secrets that are placed into the `/mnt/data/elastic/bootstrap-state/bootstrap-secrets.json` secrets file, unless you passed in a different path with the --host-storage-path parameter. Keep the information in the `bootstrap-secrets.json` file secure by removing it from its default location and placing it into a secure storage location.
+During installation, the system generates secrets that are placed into the `/mnt/data/elastic/bootstrap-state/bootstrap-secrets.json` secrets file, unless you passed in a different path with the `--host-storage-path` parameter. Keep the information in the `bootstrap-secrets.json` file secure by removing it from its default location and placing it into a secure storage location.
 ::::
 
-

deploy-manage/uninstall/uninstall-elastic-cloud-enterprise.md

@@ -1,9 +1,12 @@
 ---
-mapped_pages:
-  - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-uninstalling-eck.html
+applies_to:
+  deployment:
+    eck:
 ---
 
-# Uninstall Elastic Cloud on Kubernetes [k8s-uninstalling-eck]
+# Uninstall {{eck}} [k8s-uninstalling-eck]
+
+This page provides instructions for uninstalling {{eck}}, including removing all Elastic resources and the {{eck}} operator from your cluster.
 
 To uninstall the operator:
 
@@ -23,4 +26,6 @@ To uninstall the operator:
     kubectl delete -f https://download.elastic.co/downloads/eck/2.16.1/crds.yaml
     ```
 
-
+::::{warning}
+Deleting CRDs will trigger deletion of all custom resources (Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash) in all namespaces of the cluster, regardless of whether they are managed by a single operator or multiple operators.
+::::

deploy-manage/uninstall/uninstall-elastic-cloud-on-kubernetes.md

@@ -48,19 +48,19 @@ For advanced use cases, source records can be transformed by invoking a custom L
 
 ## Step 3: Specify the destination settings for your Firehose stream [firehose-step-three]
 
-1. From the **Destination settings** panel, specify the following settings:
+From the **Destination settings** panel, specify the following settings:
 
-    * **Elastic endpoint URL**: Enter the Elastic endpoint URL of your Elasticsearch cluster. To find the Elasticsearch endpoint, go to the {{ecloud}} Console and select **Connection details**. Here is an example of how it looks like: `https://my-deployment.es.us-east-1.aws.elastic-cloud.com`.
-    * **API key**: Enter the encoded Elastic API key. To create an API key, go to the {{ecloud}} Console, select **Connection details** and click **Create and manage API keys**. If you are using an API key with **Restrict privileges**, make sure to review the Indices privileges to provide at least "auto_configure" & "write" permissions for the indices you will be using with this delivery stream.
-    * **Content encoding**: For a better network efficiency, leave content encoding set to GZIP.
-    * **Retry duration**: Determines how long Firehose continues retrying the request in the event of an error. A duration of 60-300s should be suitable for most use cases.
-    * **Parameters**:
+* **Elastic endpoint URL**: Enter the Elastic endpoint URL of your Elasticsearch cluster. To find the Elasticsearch endpoint, go to the {{ecloud}} Console and select **Connection details**. Make sure the endpoint is in the following format: `https://<deployment_name>.es.<region>.<csp>.elastic-cloud.com`.
+* **API key**: Enter the encoded Elastic API key. This can be created in Kibana by following the instructions under [API Keys](../../../deploy-manage/api-keys.md). If you are using an API key with **Restrict privileges**, make sure to review the Indices privileges to provide at least "auto_configure" & "write" permissions for the indices you will be using with this delivery stream.
+* **Content encoding**: To reduce the data transfer costs, use GZIP encoding.
+* **Retry duration**: Determines how long Firehose continues retrying the request in the event of an error. A duration between 60 and 300 seconds should be suitable for most use cases.
+* **Parameters**:
 
-        * `es_datastream_name`: This parameter is optional and can be used to set which data stream documents will be stored. If this parameter is not specified, data is sent to the `logs-awsfirehose-default` data stream by default.
-        * `include_cw_extracted_fields`: This parameter is optional and can be set when using a CloudWatch logs subscription filter as the Firehose data source. When set to true, extracted fields generated by the filter pattern in the subscription filter will be collected. Setting this parameter can add many fields into each record and may significantly increase data volume in Elasticsearch. As such, use of this parameter should be carefully considered and used only when the extracted fields are required for specific filtering and/or aggregation.
-        * `set_es_document_id`: This parameter is optional and can be set to allow Elasticsearch to assign each document a random ID or use a calculated unique ID for each document. Default is true. When set to false, a random ID will be used for each document which will help indexing performance.
+  * `es_datastream_name`: This parameter is optional and can be used to set which data stream documents will be stored. If not specified, logs are stored in `logs-awsfirehose-default` data stream and metrics are stored in `metrics-aws.cloudwatch-default` data stream.
+  * `include_cw_extracted_fields`: This parameter is optional and can be set when using a CloudWatch logs subscription filter as the Firehose data source. When set to true, extracted fields generated by the filter pattern in the subscription filter will be collected. Setting this parameter can add many fields to each record and may significantly increase data volume in Elasticsearch. Therefore, use this parameter carefully and only when the extracted fields are required for specific filtering and/or aggregation.
+  * `set_es_document_id`: This parameter is optional and can be set to allow Elasticsearch to assign each document a random ID or use a calculated unique ID for each document. The default is true. When set to false, a random ID is used for each document, which helps indexing performance.
 
-            1. In the **Backup settings** panel, it is recommended to configure S3 backup for failed records. It’s then possible to configure workflows to automatically retry failed records, for example by using [Elastic Serverless Forwarder](asciidocalypse://docs/elastic-serverless-forwarder/docs/reference/index.md).
+* **Backup settings**: It is recommended to configure S3 backup for failed records. These backups can be used to restore data losses caused by unforeseen service outages.
 
 
 

solutions/observability/cloud/monitor-amazon-web-services-aws-with-amazon-data-firehose.md

@@ -65,6 +65,7 @@ Creating a Network Firewall is not trivial and is beyond the scope of this guide
         1. Go to the [Elastic Cloud](https://cloud.elastic.co/) console
         2. Find your deployment in the **Hosted deployments** card and select **Manage**.
         3. Under **Applications** click **Copy endpoint** next to **Elasticsearch**.
+        4. Make sure the endpoint is in the following format: `https://<deployment_name>.es.<region>.<csp>.elastic-cloud.com`.
 
     * **To create the API key**:
 
@@ -74,17 +75,11 @@ Creating a Network Firewall is not trivial and is beyond the scope of this guide
 
 4. Set up the delivery stream by specifying the following data:
 
-    * Elastic endpoint URL
-    * API key
-    * Content encoding: gzip
-    * Retry duration: 60 (default)
-    * Parameter **es_datastream_name** = `logs-aws.firewall_logs-default`
-    * Backup settings: failed data only to S3 bucket
-
-
-::::{important}
-Verify that your **Elasticsearch endpoint URL** includes `.es.` between the **deployment name** and **region**. Example: `https://my-deployment.es.us-east-1.aws.elastic-cloud.com`
-::::
+    * Elastic endpoint URL: The URL that you copied in the previous step.
+    * API key: The API key that you created in the previous step.
+    * Content encoding: To reduce the data transfer costs, use GZIP encoding.
+    * Retry duration: A duration between 60 and 300 seconds should be suitable for most use cases.
+    * Backup settings: It is recommended to configure S3 backup for failed records. These backups can then be used to restore failed data ingestion caused by unforeseen service outages.
 
 
 The Firehose stream is ready to send logs to our Elastic Cloud deployment.