AWS quietly updated the Amazon Bedrock model card for Claude Fable 5 with a detail that deserves more attention than it's getting in the AI press. According to the official documentation, customers who want to run Anthropic's newest frontier model through AWS must explicitly opt into provider data sharing — and there's no console UI to do it at launch. Teams have to hit the Data Retention API directly. That's not a footnote. That's a compliance review item wearing a release note costume.

What the Model Card Actually Says

The requirements are spelled out in black and white on AWS's documentation page for Claude Fable 5. To use the model through Bedrock, customers must set their data retention mode to 'provider_data_share' via the Data Retention API. There's no checkbox buried in the console GUI — this is pure API territory at launch. AWS even admits it: there is no console UI path for this setting right now. That means whoever enables Claude Fable 5 in your organization needs API access and IAM permissions that match, which brings its own governance headaches.

Why This Changes the Calculus

Here's where insider context matters. A lot of teams pick Bedrock specifically because they want AWS's procurement controls, billing predictability, and — critically — data-handling guarantees baked into enterprise contracts. When a frontier model requires a different retention posture than the rest of your Bedrock deployment, you're no longer comparing models on equal footing. You're running two different compliance regimes under one roof. Your prompts, uploaded files, conversation logs, and potentially customer data could be flowing to Anthropic in ways that don't match your existing AWS account configuration.

Key Takeaways

  • Verify whether your AWS account already has provider_data_share enabled before assuming you're compliant
  • Who on your team can change Bedrock data retention settings? Lock that down first
  • Review internal policies about sharing prompts, files, and customer data with model providers
  • Compare Anthropic's direct API, Bedrock, or alternative routes for each workload — the trade-offs differ
  • Check whether existing customer commitments mention model-provider access or data retention terms

The Bottom Line

AWS made this requirement easy to miss because it's buried in a model card rather than shouted from the rooftop during the launch event. But if you're running Claude Fable 5 through Bedrock without understanding what 'provider_data_share' means for your data, you might be sending more to Anthropic than your compliance team signed off on. Read the cards. Configure the settings. Then ship.