Team, Im looking for someone who can give me some light to my investigation which i did with ElasticSearch. if any one of you can confirm or extend what are requirements need to be passed to use own instance of Elastic ? This is what i have already observed. • abilities to create index_template - it can be created manually (elasticsearch-setup docker) • abilities to create index_policy (ilm policy) - it can be any of policies i guess just assigne to index_template propperly (elasticsearch-setup docker) • abilities to create indexes (datahub-gms) • ElasticSearch with version at least 7.8 (from that version ILM Policy is supported) • ElasticSearch is using Java High Level REST Client for creating and updating indexes - based on my onw investigation of a classes which are imported to the code. (This one will be deprecated in version 7.15.0 of ELK with ability to use with future version with compatibility mode enabled) • How much amount of data i can expect on a daily basis - i know it is really hard to estimate, but as you already deployed you have more insights of the estimation. Do you know if there are any other requirements which need to be fulfilled to host own ELK or use ELK in the different environments, especially what type of permission users is requiring to work with Datahub ? read/write permission to indexes, what else ? Especially in context of using Elasticsearch as well as Graph Service Implementation ? https://www.elastic.co/guide/en/elasticsearch/reference/current/security-privileges.html Thank you in advance Jaroslaw Gronowski