AWS opensearch-service documentation change
Summary
Updated version compatibility requirements and reindexing steps for OpenSearch 3.x upgrades
Security assessment
The changes focus on version compatibility and migration procedures without mentioning security vulnerabilities or mitigations. While reindexing old indexes is required, this is a compatibility requirement rather than addressing a security issue.
Diff
diff --git a/opensearch-service/latest/developerguide/version-migration.md b/opensearch-service/latest/developerguide/version-migration.md index 8404319b0..1fd0e6d1f 100644 --- a//opensearch-service/latest/developerguide/version-migration.md +++ b//opensearch-service/latest/developerguide/version-migration.md @@ -21,8 +21 @@ From version | To version -OpenSearch 3._x_ | OpenSearch 3.3 OpenSearch 3.3 maintains full compatibility with OpenSearch 3.1, with no breaking changes between these versions. If you're upgrading from OpenSearch versions prior to 3.1 or from Elasticsearch, follow the upgrade procedures documented for OpenSearch 3.1, which apply to OpenSearch 3.3 as well. Reindex incompatible indexes before upgrading to OpenSearch 3.3. If your domain contains indexes created in OpenSearch 1.3, Elasticsearch 7.10, or earlier versions, you must reindex them before upgrading to version 3.3. OpenSearch 3.x doesn't support these older indexes, regardless of whether they' re in hot, UltraWarm, or cold storage. To reindex incompatible UltraWarm or cold indexes: - - 1. Migrate the indexes to hot storage. - 2. Reindex the data. - 3. Migrate the indexes back to warm or cold storage. - -Alternatively, delete the indexes if you no longer need them. -OpenSearch 1.3 or 2._x_ | OpenSearch 3.1 If you're running OpenSearch 1.3 or 2.x, you must first upgrade to OpenSearch 2.19 _before_ upgrading to OpenSearch 3.1. Afterward, when you upgrade from OpenSearch 2.19 to OpenSearch 3.1, you may need to address the following incompatible index settings. These were deprecated earlier in 2.x and will lead to an upgrade check validation failure if not removed. +OpenSearch 1.3, 2._x_ , or 3._x_ | OpenSearch 3._x_ If you're running OpenSearch 1.3 or 2.x, you must first upgrade to OpenSearch 2.19 _before_ upgrading to OpenSearch 3.x. When upgrading from OpenSearch 2.19 to OpenSearch 3.x, you may need to address the following incompatible index settings. These were deprecated earlier in 2.x and will lead to an upgrade check validation failure if not removed. @@ -35 +28,7 @@ OpenSearch 1.3 or 2._x_ | OpenSearch 3.1 If you're running OpenSearch 1.3 or 2. -For more information about deprecated index settings and steps to remediate them, see [Index settings](https://docs.opensearch.org/2.6/search-plugins/knn/knn-index/#index-settings). For a complete list of breaking changes for OpenSearch 3.1, see [3.0.0](https://docs.opensearch.org/latest/breaking-changes/#300). +For more information about deprecated index settings and steps to remediate them, see [Index settings](https://docs.opensearch.org/2.6/search-plugins/knn/knn-index/#index-settings). For a complete list of breaking changes for OpenSearch 3.x, see [3.0.0](https://docs.opensearch.org/latest/breaking-changes/#300). If your domain contains indexes created in OpenSearch 1.3, Elasticsearch 7.10, or earlier versions, you must reindex them before upgrading to OpenSearch 3.x. OpenSearch 3.x doesn't support these older indexes, regardless of whether they're in hot, UltraWarm, or cold storage. To reindex incompatible UltraWarm or cold indexes: + + 1. Migrate the indexes to hot storage. + 2. Reindex the data. + 3. Migrate the indexes back to warm or cold storage. + +Alternatively, delete the indexes if you no longer need them.