Sazabi
MCP connectors

AWS

Give the Sazabi agent tools to search AWS documentation and run AWS API operations using your own IAM credentials.

About

AWS is an MCP connector that gives the Sazabi agent tools to search AWS documentation and invoke AWS API operations. The AWS MCP server is a remote endpoint hosted by AWS at https://aws-mcp.<region>.api.aws/mcp. It authenticates with AWS SigV4 — Sazabi signs each outbound request in its MCP client using the IAM access key, secret, optional session token, and region you provide, so no local proxy is required. Actual authorization is enforced by the IAM identity behind those credentials; the per-connection read-only toggle governs write tools on Sazabi's side. The AWS MCP server is currently available in two regions: US East (N. Virginia) and Europe (Frankfurt).

What the agent can do:

  • Search AWS documentation from agent conversations
  • Invoke AWS API operations scoped to the supplied IAM identity
  • Reach the region-scoped aws-mcp.<region>.api.aws/mcp endpoint

Prerequisites

  • An AWS account and IAM credentials (access key ID + secret access key, or temporary credentials with a session token)
  • Least-privilege permissions matching what the agent should be allowed to do
  • The AWS region to target: US East (N. Virginia, us-east-1) or Europe (Frankfurt, eu-central-1)

Set up in the dashboard

Configure connectors in the dashboard under Settings > MCP connectors.

Add your IAM credentials

Provide AWS IAM credentials; Sazabi signs each request with SigV4 — no local proxy is needed. In the AWS Console, create an IAM user or role with only the permissions Sazabi should use, then generate an access key. Paste the Access key ID and Secret access key. For temporary credentials from an assumed role, also paste the Session token. Then select the AWS region for the endpoint (us-east-1 or eu-central-1).

Set up with the CLI

AWS authenticates with AWS IAM credentials (SigV4-signed), and sazabi mcp-connectors connect only supports OAuth providers — so set up this connector in the dashboard first (above). Once it's connected, the Sazabi CLI can inspect and manage it (installed and authenticated — see sazabi mcp-connectors reference):

sazabi mcp-connectors list
sazabi mcp-connectors details <connection-id>

Find the connection ID with sazabi mcp-connectors list. To rotate the stored credentials later, use sazabi mcp-connectors update-credentials <connection-id>.

Verify

Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the credentials are valid and the selected region is supported.

Troubleshooting

No tools discovered — Confirm the IAM credentials are valid and the selected endpoint region is us-east-1 or eu-central-1; the AWS MCP server is not available in other regions.

Connection shows needs attention — The credentials may have expired or been revoked; reconnect from Settings > MCP connectors with fresh credentials.

Further reading