From 304be73f06cc498b5e2d2d78655c4a0275b42928 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A1udia=20Correia?= Date: Thu, 13 Mar 2025 11:26:30 +0000 Subject: [PATCH] Add note to change-hardware.md docs --- deploy-manage/deploy/elastic-cloud/change-hardware.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/deploy-manage/deploy/elastic-cloud/change-hardware.md b/deploy-manage/deploy/elastic-cloud/change-hardware.md index 6fbe0958dc..78255b7a49 100644 --- a/deploy-manage/deploy/elastic-cloud/change-hardware.md +++ b/deploy-manage/deploy/elastic-cloud/change-hardware.md @@ -24,6 +24,12 @@ Prerequisites: Follow these steps to migrate to a different instance configuration, replacing the default `$EC_API_KEY` value with your actual API key: 1. From the [list of instance configurations available for each region](asciidocalypse://docs/cloud/docs/reference/cloud-hosted/ec-regions-templates-instances.md), select the target instance configuration you want to migrate to. + + ::::{note} + The target instance configuration must be compatible with the Elasticsearch tier or stateless resource you are updating. + For example, if you are migrating the hot Elasticsearch tier, the target instance configuration must also be of the `es.datahot` family. + :::: + 2. Get the deployment update payload from the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body) **Edit** page, by selecting **Equivalent API request**, and store it in a file called `migrate_instance_configuration.json`. Example payload containing relevant data for migrating the hot Elasticsearch tier: