Amazon Bedrock
global.writer.palmyra-x5-v1:0 model retirement
Stops workingSubscribe to Amazon BedrockShare
Calls to the model global.writer.palmyra-x5-v1:0 on Amazon Bedrock stop working on March 21, 2027.
In Amazon Bedrock's words
Model provider: Writer; Model name: Palmyra X5; Model ID: writer.palmyra-x5-v1:0; Regions: us-east-1, us-east-2, us-west-1, us-west-2; Legacy date: September 21, 2026; EOL date: March 21, 2027; Public extended access start date: —
Facts
- API
- Amazon Bedrock
bedrock.us-east-1.amazonaws.com - Model
global.writer.palmyra-x5-v1:0- Kind
- Model retirement
- Announced
- September 21, 2026
- Takes effect
- March 21, 2027
- Calls after that day
- Fail
- Source
- Deprecations page
- Last updated
- Verified
- , against Amazon Bedrock's own pages
Questions
When does global.writer.palmyra-x5-v1:0 shut down?
Calls to the model global.writer.palmyra-x5-v1:0 on Amazon Bedrock stop working on March 21, 2027.
What happens to calls after March 21, 2027?
They fail from that day.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Amazon Bedrock 10
-
apac.writer.palmyra-x5-v1:0Model retirement Stops workingin 135 days -
au.writer.palmyra-x5-v1:0Model retirement Stops workingin 135 days -
ca.writer.palmyra-x5-v1:0Model retirement Stops workingin 135 days -
eu.writer.palmyra-x5-v1:0Model retirement Stops workingin 135 days -
jp.writer.palmyra-x5-v1:0Model retirement Stops workingin 135 days -
us-gov.writer.palmyra-x5-v1:0Model retirement Stops workingin 135 days -
us.writer.palmyra-x5-v1:0Model retirement Stops workingin 135 days -
writer.palmyra-x5-v1:0Model retirement Stops workingin 135 days -
apac.twelvelabs.marengo-embed-3-0-v1:0Model retirement Stops workingin 136 days -
apac.twelvelabs.pegasus-1-2-v1:0Model retirement Stops workingin 136 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before March 21, 2027.