# Synonym file support for ElasticSearch 5.x in AWS

**URL:** <https://discuss.elastic.co/t/synonym-file-support-for-elasticsearch-5-x-in-aws/105320>\
**Category:** Elasticsearch\
**Created:** [October 26, 2017, 3:20am UTC](https://discuss.elastic.co/t/synonym-file-support-for-elasticsearch-5-x-in-aws/105320 "2017-10-26T03:20:37Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![gautam\_gro](https://avatars.discourse-cdn.com/v4/letter/g/b9e5f3/32.png) [@gautam\_gro](https://discuss.elastic.co/u/gautam_gro)\
**Post date:** [October 26, 2017, 3:20am UTC](https://discuss.elastic.co/t/synonym-file-support-for-elasticsearch-5-x-in-aws/105320/1 "2017-10-26T03:20:37Z")

</div>

As we know, Elasticsearch supports synonyms through their synonym token filter, which expects a file of all the synonyms to be present at a particular location on the server filesystem.

Is there a way I can configure this with Amazon ES?

In AWS there's no option to upload synonym file......?

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [October 26, 2017, 4:37am UTC](https://discuss.elastic.co/t/synonym-file-support-for-elasticsearch-5-x-in-aws/105320/2 "2017-10-26T04:37:23Z")

</div>

The synonym filter also supports handling the terms inline to the filter  
definition. See the second example at  
[https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-synonym-tokenfilter.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-synonym-tokenfilter.html)

Not sure how AWS-hosted ES works, but there might be a limitation of using  
such files.

---

<div class="post-metadata">

**Author:** ![gautam\_gro](https://avatars.discourse-cdn.com/v4/letter/g/b9e5f3/32.png) [@gautam\_gro](https://discuss.elastic.co/u/gautam_gro)\
**Post date:** [October 26, 2017, 4:45am UTC](https://discuss.elastic.co/t/synonym-file-support-for-elasticsearch-5-x-in-aws/105320/3 "2017-10-26T04:45:51Z")

</div>

But problem with inline approach is that you cannot update synonym list later on. It allows only single time.  
Any suggestion?

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [October 26, 2017, 5:07am UTC](https://discuss.elastic.co/t/synonym-file-support-for-elasticsearch-5-x-in-aws/105320/4 "2017-10-26T05:07:10Z")

</div>

It does not matter since even with the synonym list, the file is not  
re-read for an open index. But in general, it does make handling updates  
more difficult. AWS-hosted ES has many limitations.

---

<div class="post-metadata">

**Author:** ![gautam\_gro](https://avatars.discourse-cdn.com/v4/letter/g/b9e5f3/32.png) [@gautam\_gro](https://discuss.elastic.co/u/gautam_gro)\
**Post date:** [October 26, 2017, 5:17am UTC](https://discuss.elastic.co/t/synonym-file-support-for-elasticsearch-5-x-in-aws/105320/5 "2017-10-26T05:17:06Z")

</div>

Yes you are right...AWS does'nt allow to close or stop an existing open index. Only way is to delete cluster and re create new index, which is not a proper solution.

---

<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:** [November 23, 2017, 5:17am UTC](https://discuss.elastic.co/t/synonym-file-support-for-elasticsearch-5-x-in-aws/105320/6 "2017-11-23T05:17:09Z")

</div>

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