Skip to content

Commit 36476af

Browse files
Add note to change-hardware.md docs (#766)
This PR adds a note to the change-hardware.md docs, to remind customers that the target instance configuration must be compatible with the tier/resource they're updating.
1 parent 0eea48e commit 36476af

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

deploy-manage/deploy/elastic-cloud/change-hardware.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,12 @@ Prerequisites:
2424
Follow these steps to migrate to a different instance configuration, replacing the default `$EC_API_KEY` value with your actual API key:
2525

2626
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.
27+
28+
::::{note}
29+
The target instance configuration must be compatible with the Elasticsearch tier or stateless resource you are updating.
30+
For example, if you are migrating the hot Elasticsearch tier, the target instance configuration must also be of the `es.datahot` family.
31+
::::
32+
2733
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`.
2834

2935
Example payload containing relevant data for migrating the hot Elasticsearch tier:

0 commit comments

Comments
 (0)