> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/aws-bedrock.md).

# AWS Bedrock

Connect to AWS Bedrock using IAM user credentials or assume-role authentication. Enterprise-grade AI with AWS security and compliance.

This catalog entry does not define workflow actions, event triggers, or knowledge retrieval capabilities.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector                 | Authentication |
| ------------------------- | -------------- |
| AWS Bedrock (IAM User)    | Credentials    |
| AWS Bedrock (Assume Role) | Credentials    |

#### AWS Bedrock (IAM User)

Connect to AWS Bedrock using IAM user credentials (access key and secret key).

**Set up in AWS Bedrock**

1. Sign in to the AWS Management Console and open the IAM service.
2. Create (or select) an IAM user and attach a policy granting Bedrock access, such as the AWS-managed AmazonBedrockFullAccess policy (or a least-privilege policy scoped to the models you need).
3. Under the user's Security credentials, create an access key and copy the Access key ID and Secret access key.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **AWS Bedrock (IAM User)**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field     | Required | What to enter                             |
| ----------------- | -------- | ----------------------------------------- |
| Access Key ID     | Yes      | Your AWS access key ID.                   |
| Secret Access Key | Yes      | Your AWS secret access key.               |
| Region            | Yes      | AWS region for Bedrock (e.g., us-east-1). |

**Provider documentation:** [Setup reference](https://docs.aws.amazon.com/bedrock/latest/userguide/getting-started.html).

#### AWS Bedrock (Assume Role)

Connect to AWS Bedrock using assume-role authentication for enhanced security.

**Set up in AWS Bedrock**

1. Attach a policy to the role granting the Bedrock permissions your workflows need.
2. Copy the role's ARN.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **AWS Bedrock (Assume Role)**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field          | Required                 | What to enter                                               |
| ---------------------- | ------------------------ | ----------------------------------------------------------- |
| Region                 | Yes                      | AWS region for Bedrock (e.g., us-east-1).                   |
| Role ARN to Assume     | Yes                      | The ARN of the IAM role to assume for Bedrock operations.   |
| External ID (Optional) | Optional / as applicable | External ID for additional security when assuming the role. |

**Provider documentation:** [Setup reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user.html).

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Important behavior

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# 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 by asking a question.

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

```
GET https://docs.stackai.com/integrations/catalog/aws-bedrock.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 `automate deployments from our CI pipeline` 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.
