# Unable to create ILM policy using version 6.8.8 **URL:** \ **Category:** Elasticsearch\ **Tags:** ilm-index-lifecycle-management\ **Created:** [October 8, 2024, 7:18am UTC](https://discuss.elastic.co/t/unable-to-create-ilm-policy-using-version-6-8-8/368409 "2024-10-08T07:18:41Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Pranathi\_Kodicherla](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pranathi_kodicherla/32/138164_2.png) [@Pranathi\_Kodicherla](https://discuss.elastic.co/u/Pranathi_Kodicherla)\ **Post date:** [October 8, 2024, 7:18am UTC](https://discuss.elastic.co/t/unable-to-create-ilm-policy-using-version-6-8-8/368409/1 "2024-10-08T07:18:41Z")
I am trying to hit the POST \_ilm/policy/test-policy API with the corresponding body. The version is 6.8.8 but the on prem elastic does not have the xpack plugin. The API throws the error: Invalid index name exception. Invalid index name \_ilm must not start with \_,-,+. What is the root cause? ---
**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:** [October 8, 2024, 7:28am UTC](https://discuss.elastic.co/t/unable-to-create-ilm-policy-using-version-6-8-8/368409/2 "2024-10-08T07:28:32Z")
You are running a very old version that has been EOL for a long time so I would recommend you upgrade. Version 6.8 has the required plugins bundled by default unless you are running the OSS distribution (sounds like that may be the case) so verify the version and distribution the cluster is running. Also check settings so you are not disabling anything. As this is a very old version it is important that you look at the correct version of the documentation as the API has changed over time. I am not sure the ability to test a policy exists in the version you are running even if you have the default distribution. If you are using the OSS distribution you will need to upgrade to the default distribution before ILM is available. I have not used the OSS version, especially on this very old version, so will not be able to help much with that. ---
**Author:** ![Pranathi\_Kodicherla](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pranathi_kodicherla/32/138164_2.png) [@Pranathi\_Kodicherla](https://discuss.elastic.co/u/Pranathi_Kodicherla)\ **Post date:** [October 8, 2024, 8:43am UTC](https://discuss.elastic.co/t/unable-to-create-ilm-policy-using-version-6-8-8/368409/3 "2024-10-08T08:43:52Z")
You are right regarding the use of OSS version. I verified that even the 6.8.8 oss version supports ilm given that xpack is present. I understand that upgrading is necessary. But installing the xpack plugin separately is a valid solution right? ---
**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:** [October 8, 2024, 8:56am UTC](https://discuss.elastic.co/t/unable-to-create-ilm-policy-using-version-6-8-8/368409/4 "2024-10-08T08:56:23Z")
> [@Pranathi\_Kodicherla](#): > > The GET / endpoint gives 6.8.8. Can you please show the output here? > [@Pranathi\_Kodicherla](#): > > I verified that even the 6.8.8 oss version supports ilm. How did you do this? This version is so old that I do not recall exactly what was and was not available in the OSS version, so I could very well be wrong here. ---
**Author:** ![Pranathi\_Kodicherla](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pranathi_kodicherla/32/138164_2.png) [@Pranathi\_Kodicherla](https://discuss.elastic.co/u/Pranathi_Kodicherla)\ **Post date:** [October 8, 2024, 9:02am UTC](https://discuss.elastic.co/t/unable-to-create-ilm-policy-using-version-6-8-8/368409/5 "2024-10-08T09:02:34Z")
I verified here: [Install Elasticsearch with Docker | Elasticsearch Guide [6.8] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/docker.html) Which is the official documentation linked to the 6.8.8 oss version. Sorry cannot paste the api response for security reasons. The version is displayed as 6.8 for sure. ---
**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:** [October 8, 2024, 9:10am UTC](https://discuss.elastic.co/t/unable-to-create-ilm-policy-using-version-6-8-8/368409/6 "2024-10-08T09:10:10Z")
That seems to download the default distribution so please curl `:9200` against the docker instance to see exactly which distribution you tested on. > [@Pranathi\_Kodicherla](#): > > Sorry cannot paste the api response for security reasons. The version is displayed as 6.8 for sure. There is nothing security related there, but if you do not want to post it all just copy the exact `version` and `distribution`. If ILM is available with the OSS distribution you will need to check if your cluster is secured and if so how it is secured. A lot of users that have the OSS distribution installed use some third-party security plugin, and it is quite possible this is not aware of all interfaces and block access. ---
**Author:** ![Pranathi\_Kodicherla](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pranathi_kodicherla/32/138164_2.png) [@Pranathi\_Kodicherla](https://discuss.elastic.co/u/Pranathi_Kodicherla)\ **Post date:** [October 8, 2024, 9:28am UTC](https://discuss.elastic.co/t/unable-to-create-ilm-policy-using-version-6-8-8/368409/7 "2024-10-08T09:28:48Z")
Tried the 9200 port. Version number is 6.8.8 and build\_flavor is oss. ---
**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:** [October 8, 2024, 9:39am UTC](https://discuss.elastic.co/t/unable-to-create-ilm-policy-using-version-6-8-8/368409/8 "2024-10-08T09:39:24Z")
OK. If that is the case I would recommend looking at security as mentioned earlier.