Amazon Web Services · 2026-06-09 · major
AWS Bedrock Requires Mandatory 30-Day Anthropic Data Sharing for Claude Fable 5 and Mythos 5 — Customers Must Set Their Bedrock Account or Project to provider_data_share Before Invoking the Models, and Future Mythos-Class Releases Will Inherit the Same Policy
AWS Bedrock now blocks Claude Fable 5 and Mythos 5 unless customers opt their account or project into provider_data_share. Prompts and completions leave AWS, sit with Anthropic for up to 30 days, and the same rule applies to future Mythos-class models.
Mythos-class capability on Bedrock comes with a new condition: your prompts leave AWS and live with Anthropic for 30 days.
Key specs
| Retention days | 30 |
|---|---|
| Required mode | provider_data_share |
| Covered models | Claude Fable 5, Claude Mythos 5, future Mythos-class |
What is it?
A Bedrock platform change tied to the June 9 launch of Anthropic's Mythos-class models (Claude Fable 5 and the limited-availability Mythos 5). Bedrock now exposes a Data Retention API with four modes (default, provider_data_share, none, inherit), and Fable 5 and Mythos 5 declare allowed_modes of only provider_data_share. Any account or project still on default, none, or inherit sees those models return status: unavailable.
How does it work?
Customers set the mode via PUT /v1/data_retention at the account level or POST /v1/organization/projects/{id} at the project level. Once enabled, user prompts and Claude completions are stored by Anthropic for up to 30 days for trust-and-safety review, including human review and use in misuse pattern detection. When a Fable 5 request is rerouted to Opus 4.8 by a safety classifier, the fallback exchange is still retained under Fable 5's rules. AWS exposes a bedrock-mantle:DataRetentionMode IAM condition key so organizations can lock the mode via SCP.
Why does it matter?
Bedrock's pitch has been that customer data does not leave the AWS boundary. Fable 5 and Mythos 5 are the first Bedrock-hosted models to break that promise by design. Regulated buyers with zero-data-retention agreements lose access to the Mythos tier unless they request a per-account ZDR exception through their AWS account team. Anthropic frames the retention as the only way to catch cross-conversation misuse that single-prompt classifiers miss.
Who is it for?
Bedrock buyers, AWS solutions architects, compliance teams, AI procurement
Try it
curl -X PUT https://bedrock-mantle.us-east-1.api.aws/v1/data_retention -H "x-api-key: $BEDROCK_API_KEY" -d '{"mode":"provider_data_share"}'