They say it's opt-in but since they are capable of agreeing to this, I am just waiting until they hide this opt-in into the regular ToS when asking for a new model access...
AWS Bedrock to require sharing data with Anthropic for Mythos and future models
11–20 of 274 posts
Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models
#12Got an email from Zed about the same this morning.
Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models
#13My thesis is that in software you don't want aggregators. They provide the promise of vendor neutrality, but it comes at the expense of increased supply chain compromise risk, small print technically legal data exfiltration.
Even in the happy case where nothing bad happens, you get a badly integrated product, because you integrate not against the actual vendor, but against a abstraction layer that commoditizes the actual product, effectively forcing you to either use the least common denominator of features, or circumventing the actual aggregation model itself with some kind of 'vendor_specific_parameters' parameter in the aggregator API.
My thesis is drop the vendor neutrality, and build your integration with the vendor directly.
Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models
#14The regulated-enterprise angle is the interesting part. Bedrock's whole pitch to those customers was "your data never leaves your AWS boundary" — that's the line that gets it through procurement and compliance reviews. A 30-day retention requirement where traffic crosses into the vendor's boundary quietly invalidates that, and for healthcare/finance/gov it's not a knob they can flip no matter how good the model is. This is exactly why we keep our LLM layer provider-agnostic with a self-hosted fallback (Ollama-class models) for data-sensitive paths — you eat a capability hit, but you keep the option of not sending regulated data anywhere. The risk TZubiri names is real: the moment you're reaching for "vendor_specific_parameters," the neutrality you bought the aggregator for is already gone.
Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models
#15This is not going to fly in EU.
I suspect they will simply not offer it, for as long as they maintain that it has to in fact fly. Anthropic appears to be somewhat principled here.
Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models
#16Same as for GitHub Copilot?
"For more on how Anthropic handles this data, see Anthropic’s commercial terms and data retention policy. Enabling the Claude Fable 5 policy constitutes acknowledgement of this requirement. Leaving it off keeps Claude Fable 5 unavailable to your organization."
https://github.blog/changelog/2026-06-09-claude-fable-5-is-g...
Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models
#17They want your data.
> After 30 days, the data is deleted automatically
Do we believe that?
> or we're legally required to keep it.
Aha - so, data is forever.
Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models
#18They want your data. > After 30 days, the data is deleted automatically Do we believe that? > or we're legally required to keep it. Aha - so, data is forever.
> Do we believe that?
If you don't believe them now why would you have believed them earlier when they said "no data is retained" ?
Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models
#19it's either this or playing x30 for a token, anyhow i physically can't write code again
Re: AWS Bedrock to require sharing data with Anthropic for Mythos and future models
#20Pretty sure this doesn't work for any regulated enterprise or government client. But AWS knows this, so I am curious why they'd agree to it.
> why they'd agree to it
that's obvious, but perhaps worth stating: it's worth it, demand for the model is unprecedented and the only downside for Anthropic if AWS rejected would be some revenue pushed a quarter away as they get Fable ready on their recently acquired compute from xAI and Google.