# Exception while attempting Migration from AWS OSS 1.3 to Elasticsearch 7.17

**URL:** <https://discuss.elastic.co/t/exception-while-attempting-migration-from-aws-oss-1-3-to-elasticsearch-7-17/337797>\
**Category:** Elasticsearch\
**Tags:** migration\
**Created:** [July 6, 2023, 12:48pm UTC](https://discuss.elastic.co/t/exception-while-attempting-migration-from-aws-oss-1-3-to-elasticsearch-7-17/337797 "2023-07-06T12:48:34Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![gaurav\_jain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gaurav_jain/32/123032_2.png) [@gaurav\_jain](https://discuss.elastic.co/u/gaurav_jain)\
**Post date:** [July 6, 2023, 12:48pm UTC](https://discuss.elastic.co/t/exception-while-attempting-migration-from-aws-oss-1-3-to-elasticsearch-7-17/337797/1 "2023-07-06T12:48:34Z")

</div>

Hello.

We are planning to migrate existing elastic cluster from AWS opensearch service 1.1 to Elastic Cloud: 7.17 with some indexes of ~50GB in size

First, I launched an elastic cloud cluster : 7.17.

- Data migration experimented with Snapshot & Restore.  
[Aws - Elastic Cloud migration doc](https://www.elastic.co/blog/migrating-from-aws-elasticsearch-to-elasticsearch-service-on-elastic-cloud)

As a result, as shown below, the version of OpenSearch is too large and an error occurs if there is no compatibility.

```auto
the snapshot was created with Elasticsearch version [35.24.80-beta2] which is higher than the version of this node [7.17.11]

```

- Data migration experimented with remote re-indexing from Elastic Cloud:

```auto
{
  "source": {
    "remote": {
      "host": https://<aws-clsuter-url>:443,
      "username": " ****",
      "password": " *******"
    },
    "index": "<indexName>"
  },
  "dest": {
    "index": "<indexName>"
  }

```

Result:

"reason" : "body={"error":{"root\_cause":"type":"illegal\_argument\_exception","reason":"No search type for [scan]"}],"type":"illegal\_argument\_exception","reason":"No search type for [scan]"},"status":400}"

Can someone please suggest if this migration is possible if yes, how can i achieve this.

Thanks in advance

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 6, 2023, 1:04pm UTC](https://discuss.elastic.co/t/exception-while-attempting-migration-from-aws-oss-1-3-to-elasticsearch-7-17/337797/3 "2023-07-06T13:04:31Z")

</div>

Opensearch was based on Elasticsearch 7.10 but has diverged and is no longer compatible. I therefore do not think you can migrate using snapshots, but rather have to create a custom script to reindex your data. I would not expect remote reindexing to be able to connect to Opensearch (unless possibly if you [override the version response it provides](https://opensearch.org/docs/latest/tools/index/)).

---

<div class="post-metadata">

**Author:** ![gaurav\_jain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gaurav_jain/32/123032_2.png) [@gaurav\_jain](https://discuss.elastic.co/u/gaurav_jain)\
**Post date:** [July 10, 2023, 9:42am UTC](https://discuss.elastic.co/t/exception-while-attempting-migration-from-aws-oss-1-3-to-elasticsearch-7-17/337797/4 "2023-07-10T09:42:27Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> but rather have to create a custom script to reindex your data

Hi @Christian_Dahlqvist ,

Could you please elaborate more on this, as what exactly this custom script would do . Also i have some indexes with ~40GB of data ,would this be a problem of re-indexing ?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 10, 2023, 9:57am UTC](https://discuss.elastic.co/t/exception-while-attempting-migration-from-aws-oss-1-3-to-elasticsearch-7-17/337797/5 "2023-07-10T09:57:20Z")

</div>

The script I discussed would basically need to do what a remote reindexing does. If you can get Elasticsearch to connect directly and run reindexing that way it is easier.

Reindexing large data volumes is possible but might be problematic if there is a lack of resources and/or connection/bandwidth issues.

---

<div class="post-metadata">

**Author:** ![gaurav\_jain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gaurav_jain/32/123032_2.png) [@gaurav\_jain](https://discuss.elastic.co/u/gaurav_jain)\
**Post date:** [July 13, 2023, 11:50am UTC](https://discuss.elastic.co/t/exception-while-attempting-migration-from-aws-oss-1-3-to-elasticsearch-7-17/337797/6 "2023-07-13T11:50:12Z")

</div>

Hi @Christian_Dahlqvist ,

Would it be possible for you to share the snippet of script ?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 13, 2023, 11:54am UTC](https://discuss.elastic.co/t/exception-while-attempting-migration-from-aws-oss-1-3-to-elasticsearch-7-17/337797/7 "2023-07-13T11:54:44Z")

</div>

I do not have anything to share, so you will need to create it yourself.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 25, 2023, 12:29pm UTC](https://discuss.elastic.co/t/exception-while-attempting-migration-from-aws-oss-1-3-to-elasticsearch-7-17/337797/8 "2023-07-25T12:29:12Z")

</div>

May be you can use Logstash to do this?

> [@gaurav\_jain](#):
>
> Data migration experimented with remote re-indexing from Elastic Cloud:

I think that's indeed not possible: [Migrate from Amazon OpenSearch Service (formerly Amazon Elasticsearch Service) | Elasticsearch Service Documentation | Elastic](https://www.elastic.co/guide/en/cloud/current/ec-migrate-from-aws.html)

> The recent Amazon OpenSearch Service versions do not use an Elasticsearch-compatible repository format, and are also incompatible with the Elasticsearch remote reindex feature.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 24, 2023, 5:47am UTC](https://discuss.elastic.co/t/exception-while-attempting-migration-from-aws-oss-1-3-to-elasticsearch-7-17/337797/10 "2023-08-24T05:47:46Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.