AWS Security ChangesHomeSearch

AWS aurora-dsql medium security documentation change

Service: aurora-dsql · 2025-12-07 · Security-related medium

File: aurora-dsql/latest/userguide/troubleshooting.md

Summary

Updated SSL error messaging and concurrency control documentation

Security assessment

Added 'unable to accept connection, sni was not received' error clarification. SNI is a TLS extension critical for secure connections to multi-tenant services. Older psql versions without SNI support could expose users to misrouting or man-in-the-middle risks.

Diff

diff --git a/aurora-dsql/latest/userguide/troubleshooting.md b/aurora-dsql/latest/userguide/troubleshooting.md
index 2c4eb662b..48cde59d6 100644
--- a//aurora-dsql/latest/userguide/troubleshooting.md
+++ b//aurora-dsql/latest/userguide/troubleshooting.md
@@ -32 +32 @@ The following topics provide troubleshooting advice for errors and issues that y
-**error: unrecognized SSL error code: 6**
+**error: unrecognized SSL error code: 6** or **unable to accept connection, sni was not received**
@@ -34 +34 @@ The following topics provide troubleshooting advice for errors and issues that y
-Cause: You might be using a psql version earlier than [version 14](https://www.postgresql.org/docs/release/14.0/), which doesn't support Server Name Indication (SNI). The SNI is required when connecting to Aurora DSQL.
+You might be using a psql version earlier than [version 14](https://www.postgresql.org/docs/release/14.0/), which doesn't support Server Name Indication (SNI). The SNI is required when connecting to Aurora DSQL.
@@ -98,4 +97,0 @@ Aurora DSQL doesn't support all PostgreSQL-based dialect. To learn about what is
-**Error: SELECT FOR UPDATE in a read-only transaction is a no-op**
-
-You are attempting an operation that isn't allowed in a read-only transaction. To learn more, see [ Understanding concurrency control in Aurora DSQL](https://docs.aws.amazon.com/aurora-dsql/latest/userguide/working-with-concurrency-control.html).
-
@@ -109,0 +106,2 @@ To create an index on a table with existing rows, you must use the `CREATE INDEX
+This transaction attempted to modify the same tuples as another, concurrent, transaction. This indicates contention on the modified tuples. To learn more, please refer to [ Concurrency control in Aurora DSQL ](https://docs.aws.amazon.com/aurora-dsql/latest/userguide/working-with-concurrency-control.html)
+