Customers accessing third-party foundation models through Bedrock are required to comply with each model provider's separately published acceptable use policies, which are incorporated by reference into the AWS Service Terms. These policies are maintained by providers including Anthropic, Meta, and Cohere and may be updated independently.
This analysis describes what AWS Bedrock's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision creates a dynamic compliance obligation that extends beyond the AWS agreement itself; customers must monitor and comply with third-party model provider policies that can be updated outside the AWS contract review cycle. Compliance teams must maintain awareness of each model provider's current terms for all models accessed in production deployments.
Interpretive note: The specific language reproduced here is a characterization based on the known structure of AWS Service Terms Section 50; the source document was truncated before the full Bedrock-specific provisions were visible.
The updated terms remove the explicit reference to a Data Processing Addendum governing Anthropic data transfers, though the requirement to obtain opt-in consent for Anthropic model use remains in place. For Kiro users, the revised language now explicitly states that abuse detection includes retention and potential human review of inputs and outputs when selecting certain models. Users of Anthropic models on Bedrock should verify opt-in consent mechanisms in service documentation to understand data handling practices.
View change record →The updated terms establish a new project-based service structure for AWS (new) users, effective August 17, 2026, with new rules governing team member access and content ownership. Users who enable spend limits agree that AWS may suspend their account or project access upon reaching their limit, and may permanently close the account or project if not reactivated within an unspecified timeframe. Contributed content by team members becomes the project owner's property and is subject to a nonexclusive irrevocable license granted to all project members. You can configure AI services opt-out policies through AWS Settings; project owners can manage team member permissions and access controls.
View change record →The updated terms now explicitly state that AWS IoT SiteWise Scenario Discovery is not designed for real-time vehicle control and cannot be used as the sole basis for determining vehicle safety or regulatory compliance. Organizations deploying this service must implement independent human monitoring and safety validation before using its outputs to support vehicle system decisions. The terms make clear that AWS assumes no responsibility for uses that violate these constraints.
View change record →Under this clause, customers are contractually bound not only by AWS's own acceptable use policy but also by the separate policies of each foundation model provider whose model is accessed through Bedrock. The agreement incorporates these third-party policies by reference, meaning changes to a model provider's policies automatically become binding contractual obligations.
How other platforms handle this
Use our Services in relation to any political campaign financing or for the purpose of influencing any election, other than sharing your own personal political opinions;
Host Content on our servers for any purpose other than for your use of the Service.
use TikTok Content...another user's content or generative AI-enabled features for commercial purposes unless permitted by TikTok USDS Joint Venture or the user, respectively...
"You must comply with all terms and conditions applicable to the third-party models available in Amazon Bedrock, which are incorporated by reference into these Service Terms. These terms are available on the Amazon Bedrock console or in the Amazon Bedrock documentation.Excerpt from AWS Bedrock's AWS Service Terms
(1) REGULATORY LANDSCAPE: This provision engages the FTC Act insofar as non-compliance with incorporated model provider policies could constitute a deceptive or unfair practice if customer-facing applications violate disclosed usage restrictions.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
This provision creates a dynamic compliance obligation that extends beyond the AWS agreement itself; customers must monitor and comply with third-party model provider policies that can be updated outside the AWS contract review cycle. Compliance teams must maintain awareness of each model provider's current terms for all models accessed in production deployments.
Under this clause, customers are contractually bound not only by AWS's own acceptable use policy but also by the separate policies of each foundation model provider whose model is accessed through Bedrock. The agreement incorporates these third-party policies by reference, meaning changes to a model provider's policies automatically become binding contractual obligations.
ConductAtlas has identified this type of provision across 282 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by AWS Bedrock.