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 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 →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 282 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by AWS Bedrock.