The Bedrock model version is no longer available

WHAT IT MEANS

The model ID must be migrated

operation error Bedrock Runtime: InvokeModel, https response error StatusCode: 404, ResourceNotFoundException: This model version has reached the end of its life.

Bedrock model versions move through Active, Legacy, and End-of-Life states. After the end-of-life date, requests to that version fail and migration does not happen automatically.

NEXT CHECK

Find the replacement before retrying

1. Read the configured model ID and Region. Keep the exact identifier from the failed request; a display name is not a safe substitute for a base model or inference-profile ID.
2. Check the lifecycle status:

   aws bedrock get-foundation-model --model-identifier <model-id>

   Use the response's lifecycle fields and the active model catalog to select a supported replacement in the same Region and API.
3. Update and test the caller. Change the application or deployment configuration to the active model, confirm its request format, and then retry. Do not add permissions for this error.

AUTOMATE THE TRIAGE

Keep the handoff in your normal workflow

SAM Doctor recognizes the Bedrock lifecycle marker with high confidence and points at model migration. It runs locally; no AWS access, no log upload.

python -m pip install sam-doctor
sam-doctor diagnose deployment.log --format markdown

RELATED

Related errors

• Bedrock could not resolve the model identifier — check the current ID, Region, endpoint, and API.
• Bedrock model access has not been submitted — complete a provider's first-use form in the same account and Region.
• Bedrock request omitted messages — correct a model-specific request body before changing access.