AWS Bedrock · AWS Service Terms · View original document ↗

AWS Nitro System personnel have no access to customer Content

High severity High confidence Explicitdocumentlanguage Common · 299 of 352 platforms
Share 𝕏 Share in Share 🔒 PDF
Recent governance activity AWS Bedrock recorded 7 documented changes in the last 30 days.
Start monitoring updates
Monitor governance changes for AWS Bedrock Create a free account to receive the weekly governance digest and monitor one platform for governance changes.
Create free account No credit card required.

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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

This clause establishes a hard boundary on AWS Bedrock personnel access to customer Content, which is a significant security and confidentiality assurance for workloads running on Nitro System EC2 instances.

Recent Activity

This document changed recently

Medium Jun 30, 2026

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 →
Medium Jun 16, 2026

The updated terms establish new data-sharing mechanisms for users of Anthropic models on Amazon Bedrock. Specifically, AWS now explicitly authorizes notification to Anthropic of metadata present in requests sent to certain Anthropic products (e.g., Claude Code, computer use features), enabling Anthropic to conduct product-level usage attribution. Additionally, the terms introduce AWS WAF AI traffic monetization, which permits AWS to facilitate payment transactions between content publishers and buyers by sharing pricing, payment, and configuration information with payment providers and facilitators; the updated terms clarify that AWS does not provide regulated financial services and is not a party to fund flows, and that users' interactions with payment providers are governed by separate terms between the user and those parties. Users employing these features should review what metadata may be embedded in their requests and understand their own obligations to payment providers.

View change record →
Medium Jun 10, 2026

The updated terms now require users of certain Anthropic models to provide explicit consent for AWS to transfer their content and associated metadata to Anthropic for abuse detection and processing. Previously, abuse detection was described as an AWS-only internal function. The revised terms clarify that Bedrock stores service inputs and outputs for up to 30 days on identified models solely for abuse detection purposes. Users of Anthropic models can provide this consent through the opt-in mechanism described in the applicable service documentation, as stated in section 50.12.2.2 of the updated terms.

View change record →

Consumer impact (what this means for users)

Customers running workloads on AWS Nitro System EC2 instances can rely on the assurance that AWS Bedrock personnel cannot access their Content on those instances.

How other platforms handle this

ZipRecruiter Medium

authorize ZipRecruiter to connect your account to the account of a "Connected Site" (e.g., Google, LinkedIn, Monster, Facebook or Twitter), we may be able to access information you have provided to the Connected Site...

Baseten Medium

Category B: Personal information categories listed in the California Customer Records statute (Cal. Civ. Code § 1798.80(e))... bank account number, credit card number, debit card number, or any other financial information... Collected: Yes.

NVIDIA NIM Medium

telemetry information collected includes: (i) microservice settings, (ii) usage data and (iii) hardware environment.

See all platforms with this clause type →

Monitoring

AWS Bedrock has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.

Get Monitor Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
AWS personnel do not have access to Your Content on AWS Nitro System EC2 instances. There are no technical means or APIs available to AWS personnel to read, copy, extract, modify, or otherwise access Your Content on an AWS Nitro System EC2 instance or encrypted-EBS volume...

— Excerpt from AWS Bedrock's AWS Service Terms

Applicable regulations

CCPA/CPRA
California, USA
Connecticut Data Privacy Act Amendments
US-CT
ePrivacy Directive
European Union
FTC Act Section 5
United States Federal
GDPR
European Union
Indiana Consumer Data Protection Act
US-IN
Kentucky Consumer Data Protection Act
US-KY
Universal Opt-Out Mechanism Expansion 2026
US

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-053019
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-053019
Captured: 2026-07-09 09:33:58 UTC
SHA-256: 83d284e932cce0fb…
URL: https://conductatlas.com/platform/aws-bedrock/aws-service-terms/provision/CA-P-053019/aws-nitro-system-personnel-have-no-access-to-customer-content/
Accessed: July 12, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
High
Categories

Other risks in this policy

Related Analysis

Compliance Governance Intelligence

Need to monitor specific governance provisions?

Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.

Arbitration clauses AI governance Data rights Indemnification Retention policies
Get Compliance

Or start with Monitor →

Built from archived source documents, structured governance mappings, and historical version tracking.

Frequently Asked Questions

What does AWS Bedrock's AWS Nitro System personnel have no access to customer Content clause do?

This clause establishes a hard boundary on AWS Bedrock personnel access to customer Content, which is a significant security and confidentiality assurance for workloads running on Nitro System EC2 instances.

How does this clause affect you?

Customers running workloads on AWS Nitro System EC2 instances can rely on the assurance that AWS Bedrock personnel cannot access their Content on those instances.

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 299 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.