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.
Consumers: You must keep your database software updated to versions AWS still supports, or AWS may delete your database.
Developers: AWS will scan code you write or use in PostgreSQL extensions to check for security issues and performance problems.
Consumers: If your database fails because you are using outdated software or problematic extensions, AWS is not responsible.
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.
→ 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
ConductAtlas has recorded 5 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
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 …
Regulatory exposure, obligation change, escalation trigger, board-ready language, and recommended action for legal and compliance teams.
Unlock the full institutional analysis — InsightConductAtlas 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.
AWS Bedrock removed language requiring explicit consent to transfer customer content and metadata to Anthropic for abuse detection, and removed …
AWS expanded the list of services classified as 'Indemnified Generative AI Services' in its AWS Service Terms, adding three additional …
AWS Bedrock updated its Service Terms to introduce a new AWS (new) program and restructured billing and project management terms. …
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.
Get alerted when this policy changes again, including what changed and why it matters.