The terms prohibit customers from attempting to disable, bypass, or otherwise circumvent safety filters and content moderation mechanisms built into Amazon Bedrock or the foundation models accessible through the service. Violations of this restriction may constitute a breach of the Service Terms.
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 establishes an enforceable restriction on prompt engineering or technical approaches designed to override model guardrails, which is operationally significant for red-teaming, security research, and adversarial testing use cases that may require evaluation of model safety boundaries.
Interpretive note: The precise scope of what constitutes circumvention versus legitimate prompt engineering or model evaluation is not defined in the provision, creating operational ambiguity for security research and adversarial testing use cases.
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 →The updated terms establish that Reserved Cache Nodes and Amazon DynamoDB Reserved Capacity purchases are noncancellable obligations, and you will owe the full amount charged for the duration of the term you selected, even if the AWS agreement is terminated. For Kiro Free Tier users, the revised policy authorizes AWS to store your inputs for up to 60 days for purposes of detecting agreement violations and improving detection capabilities. You can review your existing reserved capacity commitments and their terms at any time, but the updated language does not provide an opt-out mechanism for this noncancellation obligation.
View change record →Language simplified from 'attempt to disable, circumvent, or otherwise undermine safety mechanisms, content filters, or use policies' to 'disable or circumvent any safety filters or mechanisms,' removing redundancy and focusing on core prohibited actions.
View full change record →Under this clause, customers are prohibited from using techniques designed to bypass or disable safety controls in Bedrock models, which applies to all customer accounts regardless of use case or stated purpose. Security researchers and organizations conducting AI red-teaming should assess whether their activities require separate authorization from AWS.
How other platforms handle this
You may not automatedly crawl or query the Services for any purpose or by any means (including, without limitation, screen and database scraping, spiders, robots, crawlers and any other automated activity with the purpose of obtaining information from the Services) unless you have received prior exp...
relate to transactions involving (f) the promotion of hate, violence, racial or other forms of intolerance that is discriminatory or the financial exploitation of a crime... (i) involve offering or receiving payments for the purpose of bribery or corruption.
You must not, and must not allow others to: Facilitate illegal or harmful activity through the End User Services; Cause harm to us or others through the End User Services;
Monitoring
AWS Bedrock has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"You may not use Amazon Bedrock to disable or circumvent any safety filters or mechanisms built into Amazon Bedrock or the models available in Amazon Bedrock.— Excerpt from AWS Bedrock's AWS Service Terms
(1) REGULATORY LANDSCAPE: This provision engages emerging AI safety regulatory frameworks including the EU AI Act's requirements for maintaining safety measures in AI systems and the NIST AI Risk Management Framework's guidelines on adversarial robustness. FTC guidance on responsible AI deployment is relevant where safety filter circumvention enables harmful consumer-facing outputs. (2) GOVERNANCE EXPOSURE: Medium. The prohibition is broadly worded and may affect legitimate AI security research activities; the absence of a carve-out for authorized security testing or red-teaming creates ambiguity for organizations conducting responsible disclosure activities. (3) JURISDICTION FLAGS: EU customers operating under the EU AI Act's high-risk AI system requirements may have independent legal obligations to test model safety boundaries; the interaction between this contractual prohibition and regulatory testing obligations requires assessment. (4) CONTRACT AND VENDOR IMPLICATIONS: Organizations conducting AI security assessments of Bedrock-based systems should review this provision before designing test methodologies. Penetration testing agreements with AWS may need to specifically address Bedrock safety mechanism testing. (5) COMPLIANCE CONSIDERATIONS: AI governance teams should document approved testing methodologies for Bedrock deployments that do not implicate this prohibition. Where red-teaming or adversarial testing is required by organizational AI governance policy or regulatory obligation, teams should seek written clarification from AWS regarding permissible testing scope.
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 establishes an enforceable restriction on prompt engineering or technical approaches designed to override model guardrails, which is operationally significant for red-teaming, security research, and adversarial testing use cases that may require evaluation of model safety boundaries.
Under this clause, customers are prohibited from using techniques designed to bypass or disable safety controls in Bedrock models, which applies to all customer accounts regardless of use case or stated purpose. Security researchers and organizations conducting AI red-teaming should assess whether their activities require separate authorization from AWS.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by AWS Bedrock.