> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cloud/es/concepts/advanced-concepts/external-pam-integrations.md).

# Integraciones PAM externas

Conecte Devolutions Cloud con proveedores PAM externos como Entra ID y AWS IAM para lograr un acceso privilegiado y una auditoría centralizados.

Las integraciones PAM externas conectan los flujos de trabajo de acceso privilegiado de Devolutions Cloud con sistemas de identidad o plataformas gestionadas fuera de Devolutions. A través de los proveedores de Devolutions PAM, Devolutions Cloud puede representar fuentes de identidad externas como Entra ID, AWS IAM, bases de datos o proveedores PAM personalizados, al tiempo que centraliza el control de acceso y la auditoría.

En Devolutions Cloud, estas integraciones permiten que el descubrimiento de cuentas privilegiadas, la rotación de contraseñas y los flujos de trabajo de check-out se ejecuten contra sistemas externos, mientras que las aprobaciones, los informes y las políticas permanecen en Devolutions Cloud. Un escenario habitual es gestionar cuentas de Entra ID con privilegios elevados mediante proveedores PAM, mientras los operadores solicitan y utilizan el acceso directamente desde la interfaz de Devolutions Cloud.

#### Temas relacionados

* [PAM con Devolutions Cloud](https://docs.devolutions.net/pam/es/pam-with-devolutions-cloud)
* [Proveedores](https://docs.devolutions.net/pam/es/concepts/providers)
* [Proveedores PAM personalizados](https://docs.devolutions.net/pam/es/pam-with-devolutions-server/getting-started/custom-pam-providers)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/cloud/es/concepts/advanced-concepts/external-pam-integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.