// Module included in the following assemblies:
//
// * security/external_secrets_operator/index.adoc

:_mod-docs-content-type: CONCEPT
[id="external-secrets-about_{context}"]
= About the {external-secrets-operator}

[role="_abstract"]
Use the {external-secrets-operator} to integrate the `external-secrets` application with the {product-title} cluster. The `external-secrets` application fetches secrets stored in external providers such as AWS Secrets Manager, HashiCorp Vault, Google Secret Manager, Azure Key Vault, {ibm-cloud-title} Secrets Manager, and AWS Systems Manager Parameter Store, and integrates them with Kubernetes in a secure manner.

Using the {external-secrets-operator-short} ensures the following:

* Decouples applications from the secret-lifecycle management.
* Centralizes secret storage to support compliance requirements.
* Enables secure and automated secret rotation.
* Supports multi-cloud secret sourcing with fine-grained access control.
* Centralizes and audits access control.

[IMPORTANT]
====
Do not attempt to use more than one {external-secrets-operator-short} in your cluster. If you have a community {external-secrets-operator-short} installed in your cluster, you must uninstall it before installing the {external-secrets-operator}.
====

For more information about the `external-secrets` application, see "external-secrets application" in Additional resources.

Use the {external-secrets-operator-short} to authenticate with the external secrets store, retrieve secrets, and inject the retrieved secrets into a native Kubernetes secret. This method removes the need for applications to directly access or manage external secrets.

