AWS aurora-dsql documentation change
Summary
Removed section advising against auto-incrementing sequences and added reference to sequences/identity columns documentation
Security assessment
The changes focus on migration recommendations for data distribution efficiency rather than addressing security vulnerabilities. No mention of security risks or mitigations.
Diff
diff --git a/aurora-dsql/latest/userguide/working-with-postgresql-compatibility-migration-guide.md b/aurora-dsql/latest/userguide/working-with-postgresql-compatibility-migration-guide.md index a259178a1..909b38fec 100644 --- a//aurora-dsql/latest/userguide/working-with-postgresql-compatibility-migration-guide.md +++ b//aurora-dsql/latest/userguide/working-with-postgresql-compatibility-migration-guide.md @@ -50,7 +49,0 @@ Adapt these common PostgreSQL patterns for Aurora DSQL compatibility: -**Sequences for keys** - - -Use UUIDs or composite keys instead of auto-incrementing sequences. Auto-incrementing sequences lead to a high amount of conflicts in a distributed system as multiple writers are trying to update the same data. UUIDs provide the same function but require no coordination. - -**Example:** `id UUID PRIMARY KEY DEFAULT gen_random_uuid()` - @@ -148 +141 @@ Aurora DSQL automatically partitions and distributes your data based on access p -**Migration tip:** Remove manual partitioning logic and let Aurora DSQL handle data distribution. Use UUIDs or application-generated IDs instead of sequences. +**Migration tip:** Remove manual partitioning logic and let Aurora DSQL handle data distribution. Use UUIDs or application-generated IDs for optimal distribution. If your application requires sequential identifiers, see [Sequences and identity columns](./sequences-identity-columns.html).