- Newest
- Most votes
- Most comments
I have the same problem and it seems to be some kind of bug.
For some reason the POST request to /foundation-model-entitlement has a 400 response with the body {"message":"Operation not allowed"}.
It used to work previously but some backend change seems to have broken it.
Got the same issue. Any updates?
No. I'm still just using the 2nd AWS account I created for now
For me, I am getting this error with some models like Jurassic-2 Mid, Jurassic-2 Ultra : "operation not allowed" And for some models like "Cohere Embed Model" I get the mail, that you are subscribed. In either of these cases, I see the "access status" as "Available to request" only. FYI, I made all the requests in us-west-2 region (oregon) through my AWS management console.
Somebody, please help/enlighten. Tx
Same issue here. It worked before, now doesn't with 400 Bad Request/Operation Not Allowed response. Double checked permissions and tried various regions.
I managed to fix similar issue using a less known secret of AWS, sometimes a new account is in "limited mode" and then all kinds of services fail to work properly with no clear error message. You can usually solve this by starting a small EC2 (T instance) for about 15 minutes and then the account becomes operational and you should be able to request access.
Two days ago I wanted to create a CloudFront distribution and when clicking on "Create distribution" it told me that my account needs to be verified before I can add new CloudFront resources and that I should contact AWS Support.
I opened a case under the category "Account Activation, Account Verification" and today got a reply that they verified my account.
I then wondered if this problem might be related and indeed I am now once again able to request model access.
So the solution seems to be to request account verification.
You don't say how you're trying to access the model. I'd suggest double checking your region, and that you've enabled access to the Titan model in that region. [1]
[1] https://docs.aws.amazon.com/bedrock/latest/userguide/model-access.html
Thanks for your reply. I'm trying to access via the management console using a valid region. Out of desperation I created a new AWS account and everything worked absolutely fine. So, it looks like its something to do with my account but figure out what. They both have the same payment info
Relevant content
- asked 3 months ago
- asked 6 months ago
- asked 4 months ago
AWS OFFICIALUpdated a month ago- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 19 days ago
- AWS OFFICIALUpdated 2 years ago
I'm using the root account and got the same error for every model.
Same issue- tried with root account (that has Administrator access including AmazonBedrockFullAccess'. Tried with a user account that has marketplace permissions as well- I am able to request other models, but not the Amazon Titan models https://docs.aws.amazon.com/bedrock/latest/userguide/model-access.html#model-access-add