Claude Fable 5 on Bedrock appears to require provider data sharing

#aws #bedrock #ai #anthropic

Claude Fable 5 on Bedrock appears to require provider data sharing

AWS's Claude Fable 5 model card for Amazon Bedrock says customers must opt in to provider data sharing by setting Bedrock's data retention mode to provider_data_share through the Data Retention API. That is worth tracking for the daily AI news roundup because it changes the privacy/compliance shape of using Anthropic's newest model through Bedrock, but it is not a clean immediate-publish item on its own.

What changed

The Bedrock model card for Claude Fable 5 says:

Claude Fable 5 is available through Amazon Bedrock as an Anthropic model.
To use it, customers "must opt in to provider data sharing".
The required setting is Bedrock data retention mode provider_data_share.
AWS says there is no console UI for the setting at launch; teams have to use the Data Retention API.

This matters because many teams choose Bedrock specifically for AWS procurement, controls, and data-handling expectations. If a frontier model requires a different data-retention mode than the rest of a team's Bedrock usage, that is a compliance review item, not just a model-selection detail.

Why builders should care

For founders and engineering teams, the practical question is simple: do not assume every Bedrock model has the same data-handling posture.

Before enabling Claude Fable 5 in production, teams should check:

whether their AWS account has opted into provider data sharing;
who is allowed to change Bedrock data retention settings;
whether internal policies allow prompts, files, logs, or customer data to be shared with the model provider;
whether Anthropic's direct API, Bedrock, or another provider route has the right trade-off for the workload;
whether existing customer commitments mention model-provider access or retention.

Why this is not an immediate breaking article

This is important builder context, but it is narrower than a new model launch, platform-wide outage, pricing shock, or broad policy change. It also overlaps with the already-covered Claude Fable 5 / Mythos 5 access issue. Best treatment: include it in the daily roundup with a clear note for AWS/Bedrock users.