ERROR REFERENCE
Bedrock has not received model use-case details
Amazon Bedrock rejected the model call because this account has not submitted the first-use details required by the model provider. This is an account access gate, not proof that a CloudFormation resource is gone.
WHAT IT MEANS
The account is not cleared to use this model
An error occurred (ResourceNotFoundException) when calling the ConverseStream operation: Model use case details have not been submitted for this account.Bedrock can report this from a post-deploy smoke test, Lambda, or other application call. The model may be listed while the account is still waiting for the provider's use-case form, so changing the template or deleting the stack is the wrong first move.
NEXT CHECK
Submit access details in the same account
- Confirm the caller and Region. Use the account, Region, and model ID from the failing request; model access is not a global setting shared by every account or Region.
- Open Bedrock model access. Follow the first-use form requested for that provider. For Anthropic models, complete the Anthropic use-case details form in the Bedrock console.
- Retry the same call after the access state updates. If it still fails, check the model ID and the caller's Region before changing IAM; this message is not an ordinary missing-resource error.
AUTOMATE THE TRIAGE
Keep the check in your normal workflow
SAM Doctor recognizes the Bedrock first-use access marker with medium confidence and points at the account-level form. Runs locally; no AWS access, no log upload.
python -m pip install sam-doctor
sam-doctor diagnose deployment.log --format markdownRELATED
Related errors
- Lambda invoke target not found - a post-deploy check aimed at the wrong function or qualifier.
- ECS Exec agent could not start - task launch, SSM messaging, network, and filesystem prerequisites.
- CloudFormation resource creation or update failed - the resource-level fallback when the deployment itself reports a failed event.