Provision record
AWS Bedrock · AWS Service Terms · View original document ↗

Outposts physical security AWS commitments do not apply

High severity Explicit document language Common · 286 of 352 platforms
Stay ahead of the changes
Track AWS Bedrock and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF

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

Recent Activity

This document changed recently

Medium Sep 2, 2026

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 →
High Aug 18, 2026

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 →
Medium Jul 30, 2026

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 →

Clause Stability Stable

0
Changes
4
Months Monitored
Jul 10, 2026
First Seen
Jul 10, 2026
Last Seen
This clause type exists across 4260 other provisions on other platforms.

How other platforms handle this

Glassdoor Medium

We employ physical, electronic, and managerial measures to safeguard the data we collect online. However, no company can fully eliminate security risks, so we cannot make guarantees about any part of our services.

Datadog Medium

THE EXCLUSIONS AND LIMITATIONS IN THIS SECTION APPLY WHETHER THE ALLEGED LIABILITY IS BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR ANY OTHER BASIS...

Tinder Medium

TINDER ASSUMES NO RESPONSIBILITY FOR ANY CONTENT THAT YOU OR ANOTHER USER OR THIRD PARTY POSTS, SENDS, RECEIVES, AND/OR ACTS ON THROUGH OUR SERVICES, NOR DOES TINDER ASSUME ANY RESPONSIBILITY FOR THE IDENTITY, INTENTIONS...

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
Any AWS commitments in the Agreement that depend on AWS's operation of such physical security and access controls, or power, networking, and environmental conditions, do not apply to AWS Outposts or any Services running locally on AWS Outposts.

Excerpt from AWS Bedrock's AWS Service Terms

Applicable regulations

FTC Act Section 5
United States Federal

Provision details

Document information
Document
AWS Service Terms
Entity
AWS Bedrock
Document last updated
May 5, 2026
Tracking information
First tracked
July 9, 2026
Last verified
July 9, 2026
Record ID
CA-P-052350
Document ID
CA-D-00648
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
83d284e932cce0fb70f9c098a11039b78dc496bb03b15955d175ddd7d90142ee
Analysis generated
July 9, 2026 09:33 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: AWS Bedrock
Document: AWS Service Terms
Record ID: CA-P-052350
Captured: 2026-07-09 09:33:58 UTC
SHA-256: 83d284e932cce0fb…
URL: https://conductatlas.com/platform/aws-bedrock/aws-service-terms/provision/CA-P-052350/outposts-physical-security-aws-commitments-do-not-apply/
Accessed: Sept. 8, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
High
Categories

Other risks in this policy

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.

Frequently Asked Questions

What does AWS Bedrock's Outposts physical security AWS commitments do not apply clause do?

The clause states: “Any AWS commitments in the Agreement that depend on AWS's operation of such physical security and access controls, or power, networking, and environmental conditions, do not apply to AWS Outposts or any Services running locally on AWS Outposts.”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 286 platforms. See the full comparison.

Is ConductAtlas affiliated with AWS Bedrock?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by AWS Bedrock.