- Newest
- Most votes
- Most comments
Based on your description, there are several potential reasons why all Bedrock models appear disabled when trying to request access:
-
Account approval status: Even as a root user with all IAM permissions, your AWS account may need specific approval for Amazon Bedrock usage. This is separate from IAM permissions.
-
Regional restrictions: While you correctly chose US East (N. Virginia), which is a supported region for Bedrock, some models have specific regional availability.
-
Request process issues: Some users have reported experiencing "operation not allowed" errors when submitting model access requests, even as root users.
-
Account limitations: If you're using a new account or one with certain restrictions, this might affect your ability to request model access.
-
Marketplace restrictions: If you're using AWS Organizations, there might be central marketplace restrictions blocking access.
To resolve this issue:
-
Try contacting AWS Support directly. For Bedrock access issues that can't be resolved through the console, you'll need to submit a support request. AWS may need to verify you're a corporate customer and grant access based on applicable policies.
-
If you're part of an AWS Organization, check if there are marketplace restrictions and ensure Bedrock products are approved.
-
Some users have reported that their Bedrock quota was set to 0, which could cause similar issues. This would require AWS Support intervention to resolve.
This appears to be an issue that cannot be resolved solely from your side and likely requires AWS Support assistance.
Sources
All Bedrock models are unavailable | AWS re:Post
Unable to request any model access in AWS bedrock service | AWS re:Post
Bedrock Model "Unavailable" for all Regions | AWS re:Post
"Invalid Model Identifier Error in Amazon Bedrock and Unable to Request Specific Models" | AWS re:Post
Relevant content
asked a year ago
asked 2 years ago
