Change record
CA-X-002499
AWS Service Terms | AWS Bedrock
Entity
Date detected
May 30, 2026
Effective date
May 29, 2026
Severity
Direction
Neutral
Taxonomy
Disclosure requirement change
Changes
+13 sentences added · −2 sentences removed · 14 sentences modified

Impact Summary

Generated by a model from the captured document; not read by a person
Medium Neutral for users
Affected users
Aws customers using amazon rds Aws customers using rds custom Aws customers using oracle database Aws customers using microsoft sql server Aws customers using ibm db2

AWS Bedrock restructured its Amazon RDS service terms, reorganizing sections for RDS, RDS Custom, and database engine-specific provisions. The updated terms add new sections on Trusted Language Extensions, Engine End of Life (EOL) management, and Oracle AI Database@AWS, while clarifying licensing requirements for RDS Custom with Microsoft, IBM Db2, and Oracle software. Key additions include AWS's right to scan extension code for security purposes, responsibility for maintaining EOL engine versions, and requirements for License Mobility verification when using Microsoft software via Bring Your Own Media (BYOM).

3 new obligations 1 obligation expanded

Aws customers using amazon rds: You must upgrade your database engine before AWS stops supporting it, or AWS may delete your instance after giving you notice.

Aws customers using rds custom with microsoft software: Before you can use your own Microsoft license on RDS Custom, you must verify with Microsoft that you have the right to do so.

Aws customers using trusted language extensions for postgresql: AWS will scan the code you use with Trusted Language Extensions to check for security and performance issues.

Aws customers using rds custom: If your customizations or additional software cause your RDS Custom instance to fall outside AWS's support perimeter, AWS is not responsible for service failures.

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 new operational requirements for AWS RDS customers. Users operating database instances on end-of-life engine versions must upgrade to supported versions or face automatic instance deletion after AWS provides prior notice. For customers using RDS Custom with Microsoft software via Bring Your Own Media, the terms now require License Mobility Verification Form submission to Microsoft and compliance with Microsoft's cloud licensing policies. Customers using Trusted Language Extensions must understand that AWS may scan extension code for security and performance purposes, and AWS disclaims responsibility for service failures caused by extensions. You should review your current database engine versions and licensing arrangements to ensure compliance with these updated requirements.

What you can do

→ Audit your Amazon RDS instances to identify any running end-of-life database engine versions and plan upgrades to supported versions.

→ If using RDS Custom with Microsoft SQL Server via Bring Your Own Media, obtain and submit the License Mobility Verification Form to Microsoft before deployment.

→ Review your Trusted Language Extensions deployments to understand AWS's code scanning practices and ensure compliance.

Historical Context

ConductAtlas has recorded 5 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
Engine End of Life (EOL) Management

AWS may delete RDS instances running unsupported engine versions after providing prior notice; customers are responsible for upgrading to supported versions.

Trusted Language Extensions Scanning

AWS may scan extension code for security and performance purposes; AWS disclaims responsibility for service failures caused by extensions.

RDS Custom License Mobility Verification

Customers using Bring Your Own Media with Microsoft Software must submit License Mobility Verification Form to Microsoft and maintain valid License Mobility rights.

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
c39b5e61669e994b72eea67689b9b8b1105fe8dfcea0809b0c93f21a4c26084f
May 29, 2026 01:07 UTC
✓ Verified
Current Version
d60e9a71487307f8b041f5d0a466d87958df3404718291d4cb2b49f6b2cdec81
May 30, 2026 01:19 UTC
✓ Verified
Change Detected
May 30, 2026 01:19 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
Adds database engine upgrade requirements and scanning rights for RDS extensions
2026-10-11 · Impact summary edited · summary regenerated by summarize_events
Previous text
The updated terms establish that customers operating Amazon RDS databases on end-of-life software versions are now required to upgrade to supported versions. The agreement authorizes AWS to scan extension code used with Trusted Language Extensions for security and performance purposes, and establishes that extension code constitutes customer content. AWS disclaims responsibility for service failures caused by extensions or end-of-life database software. If a customer does not upgrade before an engine reaches end of life, AWS may snapshot the customer's data and delete the instance or cluster running the unsupported software, after providing prior notice of the engine end-of-life date.
2026-10-11 · Summary edited · summary regenerated by summarize_events
Previous text
AWS Bedrock updated its Amazon RDS service terms on May 30, 2026, adding new provisions governing Trusted Language Extensions, engine end-of-life management, and RDS Custom. The updated terms establish that extension code falls under customer content, require customers to upgrade to supported database engine versions when old versions reach end of life, authorize AWS to scan extension code for security purposes, and permit AWS to snapshot and delete instances running unsupported software after providing notice. These changes create new customer obligations around database engine maintenance and establish AWS liability limitations for failures caused by extensions or obsolete software.
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 May 30, 2026. Change detected: 13 sentence(s) added, 2 sentence(s) removed, 14 sentence(s) modified. Document contained 1007 sentences after update.
Citation Record
Entity: AWS Bedrock
Document: AWS Service Terms
Record ID: CA-X-002499
Version: CA-V-003185
Captured: 2026-05-30 01:19:49 UTC
URL: https://conductatlas.com/change/2026-05-30-aws-bedrock-aws-service-terms-2499/
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 restructured its RDS service terms to clarify database engine lifecycle management and third-party licensing obligations. The change introduces explicit requirements for customers to maintain supported database engine versions, with AWS reserving the right to …

🔒 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-002499.

Full Changes

View complete diff →

Document Context

Version history → Policy drift analysis → Document page →
Document
AWS Service Terms
Entity
AWS Bedrock
Captured
May 30, 2026
Source URL
https://aws.amazon.com/service-terms/
Other changes to AWS Service Terms
Previous change May 29, 2026
AWS Bedrock's Service Terms were updated to add comprehensive governance requirements for Amazon Connect Talent, a new AI service for …
High Negative
Next change Jun 2, 2026
AWS Bedrock updated its abuse detection and content retention practices. Previously, the terms stated that automated abuse detection mechanisms "may …
Medium 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 →