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 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 →The removal of this prohibition on bypassing AI safety mechanisms eliminates an important guardrail against adversarial use of AI services.
View full 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
interfere with or circumvent Product usage limits or Scope of Use restrictions
You may not display any personal contact, banking, or peer-to-peer payment information, whether in relation to you or any other person (for example, names, home addresses or postcodes, telephone numbers, email addresses, URLs, credit/debit card...)
Bypass or ignore instructions contained in our robots.txt file that controls automated access to portions of our Services;
"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.
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 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.
ConductAtlas has identified this type of provision across 281 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by AWS Bedrock.