You are not permitted to take the outputs you receive from Amazon Bedrock and use them to build or train an AI model that would compete with Bedrock or other AWS services.
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 directly restricts how enterprise AI teams can use inference outputs in their internal model development and fine-tuning workflows, which may affect standard MLOps practices that aggregate model responses into training datasets.
Interpretive note: The scope of what constitutes a service that competes with Amazon Bedrock or AWS is not exhaustively defined in the document, creating interpretive uncertainty about edge 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 →The terms prohibit using Bedrock model outputs in pipelines that train or develop competing AI foundation models; organizations must audit whether their internal AI development workflows that incorporate Bedrock outputs are compliant with this restriction.
How other platforms handle this
Microsoft reserves the right to restrict the export of data that may compromise the security of the services or Microsoft's intellectual property.
Datadog reserves the right, but does not assume the obligation, to investigate any violation of these Terms or misuse of the Site.
Pharmaceutical products
"You may not use the Services to develop foundation models or other large scale models that compete with Amazon Bedrock or any other AWS Service.Excerpt from AWS Bedrock's AWS Service Terms
(1) REGULATORY LANDSCAPE: This restriction is primarily a contractual obligation rather than one directly mandated by regulation.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Buried in Robinhood's customer agreement is broad authority to close your positions, suspend your account, and force arbitration. Here is what it actually says.
Stripe's terms authorize fund reserves, payout withholding, and account termination. Here is what the agreement states and what business owners should review.
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 directly restricts how enterprise AI teams can use inference outputs in their internal model development and fine-tuning workflows, which may affect standard MLOps practices that aggregate model responses into training datasets.
The terms prohibit using Bedrock model outputs in pipelines that train or develop competing AI foundation models; organizations must audit whether their internal AI development workflows that incorporate Bedrock outputs are compliant with this restriction.
ConductAtlas has identified this type of provision across 263 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by AWS Bedrock.