# Unable to create new security deployment ECE

**URL:** <https://discuss.elastic.co/t/unable-to-create-new-security-deployment-ece/368382>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [October 7, 2024, 8:22pm UTC](https://discuss.elastic.co/t/unable-to-create-new-security-deployment-ece/368382 "2024-10-07T20:22:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shani\_angarkadu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shani_angarkadu/32/50638_2.png) [@shani\_angarkadu](https://discuss.elastic.co/u/shani_angarkadu)\
**Post date:** [October 7, 2024, 8:22pm UTC](https://discuss.elastic.co/t/unable-to-create-new-security-deployment-ece/368382/1 "2024-10-07T20:22:05Z")

</div>

We had an issue with our SAML configuration, and the security cluster kept restarting, even after we attempted to update the deployment configuration by removing the SAML block. However, we were unable to bring the cluster back.

As a result, we had no choice but to delete the security cluster.

Now, as we attempt to recreate it, it's still pointing to the old cluster and throwing the following exception.

used the platform security api

> **[Create security deployment | Elastic Cloud Enterprise Reference \[3.7\] | Elastic](https://www.elastic.co/guide/en/cloud-enterprise/current/create-security-deployment.html)**

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/e/de742ce2d904717c6b20942af14a571a8805892c.jpeg)

---

<div class="post-metadata">

**Author:** ![joean407](https://avatars.discourse-cdn.com/v4/letter/j/96bed5/32.png) [@joean407](https://discuss.elastic.co/u/joean407)\
**Post date:** [October 10, 2024, 11:30am UTC](https://discuss.elastic.co/t/unable-to-create-new-security-deployment-ece/368382/2 "2024-10-10T11:30:49Z")

</div>

I am quite sure you cannot delete the security cluster without wrecking the whole ECE installation since the security cluster is at the root of all authentication in the platform... I would recommend to start a support case about this because I'm quite sure there is no easy fix to this issue.
