Elasticsearch instance unprotected, thus allowing an attacker to perform write/read operations on the database huly

### Description of the issue
A clear and concise description of the issue.
i found bug Elasticsearch instance unprotected, thus allowing an attacker to perform write/read operations on the database huly
### Your environment
* Version of Huly
* Browser (and version)
* Your operating system (and version)

### Steps to reproduce
Please produce the steps for us to reproduce this issue.
1- i use for exploit bug and create poc in db by used in linux os

curl -XPUT 'http://23.94.180.12:9200/poc3' and see create poc in db
http://23.94.180.12:9200/poc3
and go to http://23.94.180.12:9200/huly_storage_index_v1/_search?size=1000 and see huly in url thats means own company
### Expected behaviour
Tell us what should happen.

### Actual behaviour
Tell us what happens instead (include screenshots or logs).
thus allowing an attacker to perform write/read operations on the huly

### Possible solutions
(Not obligatory)
If you know how to fix the bug, please describe your solution here.

Start by reviewing how the Elasticsearch service at port 9200 is exposed and whether the reported write and read requests can be reproduced safely. No repository file or test is identified in the issue; done means unauthenticated external requests can no longer access the Huly indexes, with appropriate verification of the deployment configuration.

Written by the indexing model from the issue text.