CloudConsole

IAM policy: invoke one Amazon Bedrock model

Updated 17 November 2026 · How we write and check guides

Short answer

Allow the bedrock:InvokeModel action, and its streaming twin InvokeModelWithResponseStream, on the model you use. With a cross-Region inference profile (model IDs starting eu. or us.), allow the profile ARN and the underlying foundation-model ARN in each Region the profile can route to. The Converse and ConverseStream APIs use the same two permissions.

Policy diagram: 2 statement(s); first Allow bedrock:InvokeModel, bedrock:InvokeModelWithResponseStream on bedrock…
The policy on this page drawn statement by statement: who it applies to, the actions, the resources and any condition.

The policy

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "InvokeViaEuProfile",
      "Effect": "Allow",
      "Action": [
        "bedrock:InvokeModel",
        "bedrock:InvokeModelWithResponseStream"
      ],
      "Resource": "arn:aws:bedrock:eu-west-2:123456789012:inference-profile/eu.amazon.nova-lite-v1:0"
    },
    {
      "Sid": "ModelBehindTheProfile",
      "Effect": "Allow",
      "Action": [
        "bedrock:InvokeModel",
        "bedrock:InvokeModelWithResponseStream"
      ],
      "Resource": "arn:aws:bedrock:*::foundation-model/amazon.nova-lite-v1:0",
      "Condition": {
        "StringEquals": {
          "bedrock:InferenceProfileArn": "arn:aws:bedrock:eu-west-2:123456789012:inference-profile/eu.amazon.nova-lite-v1:0"
        }
      }
    }
  ]
}

What each statement allows

  • InvokeViaEuProfile: calls with modelId set to eu.amazon.nova-lite-v1:0. A cross-Region inference profile lets Bedrock serve the request from any of several Regions in the geography for better throughput.
  • ModelBehindTheProfile: Bedrock also checks permission on the foundation model in whichever Region serves the request. Foundation-model ARNs have no account ID, and the * Region covers wherever the profile routes. The bedrock:InferenceProfileArn condition means the model can be reached only through this profile, not called directly in any Region.

Both statements allow streaming. The Converse API is authorised as bedrock:InvokeModel, and ConverseStream as bedrock:InvokeModelWithResponseStream; there is no separate Converse permission.

Attach and test

aws iam put-role-policy --role-name summariser-lambda \
  --policy-name bedrock-nova-lite --policy-document file://bedrock.json

aws bedrock-runtime converse --model-id eu.amazon.nova-lite-v1:0 \
  --messages '[{"role":"user","content":[{"text":"Say hello"}]}]' \
  --region eu-west-2 --profile summariser-lambda

Variations

  • Model in one Region, no profile: a single statement on arn:aws:bedrock:eu-west-2::foundation-model/<model-id>, if that model is offered in-Region.
  • Several models: list each ARN. Avoid foundation-model/* in production; new, more expensive models appear under it automatically.
  • Guardrails: add bedrock:ApplyGuardrail on the guardrail ARN if you call it separately.
  • Agents, knowledge bases and flows have their own actions (bedrock:InvokeAgent, bedrock:InvokeFlow, and so on) and their own service roles.
  • Listing models in a UI: bedrock:ListFoundationModels and bedrock:ListInferenceProfiles on "*".

Find the right ARNs

List the inference profiles available in your Region to get the exact profile ID and ARN, then check which model IDs it routes to:

aws bedrock list-inference-profiles --region eu-west-2 \
  --query 'inferenceProfileSummaries[].[inferenceProfileId,inferenceProfileArn]' --output text

aws bedrock list-foundation-models --region eu-west-2 \
  --query 'modelSummaries[].modelId' --output text

Common mistakes

  • Only allowing the foundation model while the code uses an eu. or us. model ID: AccessDenied names the inference profile.
  • Only allowing the profile: AccessDenied names a foundation model in another Region.
  • Model access not set up: depending on the model and the account, you may need to enable it in the Bedrock console, and third-party models may require accepting the provider's terms (which uses AWS Marketplace permissions) before the first call. That error differs from an IAM denial; it says the model isn't accessible.
  • bedrock:* on "*": includes creating provisioned throughput, which is billed whether you use it or not.

Questions

What IAM permission does the Bedrock Converse API need?

Converse needs bedrock:InvokeModel and ConverseStream needs InvokeModelWithResponseStream, both on the model or inference profile you call.

Why do I get AccessDenied with a cross-Region inference profile?

You need permission on both the inference profile ARN and the foundation-model ARN in each Region it can route to.

When this happens away from your desk

Model calls are billed per token, so a runaway loop shows up as cost before anything else. A phone that shows today's Bedrock spend and the calling function's errors catches that early.

About the app → · Download on the App Store

Sources