Publishers on Bedrock
Guild routes six publishers through Bedrock. Models marked with a region list are only in those regions. The rest are in all four supported regions.
Guild refreshes this list from Bedrock’s catalog every day, so it can change. It keeps only models that are active and produce text. Bedrock also lists Llama models, but Guild doesn’t route Meta models through Bedrock, and Gemini models aren’t on Bedrock.
Connect Bedrock
1
Start the credential
Click Access & setup in the left nav, then Models & providers. Click Add API key and choose AWS Bedrock from the menu.
2
Copy Guild's values
Give the credential a Name. Under Add these to your role, copy the Principal and the External ID. Keep the dialog open.
3
Create the role in AWS
In your AWS account, create an IAM role that can invoke the Bedrock models you want. Set its trust policy to let the Principal assume it, and match the External ID with a
StringLike condition.4
Enter the role and region
Paste the role’s ARN, such as
arn:aws:iam::123456789012:role/GuildBedrock, into IAM role ARN. Enter the region to call Bedrock in, such as us-east-1, under AWS region. Pick a region that has the models you want.5
Choose publishers
Under Models, check each publisher this credential should reach, and keep or change each default model. Then click Add Key.
:* because Guild appends the credential’s ID when it assumes the role. One role can serve every Bedrock credential on the same Guild account.
If the dialog says the deployment has no AWS role configured, Bedrock can’t be connected on that deployment yet.
Regions and model IDs
A Bedrock credential names one region. Guild supportsus-east-1, us-east-2, us-west-1, and us-west-2. A model that isn’t in your credential’s region can’t be routed through it, so add a credential for another region if you need one. Write canonical model names, such as claude-sonnet-4-6 or deepseek-r1, in policies and llmPreferences. Guild maps each one to its Bedrock ID, such as us.anthropic.claude-sonnet-4-6 or us.deepseek.r1-v1:0.
When a model has an inference profile, Guild prefers the profile for your region’s geography, us., over a global. profile. A global profile can serve a request from another continent, which may break data-residency terms or IAM policies scoped to regional ARNs. Guild uses a global profile only when AWS publishes nothing narrower.
Audit calls in CloudTrail
Each call Guild makes assumes your role with a session name ofguild-<task-id>. To trace a Bedrock call back to the Guild task that made it, look for that session name in CloudTrail.
Related pages
- Models & providers for credentials, model policies, and the daily token limit
- Fireworks AI and OpenRouter, the other third-party providers