If you build an application using Bedrock and offer it to other people, you are legally responsible for making sure those users also follow all of AWS's rules and the model providers' rules.
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 allocates compliance monitoring obligations to the customer tier rather than AWS, creating a contractual chain where customers serve as the compliance intermediary between AWS and downstream users. This structure establishes clear responsibility boundaries for policy enforcement across the service chain.
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 →Businesses deploying Bedrock-powered applications bear full liability for their customers' compliance with AWS and model provider policies, which requires implementing monitoring, enforcement mechanisms, and compliant end-user terms of service.
Cross-platform context
See how other platforms handle Customer Downstream End-User Compliance Obligation and similar clauses.
Compare across platforms →"You are responsible for ensuring that your end users comply with the AWS Acceptable Use Policy, these Service Terms, and the applicable model provider use policies. You must have terms of service with your end users that are consistent with these Service Terms.Excerpt from AWS Bedrock's AWS Service Terms
REGULATORY FRAMEWORK: This provision creates a private contractual enforcement chain that intersects with consumer protection law in all jurisdictions where the customer's end users are located.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Search "[your state] attorney general consumer complaint" to find your state's direct complaint form
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 allocates compliance monitoring obligations to the customer tier rather than AWS, creating a contractual chain where customers serve as the compliance intermediary between AWS and downstream users. This structure establishes clear responsibility boundaries for policy enforcement across the service chain.
Businesses deploying Bedrock-powered applications bear full liability for their customers' compliance with AWS and model provider policies, which requires implementing monitoring, enforcement mechanisms, and compliant end-user terms of service.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by AWS Bedrock.