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 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 →The updated terms establish new restrictions on how AWS Capacity Reservations may be used. Specifically, customers purchasing On-Demand Capacity Reservations can no longer resell them to other parties, and AWS reserves the right to cancel the purchase or terminate running instances if the company suspects resale activity. For Capacity Blocks for ML, the grace period before instance termination increased from 30 minutes to 60 minutes for UltraServer instance types, allowing slightly more time to complete workloads. The Amazon Sidewalk qualification program was renamed and simplified, but the underlying security and operational requirements remain in effect.
View change record →The updated terms establish a formal framework for AWS Bedrock's free exploration services, clarifying the operational boundaries and responsibilities. AWS reserves the right to discontinue these services at any time without prior notice, meaning customers cannot rely on their continuation for production planning. Customers are solely responsible for testing, deploying, and maintaining any code, documents, or AI solutions AWS provides, including determining whether those solutions comply with applicable law. AWS retains the right to develop competing products based on content it creates during these engagements, though this does not override existing non-disclosure agreements. Customers are prohibited from requiring AWS personnel to sign additional terms as a condition of receiving free services, and any such documentation signed by AWS personnel is void.
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.