Index lifecycle policies not transfered to external elasticsearch

[lf-puc]

Hello
Because of resource limitations, I am using SELKS with an external elasticsearch physical machine (as SELKS). But the Policies set in the Index Lifecycle Management (that used to work when elasticsearch was running on the local SELKS machine) were not transfered to the external elasticsearh so the indices (mainly logstash) are never deleted when they were supposed to reach the Delete phase. If I run
GET /_cat/indices?v
on the SELKS Kibana console, logstash-* indices are not shown. So we conclude that the console is not connected to the external ES server. If I use tools like Elasticvue on the external ES server, I can see 600+ indices that are never deleted.
How can I set the Lifecycle Policy to these indices that are on the external ES server?
Thanks

[pevma]

i think you should be able to do that form the external ES Management console.
As a first step the extra nes can be manually deleted of course.

[lf-puc]

Hello
Yes, I have been deleting the old indices manually with ElasticVue. However I can't easily create a lifecycle policy and apply to index templates with this software. Do you know a good [free] ES Management console to automate this process?
Thank you.

[lf-puc]

Hello
I ended up creating a cron job on the elasticsearch server to delete every logstash log created on a date x days ago, using curl.

curl -X DELETE "localhost:9200/logstash-smtp-$CHOSEN_DATE?pretty"

$CHOSEN_DATE is a calculation from date subtracting the number of seconds corresponding to the number of days to be kept.

Hope it helps someone while we wait for a better solution.