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 establish new data-sharing mechanisms for users of Anthropic models on Amazon Bedrock. Specifically, AWS now explicitly authorizes notification to Anthropic of metadata present in requests sent to certain Anthropic products (e.g., Claude Code, computer use features), enabling Anthropic to conduct product-level usage attribution. Additionally, the terms introduce AWS WAF AI traffic monetization, which permits AWS to facilitate payment transactions between content publishers and buyers by sharing pricing, payment, and configuration information with payment providers and facilitators; the updated terms clarify that AWS does not provide regulated financial services and is not a party to fund flows, and that users' interactions with payment providers are governed by separate terms between the user and those parties. Users employing these features should review what metadata may be embedded in their requests and understand their own obligations to payment providers.
View change record →The updated terms establish that customers operating Amazon RDS databases on end-of-life software versions are now required to upgrade to supported versions. The agreement authorizes AWS to scan extension code used with Trusted Language Extensions for security and performance purposes, and establishes that extension code constitutes customer content. AWS disclaims responsibility for service failures caused by extensions or end-of-life database software. If a customer does not upgrade before an engine reaches end of life, AWS may snapshot the customer's data and delete the instance or cluster running the unsupported software, after providing prior notice of the engine end-of-life date.
View change record →The updated terms establish new operational requirements for any organization using Amazon Connect Talent to make or inform employment decisions. Customers must now obtain legally adequate privacy notices and consents from job applicants before their data is processed by the service. The terms require customers to review all AI output before making hiring decisions, implement processes for applicants to request information about the AI's role in decisions, and ensure their use of the tool complies with applicable labor, anti-discrimination, disability, data privacy, AI, wiretap, recordkeeping, and biometrics laws. Customers can configure an AI services opt-out policy through AWS Organizations to prevent their data from being used to train or improve AWS AI technologies.
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 →Monitoring
AWS Bedrock has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 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. GDPR Art. 26 (joint controller) and Art. 28 (processor chain) may apply where end-user data is processed through Bedrock. CCPA §1798.140 (service provider obligations) is relevant for California end users. The EU AI Act's deployer obligations (Art. 26) apply where business customers deploy Bedrock as an AI system to end users in the EU.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
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.