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.
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.
The updated terms establish new customer obligations to manage database engine lifecycle and upgrade to supported versions, with AWS authorized to take unilateral action (delete instances) on unsupported software after notice. This creates operational risk for customers with legacy databases or limited maintenance resources, and shifts liability for extension-related failures from AWS to customers.
→ Audit current Amazon RDS database inventory to identify instances running end-of-life or near-end-of-life database engine versions
→ Schedule and execute database engine upgrades for instances on unsupported versions before the published engine end-of-life date
→ If using Trusted Language Extensions, review extension code and AWS's authority to scan it, and update internal documentation or privacy policies as needed
→ Instances running end-of-life database software may be snapshot and deleted by AWS after prior notice is provided, resulting in potential service interruption unless a restore is performed.
→ Service failures caused by database extensions or end-of-life software are excluded from AWS's responsibility, meaning AWS will not provide technical support or service credits for such failures.
ConductAtlas has recorded 4 material changes to this document (since May 2026). An additional minor or cosmetic changes were excluded.
2 of AWS Bedrock's significant changes have been classified as negative for consumers.
Establishes customer responsibility for engine upgrades and authorizes AWS to snapshot and delete instances running end-of-life software after providing notice.
Authorizes AWS to scan extension code for security and performance purposes and disclaims AWS responsibility for service failures caused by extensions.
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
You must keep your database software updated to versions AWS still supports, or AWS may delete your database.
AWS will scan code you write or use in PostgreSQL extensions to check for security issues and performance problems.
+ 1 more obligation changes. Full breakdown available with Monitor.
Track changes →AWS has added explicit obligations requiring RDS customers to manage database engine lifecycle and upgrade to supported versions before end of life, with authorization for AWS to take unilateral action (snapshots and deletion) on instances running obsolete software after notice. The terms also formalize AWS's right to scan extension code without prior consent, classified as a security measure. Organizations using RDS should assess current database inventory for engines approaching end of life and establish upgrade protocols. The change may trigger policy updates for customers with SLAs requiring database availability, as AWS's unilateral deletion authority creates operational risk for instances not actively managed. No explicit regulatory exposure is identified, but backup and disaster recovery procedures should account for AWS's ability to delete instances running EOL software after notice.
Full compliance analysis
Obligation analysis, escalation trigger, board language, and recommended action.
Monitor: regulatory citations + obligations. Compliance: full compliance memo.
ConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-C-002499.
See the full side-by-side comparison of every sentence added, removed, and modified.
🔒 Full diff — MonitorAWS Bedrock updated its AWS Service Terms on May 23, 2026, adding explicit language stating that Reserved Cache Nodes and …
AWS Bedrock updated its AWS Service Terms on May 19, 2026, modifying two contact information entries in its contracting party …
Get alerted when this policy changes again — including what changed and why it matters.
Prefer a weekly summary instead?
Get the biggest policy changes across 320+ platforms every Sunday.