# AWS Secrets Manager

{% hint style="info" %}
The content of this documentation is under revision and may change. We appreciate your understanding as we work to improve it.
{% endhint %}

**AWS Secrets Manager** manages AWS Secrets Manager services using AWS SDK version 2.x.

## **Parameters**

Take a look at the configuration parameters for the connector. Parameters supported by [Double Braces expressions](/documentation/connectors-and-triggers/double-braces/overview.md) are marked with `(DB)`.

### **General tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Dynamic Account</strong></td><td>When active, the connector will use the account dynamically. Otherwise, it will use the account statically.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Account Name</strong> <code>(DB)</code></td><td>The name of the dynamic account used by the connector. This account must have been previously configured in a <a href="/pages/0kxlZ011XP4A2T43v9kh"><strong>Store Account</strong></a> connector in the pipeline for this process to take effect. It is only available if the <strong>Dynamic Account</strong> parameter is active.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Account</strong></td><td>The account used by the connector. It is only available if the <strong>Dynamic Account</strong> parameter is inactive.</td><td>N/A</td><td>Account</td></tr><tr><td><strong>Label</strong> <code>(DB)</code></td><td>Logical name.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Operation</strong></td><td>The operation to perform.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Fail On Error</strong></td><td>If the option is activated, the pipeline's execution with an error will be interrupted. Otherwise, the pipeline execution proceeds, but the result will show a false value for the <code>"success"</code> property.</td><td>False</td><td>Boolean</td></tr></tbody></table>

### **Optional tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Binary Payload</strong></td><td>Set if the secret is binary or not.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Override Endpoint</strong></td><td>Set the need for overidding the endpoint. This option needs to be used in combination with the <strong>Uri Endpoint Override</strong> parameter.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Pojo Request</strong></td><td>Whether to use a POJO request as body or not.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Region <code>DB</code></strong></td><td>The region in which Secrets Manager client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You’ll need to use the name <code>Region.EU_WEST_1.id()</code></td><td>N/A</td><td>String</td></tr><tr><td><strong>Trust All Certificates</strong></td><td>Whether to trust all certificates in case of overriding the endpoint.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Uri Endpoint Override</strong> <code>(DB)</code></td><td>Set the overriding URI endpoint. This option needs to be used in combination with the <strong>Override Endpoint</strong> parameter.</td><td>N/A</td><td>String</td></tr></tbody></table>

### **Headers tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Manager Operation</strong> <code>(DB)</code></td><td>The operation to perform.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Manager Max Results</strong></td><td>The number of results to include in the response.</td><td>N/A</td><td>Integer</td></tr><tr><td><strong>Manager Secret Name</strong> <code>(DB)</code></td><td>The name of the secret.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Manager Secret Description</strong> <code>(DB)</code></td><td>The description of the secret.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Manager Secret Id</strong> <code>(DB)</code></td><td>The ARN or name of the secret.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Manager Lambda Rotation Function Arn</strong> <code>(DB)</code></td><td>The ARN of the Lambda rotation function that can rotate the secret.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Manager Secret Version Id</strong> <code>(DB)</code></td><td>The unique identifier of the version of the secret.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Manager Secret Replication Regions</strong> <code>(DB)</code></td><td>A comma separated list of Regions in which to replicate the secret.</td><td>N/A</td><td>String</td></tr></tbody></table>

### **Documentation tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Documentation</strong></td><td>Section for documenting any necessary information about the connector configuration and business rules.</td><td>N/A</td><td>String</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.digibee.com/documentation/connectors-and-triggers/connectors/aws/secrets-manager.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.