Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Bedrock InvokeModel returns “Operation not allowed” in us-east-2 after “Model access” page retirement

1

Looking for guidance on Bedrock serverless model authorization in us-east-2.

tldr;

  • Our account was recently recreated.
  • Our account in us-east-2 can’t invoke Bedrock serverless models; all calls return ValidationException: Operation not allowed.
  • aws bedrock get-foundation-model-availability reports authorizationStatus: NOT_AUTHORIZED for amazon.titan-embed-text-v2:0, cohere.embed-v4:0, and common Anthropic Claude models.
  • This is not IAM or VPC: EC2 role allows bedrock:InvokeModel; same error from admin user; endpoints are in place.
  • It worked Monday and I have proof.

Context

Region: us-east-2

  • Workloads: On-demand embeddings (Titan v2) + Claude summarization
  • Network: Private VPC (no egress) with interface endpoints for bedrock, bedrock-runtime, kms, logs, ssm, ssmmessages, ec2messages (rds-data/secretsmanager also present for DB usage)
  • Compute: AL2023 EC2 (SSM-managed), invoking via instance role
  • Storage: S3 SSE-KMS, VPCE-only bucket policies
  • IAM: Role allows bedrock:InvokeModel on target model ARNs (see snippet below). No known SCP denies.
  • What worked last week: We successfully ran Titan Text Embeddings V2, Claude Sonnet 4 and produced an artifact.

Current issue

  • All serverless InvokeModel calls now fail with:
  • ValidationException: “Operation not allowed”
  • The Bedrock console “Model access” page states access is auto-enabled, but the API indicates we are not authorized for multiple models in us-east-2.

Repro (CLI)

  • Model present and ACTIVE:
  • aws bedrock list-foundation-models --region us-east-2 --query 'modelSummaries[?modelId==amazon.titan-embed-text-v2:0]'

Authorization status (authoritative):

  • aws bedrock get-foundation-model-availability --region us-east-2 --model-id amazon.titan-embed-text-v2:0
  • Returns: "authorizationStatus": "NOT_AUTHORIZED"
  • Minimal InvokeModel test (both forms tried):
  • aws bedrock-runtime invoke-model --region us-east-2 --model-id amazon.titan-embed-text-v2:0 --content-type application/json --accept application/json --body '{"inputText":"hello world"}' out.json
  • aws bedrock-runtime invoke-model --region us-east-2 --model-id amazon.titan-embed-text-v2:0 --content-type application/json --accept application/json --body '{"inputText":["hello world"]}' out.json
  • Both return: ValidationException: Operation not allowed
  • Other providers also show NOT_AUTHORIZED and same error (in us-east-2):
  • cohere.embed-v4:0
  • Anthropic Claude (e.g., anthropic.claude-3-5-sonnet-20241022-v2:0)
  • IAM checks (summarized)

EC2 role is allowed for InvokeModel (simulated allowed). Example policy shape we use:

  • Action: bedrock:InvokeModel, bedrock:InvokeModelWithResponseStream
  • Resource: arn:aws:bedrock:us-east-2::foundation-model/amazon.titan-embed-text-v2:0 (plus other regions as needed)
  • VPC endpoint policies allow the role to call bedrock:InvokeModel.
  • From my workstation (admin user) I see the same “Operation not allowed”, which suggests this is not a VPC/endpoint policy issue.

What I’m looking for

  • With the retirement of the “Model access” page (which says “serverless foundation models are now automatically enabled”), what is the correct enablement path to get serverless InvokeModel authorized for:
  • amazon.titan-embed-text-v2:0 (primary need)
  • Optional: Anthropic Claude (e.g., anthropic.claude-3-5-sonnet-20241022-v2:0) and Cohere embed (cohere.embed-v4:0)
  • Is there a new backend authorization step required per account/region post-retirement?
  • If there’s a self-serve route in the console, where is it now surfaced for Amazon models (non-Anthropic)?

Thanks in advance for any pointers.

Topics
Machine Learning & AIGenerative AI on AWS
Tags
IAM PoliciesAmazon Bedrock
Language
English

asked a year ago444 views

3 Answers
0

Based on the information provided, it appears you're experiencing an authorization issue with Amazon Bedrock models in us-east-2 after the retirement of the "Model access" page.

While Amazon Bedrock has simplified model access by eliminating the requirement for manual enablement of individual models, there are still some authorization steps that might be needed, especially for a recently recreated account.

For the "NOT_AUTHORIZED" status and "Operation not allowed" error you're encountering, here are some potential solutions:

  1. Contact AWS Support: When you receive a 403 error with the cause "Your account is not authorized to access this model," the recommended solution is to contact AWS Support for further details. This is especially important since your account was recently recreated, which might require specific backend authorization steps from AWS.

  2. Check for Organization-level restrictions: If your account is part of an AWS Organization, there might be Service Control Policies (SCPs) restricting access to Bedrock models in specific regions. Even though you mentioned no known SCPs deny access, it's worth double-checking with your organization administrators.

  3. IAM Permissions: While you've confirmed your IAM role has the necessary permissions, ensure you have all the required permissions for Bedrock operations. Some users have reported success with a broader set of permissions including:

  • bedrock:InvokeModel
  • bedrock:ListInvocations
  • bedrock:ListSessions
  • bedrock:GetSession
  • bedrock:RenderPrompt
  • bedrock:CreateInvocation
  • bedrock:CreateSession

  1. Region Availability: Confirm that the specific models you're trying to use are available in us-east-2. Some models might only be available in specific regions. For example, certain Mistral models are only available in us-west-2 and not in us-east-1.

  2. First-time Usage Form: For Anthropic models specifically, you might need to submit a first-time usage form. This can be completed at the organization management account level for child accounts within an organization.

Since you mentioned that this worked previously and you have proof, and given that your account was recently recreated, this strongly suggests an account-specific authorization issue that might require AWS Support intervention to resolve.
Sources
Bedrock InvokeModel/Converse with Managed Prompt - AccessDenied | AWS re:Post
Troubleshooting Amazon Bedrock API Error Codes - Amazon Bedrock
Simplified model access in Amazon Bedrock | AWS Security Blog
i'm not able to invoke aws bedrock model locally | AWS re:Post

answered a year ago

  • Warren Hammond
    a year ago

    I don't have a support contract with AWS so I can't submit a support request. I am an independent Amazon Authorized Instructor who needs to be able to demonstrate Bedrock. I do not have the budget to sign up for support.

0

Hi,

Look at the announcement: https://aws.amazon.com/about-aws/whats-new/2025/10/amazon-bedrock-automatic-enablement-serverless-foundation-models/

While you can quickly begin using serverless foundation models from most providers, 
Anthropic models, although enabled by default, still require you to submit a one-time 
usage form before first use. You can complete this form either through the API or through 
the Amazon Bedrock console by selecting an Anthropic model from the playground. When 
completed through the AWS organization management account, the form submission 
automatically enables Anthropic models across all member accounts in the organization.

Did you submit the form that is still required for Anthropic models as per the quote above?

Best,

Didier

EXPERT

answered a year ago

0

Thanks, Didler! We'll try that. We were approved for the anthropic models before the change, but we'll try again. Also, do you think we should be having trouble with the non-anthropic models; Titan and cohere embedding models?

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content