AWS bedrock documentation change
Summary
Added clarification on data retention policies for different model versions, cross-region storage implications, and fallback behavior during safety classifier rejections.
Security assessment
The changes document data retention behaviors and storage locations for abuse detection, but don't fix a specific vulnerability. They enhance transparency about data handling practices.
Diff
diff --git a/bedrock/latest/userguide/data-retention.md b/bedrock/latest/userguide/data-retention.md index 5edd07d66..0d372ea4f 100644 --- a//bedrock/latest/userguide/data-retention.md +++ b//bedrock/latest/userguide/data-retention.md @@ -16,0 +17,4 @@ Your data retention configuration is yours to manage. If your account or project +###### Important + +There is no data retention change to models released before Claude Fable 5. AWS is committed to making sure that you are in full control over when and with whom your data is retained and shared. + @@ -23 +27 @@ Data retention is controlled by a **mode** rather than a simple on/off toggle: -`default` | AWS may retain the data for safety and abuse-prevention purposes. The model provider does not receive it. Actual retention depends on the model — consult the model's terms for specifics. On the Responses API, `store` defaults to `true` and may be set to either value. +`default` | Default means the data retention policy of the model applies. There is no change to previous model retention behavior; if ZDR applied previously, then ZDR still applies. Actual retention depends on the model — consult the model's terms for specifics. AWS may retain the data for safety and abuse-prevention purposes. The model provider does not receive it. On the Responses API, `store` defaults to `true` and may be set to either value. @@ -191,0 +196,13 @@ Or at the project level (if you want to limit provider data sharing to a specifi +###### Mixed-model projects + +Setting a project to `provider_data_share` does not mean all model traffic in that project is shared with the model provider. Each model's `allowed_modes` determines what actually happens to your data: + + * A model whose `allowed_modes` is `["provider_data_share"]` (e.g., Claude Fable 5) — data is retained and shared with the provider. + + * A model whose `allowed_modes` is `["default", "provider_data_share"]` (e.g., Claude Opus 4.8) — data is retained by AWS only. The model accepts `provider_data_share` as a valid mode but does not require data to leave AWS's boundary. + + * When a Claude Fable 5 request is declined by a safety classifier and the fallback credit is redeemed on Claude Opus 4.8, the fallback invocation follows Opus 4.8's data-handling rules, not Fable 5's. The Opus 4.8 response is not retained or shared with Anthropic. + + + + @@ -208,0 +226 @@ You can enforce a data retention policy across your organization using IAM polic + "bedrock-mantle:CreateProject", @@ -240,0 +259,2 @@ For models under `default` mode: data may be retained for abuse detection purpos +If cross-region inference is enabled for these models, retained inputs and outputs are stored in destination regions (i.e., the region where your inference request is processed). +