Skip to main content
Amazon Bedrock Mantle is Amazon Bedrock’s Anthropic-native API surface. Unlike the standard Amazon Bedrock provider, Mantle speaks the Anthropic Messages API directly and authenticates with a bearer token rather than the AWS SigV4 credential chain, so no AWS CLI, named profile, or IAM Identity Center setup is needed on the device. In practice, Mantle is the Amazon Bedrock provider with a different runtime endpoint and a single bearer-token credential path.

​
Choose an authentication approach

Mantle supports a bearer token only. There is no in-app AWS sign-in or named-profile support for this provider; if you need per-user IAM Identity Center authentication, use the standard Amazon Bedrock provider instead.

​
Set up AWS

Enable Claude models in Amazon Bedrock for the region you will set as inferenceBedrockRegion, and obtain a Mantle bearer token for that account. See Set up AWS on the Amazon Bedrock page for the model-access step; the IAM Identity Center steps there are not needed for Mantle.

​
Prepare devices

​
Bearer token

No per-device preparation is required. Place the Mantle bearer token in the managed configuration as inferenceBedrockBearerToken. The app reaches bedrock-mantle.<region>.api.aws (or the host in inferenceBedrockBaseUrl if you set one). This host is included automatically in the Egress section of the in-app configuration window. The .api.aws zone has no FIPS endpoint variant.

​
Configure the app

Open the in-app configuration window (Developer → Configure Third-Party Inference…). In the Connection section, set Inference provider to Bedrock Mantle, then fill in the credentials card: If you set Bedrock base URL, provide the full SDK base URL including the /anthropic path (for example https://bedrock-mantle.us-east-1.api.aws/anthropic); it replaces the default bedrock-mantle.<region>.api.aws/anthropic endpoint. Under Models, add at least one Model list entry. Mantle has no model-list endpoint, so model discovery is not available and inferenceModels is required. Then click Export to produce a .mobileconfig (macOS) or .reg (Windows) file for your MDM. See Deploy with MDM for the export and deployment workflow.

​
Configuration keys

Mantle reuses the inferenceBedrock* key names. Only inferenceBedrockRegion, inferenceBedrockBearerToken, and inferenceBedrockBaseUrl apply; the other keys below (inferenceBedrockProfile, inferenceBedrockSso*, inferenceBedrockAwsDir, inferenceBedrockAwsCliPath, inferenceBedrockServiceTier) are ignored for this provider.
Tier availability varies by model and region. Reserved capacity uses a provisioned-throughput ARN as the model ID instead of this setting. Older bundled Claude Code CLI versions ignore this key.
You must also set inferenceModels. As with the standard Amazon Bedrock provider, server-side Web Search is not supported. See the Configuration reference.

​
What users experience

The app opens directly on first launch with no user action. Users are never prompted to sign in; re-authentication happens only when you rotate the bearer token in the managed profile.

​
Troubleshoot

To confirm which keys the app read and whether the provider settings validated, use Help → Troubleshooting → Generate Diagnostic Report, export the report, and check managed-config.txt and provider-status.txt; see Verifying the deployment for that workflow and the common causes when the app does not enter 3P mode. Application log locations are listed in Data storage and residency.