AWS Bedrock Error: AccessDeniedException When Invoking AWS Bedrock Models

#aws#bedrock#ai#cloudcomputing

A diagnostic guide for fixing AccessDeniedException and the common "IAM vs. Model Access" confusion.

Problem

You attempt to invoke a foundation model in AWS Bedrock and receive an error similar to:

AccessDeniedException: User is not authorized to perform bedrock:InvokeModel

The request fails immediately. No tokens are consumed. No model response is returned.

---

Clarifying the Issue

This error means IAM authorization is blocking the request, not the model, not the SDK, and not Bedrock itself.

AWS Bedrock enforces two separate permission gates:

1. IAM permissions allowing bedrock:InvokeModel.
2. Explicit model access enablement in the Bedrock console.

If either is missing, Bedrock will return AccessDeniedException.

---

Why It Matters

Bedrock errors surface early in AI pipelines:

• RAG systems fail silently.
• Lambda functions short-circuit.
• Retry logic wastes execution time.
• Developers misdiagnose the issue as SDK or region-related.

This Fix-It prevents hours of chasing the wrong root cause.

---

Key Terms

• AccessDeniedException: IAM or service-level authorization failure.
• bedrock:InvokeModel: Required action to call a Bedrock model.
• Foundation Model: Claude, Titan, Mistral, Llama, etc.
• Model Access: Per-account enablement inside the Bedrock console.

---

Steps at a Glance

1. Verify IAM policy includes bedrock:InvokeModel.
2. Confirm Bedrock model access is enabled (the "checkbox").
3. Check the exact model ID.
4. Validate region alignment.
5. Retest using AWS CLI.

---

Detailed Steps

1. Verify IAM Permissions

Your IAM role or user must explicitly allow model invocation.

Minimum required policy:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "bedrock:InvokeModel",
        "bedrock:InvokeModelWithResponseStream"
      ],
      "Resource": "*"
    }
  ]
}

📌 Note: If you are scoping resources, be aware that some Bedrock model ARNs are region-specific.

---

2. Enable Model Access in Bedrock Console

IAM alone is not sufficient. You must explicitly request access to models from third-party providers (Anthropic, Meta, etc.).

Navigate to:
AWS Console → Bedrock → Model access (bottom left sidebar)

Then:

1. Click Manage model access.
2. Check the boxes for the required models.
3. Click Save changes.
4. Wait for the status to change to Access granted (look for the green text).

📌 Timing: Anthropic models may take 5-10 minutes to propagate. If it doesn't change immediately, refresh the page.

---

3. Confirm the Model ID

Typos or deprecated IDs will still surface as AccessDeniedException.

Example valid IDs:

• anthropic.claude-3-sonnet-20240229-v1:0
• amazon.titan-text-express-v1

Double-check against:
Bedrock → Foundation models → Model details (Section: API request)

---

4. Check the Region

Bedrock is region-restricted. If your SDK is pointed at us-east-1 but you enabled models in us-west-2:

• IAM may succeed.
• Bedrock will still deny the request.

Ensure:

aws configure get region

Matches a supported Bedrock region where you have granted Model Access.

---

5. Validate with AWS CLI

Before blaming your application code, isolate the failure.

First, verify which identity you are actually using:

aws sts get-caller-identity

📌 Tip: If this shows a different user than expected, check your ~/.aws/credentials file or environment variables.

Second, run the invocation:

aws bedrock-runtime invoke-model \
  --model-id amazon.titan-text-express-v1 \
  --body '{"inputText":"Hello"}' \
  output.json

Diagnose the result:

• ✅ Works: Your application's SDK configuration.
• ❌ Fails (Wrong Identity): Local AWS credentials/profile.
• ❌ Fails (Correct Identity): IAM Policy (Step 1) or Model Access (Step 2).

---

Pro Tips

• Lambda Roles: These frequently lack Bedrock permissions even when local tests work.
• SCPs: Service Control Policies at the Organization level can block Bedrock silently.
• CloudTrail: Data events (like InvokeModel) may not appear unless specifically enabled, but AccessDenied errors often show up in standard management logs.

---

Conclusion

AccessDeniedException in AWS Bedrock is not mysterious—it’s procedural.

Once you align IAM permissions, Model Access, and Region configuration, Bedrock behaves predictably and consistently. This Fix-It closes the most common Bedrock onboarding failure cleanly.

---

Aaron Rose is a software engineer and technology writer at tech-reader.blog and the author of Think Like a Genius.