AWS Security ChangesHomeSearch

AWS aurora-dsql documentation change

Service: aurora-dsql · 2026-04-25 · Documentation low

File: aurora-dsql/latest/userguide/working-with-concurrency-control.md

Summary

Updated error messages for transaction conflicts and schema update conflicts

Security assessment

The changes are minor wording updates to error messages (removing 'retry as needed' and 'please retry'). There's no evidence these changes are related to security issues - they appear to be routine error message clarifications.

Diff

diff --git a/aurora-dsql/latest/userguide/working-with-concurrency-control.md b/aurora-dsql/latest/userguide/working-with-concurrency-control.md
index 8f6705e0d..a6c8d5126 100644
--- a//aurora-dsql/latest/userguide/working-with-concurrency-control.md
+++ b//aurora-dsql/latest/userguide/working-with-concurrency-control.md
@@ -25 +25 @@ Two transactions attempted to modify the same row. The transaction with the earl
-    ERROR: mutation conflicts with another transaction, retry as needed (OC000) (SQLSTATE 40001)
+    ERROR: change conflicts with another transaction (OC000) (SQLSTATE 40001)
@@ -33 +33 @@ The session's cached schema catalog is out of date. When Aurora DSQL detects tha
-    ERROR:  schema has been updated by another transaction, please retry: (OC001) (SQLSTATE 40001)
+    ERROR: schema has been updated by another transaction (OC001) (SQLSTATE 40001)