AWS Bedrock

Enable the AWS Bedrock connector in your fastn dashboard, then let each customer authenticate their own AWS Bedrock account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no AWS Bedrock client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own AWS Bedrock account and only ever sees their own models, requests and outputs. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.

Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent calls a model through the customer's own account rather than a shared one.

fastn does. When AWS Bedrock changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.

Each customer authorises their own AWS Bedrock account, so usage, rate limits and cost land on the customer that caused them. You are not metering a shared key and re-billing it, and one heavy customer cannot exhaust another's quota.

Yes. Every call is logged per tenant with the call, the input and the result, so an output can be traced back to what produced it. That matters more here than in most integrations, because a generated answer or an extracted field cannot be reconstructed from the request alone.

A common starting point: invoke models using each customer's own AWS account, so their usage bills to them. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding AWS Bedrock does not change your per-connector cost. You can start free with 3 connected accounts.