> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/secrets/secrets-stores/aws-secrets-manager.md).

# AWS Secrets Manager

You can integrate Prisma Cloud with AWS Secrets Manager. First, configure Prisma Cloud to access AWS Secrets Manager, then create rules to inject the relevant secrets into the relevant containers.

**Prerequisites:**

* The service account Prisma Cloud uses to access the secrets store must have the following permissions:
  * secretsmanager:GetSecretValue
  * secretsmanager:ListSecrets
* You have [created a secret](https://docs.aws.amazon.com/secretsmanager/latest/userguide/manage_create-basic-secret.html) in AWS Secrets Manager. Automatic rotation must be disabled. Prisma Cloud supports the key-value secret type only. When storing a new secret, select **Other type of secrets**, then **Secret key/value**.

  <figure><img src="/files/C6WmhX1UWtmuixDT2gbY" alt="aws secrets manager secret type"><figcaption></figcaption></figure>

1. Open Prisma Cloud Console.
2. Integrate Prisma Cloud with the secrets store.
   1. Go to **Manage > Authentication > Secrets**, and click **Add store**.
   2. Enter a name for the store. This name is used when you create rules to inject secrets into specific containers.
   3. For **Type**, select **AWS Secrets Manager**, then fill out the rest of the form, including your credentials.
   4. Fill out the rest of the form, specifying how to connect to the Secrets Manager.
   5. Click **Add**.

      After clicking **Add**, Prisma Cloud tries connecting to your secrets manager. If successful, the dialog closes, and an entry is added to the table. Otherwise, connection errors are displayed directly in the configuration dialog.

      Next, [inject a secret into a container](/admin-guide/secrets/inject-secrets.md).


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prismacloud.io/admin-guide/secrets/secrets-stores/aws-secrets-manager.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
