Enable Anthropic Claude models on Amazon Bedrock

Enable Anthropic Claude models on Amazon Bedrock

If your RunsOn jobs need to invoke Anthropic Claude models through Amazon Bedrock, there are two separate steps to be aware of:

  1. Submit the Anthropic first-time-use form once.
  2. Invoke the model from an account or role that has enough AWS Marketplace permissions to auto-create the model agreement.

AWS documents this behavior here: Request access to models - Amazon Bedrock ↗. In short, Anthropic requires first-time use-case details, and for third-party Bedrock models, the first invocation can automatically create the AWS Marketplace/SaaS agreement if the caller has the right permissions.

Example flow:

AWS_PROFILE=management aws bedrock put-use-case-for-model-access \
  --region us-east-1 \
  --form-data "$(printf '%s' '{
    "companyName": "Your Company",
    "companyWebsite": "https://example.com",
    "intendedUsers": "0",
    "industryOption": "Technology",
    "otherIndustryOption": "",
    "useCases": "Internal software engineering and operational automation using Anthropic Claude models through Amazon Bedrock, including code generation, code review, debugging, documentation, log analysis, and AI-assisted developer workflows."
  }' | base64)"

Notes:

  • intendedUsers: "0" means internal users. AWS also supports external or both, depending on your use case.
  • Submit this from the AWS Organization management account if you want the Anthropic FTU form to be inherited by member accounts.
  • This does not by itself create the per-account AWS Marketplace model agreement.

Then, from the account where RunsOn jobs will invoke Bedrock, use a role/profile that has the required Bedrock invoke permissions and enough AWS Marketplace permissions for first use:

{
  "Effect": "Allow",
  "Action": [
    "aws-marketplace:Subscribe",
    "aws-marketplace:ViewSubscriptions"
  ],
  "Resource": "*"
}

AWS also documents aws-marketplace:Unsubscribe as part of model-access management. For a tightly scoped production policy, restrict these permissions according to your organization controls.

Trigger first use with a minimal invocation:

AWS_PROFILE=runtime aws bedrock-runtime converse \
  --region us-east-1 \
  --model-id us.anthropic.claude-sonnet-4-6 \
  --messages '[{"role":"user","content":[{"text":"Reply with OK only."}]}]' \
  --inference-config '{"maxTokens":8,"temperature":0}' \
  --query 'output.message.content[0].text' \
  --output text

If the role lacks Marketplace permissions, the first invocation can fail with an error mentioning:

aws-marketplace:ViewSubscriptions
aws-marketplace:Subscribe

After invoking once with sufficient permissions, Bedrock auto-creates the Anthropic SaaS agreement for that account. Subsequent calls from normal Bedrock invocation roles should work without needing those Marketplace subscription permissions again.

You can check availability with:

AWS_PROFILE=runtime aws bedrock get-foundation-model-availability \
  --region us-east-1 \
  --model-id anthropic.claude-sonnet-4-6

In our test, after first invoking with enough privileges, this model worked successfully from the runtime account:

OK

Useful model/profile IDs:

anthropic.claude-sonnet-4-6
us.anthropic.claude-sonnet-4-6
global.anthropic.claude-sonnet-4-6
anthropic.claude-opus-4-6-v1
us.anthropic.claude-opus-4-6-v1
global.anthropic.claude-opus-4-6-v1

Last updated: April 28, 2026

View original discussion ↗