Change record
CA-X-002570
AWS Service Terms | AWS Bedrock
Entity
Date detected
June 2, 2026
Effective date
June 1, 2026
Severity
Direction
Neutral
Taxonomy
Disclosure requirement change
Changes
6 sentences modified

Impact Summary

Generated by a model from the captured document; not read by a person
Medium Neutral for users
Affected users
All users Aws bedrock customers Developers using bedrock-powered services

AWS Bedrock updated its abuse detection and content retention practices. Previously, the terms stated that automated abuse detection mechanisms "may apply" to services using Bedrock. The updated language specifies that Bedrock may store service inputs and outputs for up to 30 days to detect policy violations, and clarifies that if child sexual abuse material is detected, AWS may review the flagged content before reporting to authorities. The change also adds a reference to "applicable Service-specific documentation" for additional details and removes a reference to "related information sharing with third parties."

Stay ahead of the changes
Track AWS Bedrock and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF

What this means for you

Generated by a model from the captured document; not read by a person

The updated terms establish that AWS Bedrock may store your service inputs and outputs for up to 30 days for the sole purpose of detecting policy violations. Previously, the terms referenced abuse detection mechanisms without specifying retention duration or scope. The revised language also clarifies that if suspected child sexual abuse material is detected, AWS may review the flagged content before reporting to authorities. These changes make explicit what was previously stated in general terms, establishing a concrete data retention window and procedural clarity around content review.

Historical Context

This is the 2nd significant Disclosure Requirement Change change AWS Bedrock has made since ConductAtlas began monitoring.

ConductAtlas has recorded 6 material changes to this document (since May 2026).

2 of AWS Bedrock's significant changes have been classified as negative for consumers.

Key Clauses Affected

Generated by a model from the captured document; not read by a person
Data retention for abuse detection

AWS may store service inputs and outputs for up to 30 days for abuse detection purposes, establishing an explicit retention window previously stated only as 'may apply'.

CSAM review and reporting process

Clarifies that AWS may review flagged content to determine if it is CSAM before reporting to authorities, adding a procedural step to the reporting process.

Third-party information sharing disclosure

Removed reference to 'related information sharing with third parties' from abuse detection documentation reference.

Full clause-by-clause analysis available with Insight.
ⓘ

This change record describes what was added, removed, or modified in the document. Analysis reflects what the updated agreement states or permits. It does not constitute a legal determination about enforceability. Applicability may vary by jurisdiction. Methodology

Evidence Verification

✓ Verified
Previous Version
d60e9a71487307f8b041f5d0a466d87958df3404718291d4cb2b49f6b2cdec81
May 30, 2026 01:19 UTC
✓ Verified
Current Version
fe2ad8e475c7223be304443c27fca9f43ce70ae337fb8c79c8f36229294fb926
June 2, 2026 01:09 UTC
✓ Verified
Change Detected
June 2, 2026 01:09 UTC
✓
Analysis Methodology
✓ Verified
Source Document
https://aws.amazon.com/service-terms/
Record history

Wording edits to this record that do not change what it claims. Changes to a claim are published as corrections.

2026-10-11 · Feed summary edited · summary regenerated by summarize_events
Previous text
Added 30-day retention period for abuse detection; clarified review process for child safety reports.
2026-10-11 · Impact summary edited · summary regenerated by summarize_events
Previous text
The updated terms establish that AWS Bedrock may retain service inputs and outputs for up to 30 days solely to detect policy violations and harmful content, including potential child sexual abuse material. The revised language also specifies that if such material is detected, AWS may review the flagged content to confirm it before reporting to the National Center for Missing and Exploited Children or other authorities. These terms apply to 23 AWS services that incorporate Bedrock generative AI features.
2026-10-11 · Summary edited · summary regenerated by summarize_events
Previous text
AWS Bedrock updated its abuse detection and monitoring practices on June 2, 2026. The revised terms clarify that abuse detection mechanisms may now store service inputs and outputs for up to 30 days to detect policy violations, and specify that if child sexual abuse material is detected, AWS may review flagged content before reporting it to authorities. The prior language described automated detection without explicitly stating the 30-day retention period or the review step.
2026-10-07 · Change line edited · change line rewritten to the 2026-10-07 template: no detection date, no sentence counts
Previous text
AWS Bedrock updated their AWS Service Terms on June 02, 2026. Change detected: 6 sentence(s) modified. Document contained 1007 sentences after update.
Citation Record
Entity: AWS Bedrock
Document: AWS Service Terms
Record ID: CA-X-002570
Version: CA-V-003289
Captured: 2026-06-02 01:09:30 UTC
URL: https://conductatlas.com/change/2026-06-02-aws-bedrock-aws-service-terms-2570/
Accessed: Oct. 21, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
For legal and compliance teams

Institutional Analysis

Generated by a model from the captured document; not read by a person
Assessment

AWS has clarified its abuse detection practices by specifying a 30-day retention window for service inputs and outputs and detailing the review process for suspected CSAM. This change moves from general language ('automated abuse detection …

🔒 Full institutional analysis

Regulatory exposure, obligation change, escalation trigger, board-ready language, and recommended action for legal and compliance teams.

Unlock the full institutional analysis — Insight

ConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-X-002570.

Full Changes

View complete diff →

Document Context

Version history → Policy drift analysis → Document page →
Document
AWS Service Terms
Entity
AWS Bedrock
Captured
June 2, 2026
Source URL
https://aws.amazon.com/service-terms/
Other changes to AWS Service Terms
Previous change May 30, 2026
AWS Bedrock restructured its Amazon RDS service terms, reorganizing sections for RDS, RDS Custom, and database engine-specific provisions. The updated …
Medium Neutral
Next change Jun 23, 2026
AWS updated its Service Terms to add Amazon GuardDuty to the list of services that may incorporate generative AI features …
Low Neutral
View full version history →
More from AWS Bedrock
Oct 2, 2026 Low
AWS Service Terms

AWS Bedrock updated its Service Terms to add AWS Elemental Inference to the list of Indemnified Generative AI Services and …

Sep 12, 2026 Low
AWS Service Terms

AWS Bedrock updated its Service Terms document date from September 1, 2026 to September 11, 2026. The only substantive change …

Aug 21, 2026 Low
AWS Service Terms

AWS Bedrock updated its AWS Service Terms to expand the list of services covered under its Indemnified Generative AI Services …

Get the weekly coverage letter

Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.

Stay ahead of the changes

Track AWS Bedrock policy changes

Get alerted when this policy changes again, including what changed and why it matters.

All AWS Bedrock changes →