# How to unblock .security-x index?

**URL:** https://discuss.elastic.co/t/how-to-unblock-security-x-index/368918
**Category:** Elasticsearch
**Tags:** elastic-stack-security, docker
**Created:** [October 16, 2024, 1:41pm UTC](https://discuss.elastic.co/t/how-to-unblock-security-x-index/368918 "2024-10-16T13:41:41Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Oleg\_G](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oleg_g/32/138421_2.png) [@Oleg\_G](https://discuss.elastic.co/u/Oleg_G)
#### Post date: [October 16, 2024, 1:41pm UTC](https://discuss.elastic.co/t/how-to-unblock-security-x-index/368918/1 "2024-10-16T13:41:41Z")

</div>

We run Elastic and Kibana in Docker.  
We hit the disk space limit and indices moved to read-only state. After cleaned up I tried to set them to read-write state by executing this command-

```auto
$ curl -XPUT -H "Content-Type: application/json" https://[YOUR_ELASTICSEARCH_ENDPOINT]:9200/_all/_settings -d '{"index.blocks.read_only_allow_delete": null}'

```

but some indices were not affected, including .security \*.  
It looks like that elastic user does not have enough privileges to do it.  
I tried to create a new role in roles.yml, but I still cannot assign this role to elastic due to .security index is read only.  
So it looks like a catch22 situation.  
Is it a way to assign this role to an elastic user directly in yamls, bypassing API?  
Or may be there is more elegant way to get out of this loop?