AWS aurora-dsql documentation change
Summary
Removed section about relationships and referential integrity including foreign key constraints and application layer validation recommendations
Security assessment
The removed section discussed database design patterns including referential integrity and foreign key constraints. While data integrity can have security implications, removing this documentation doesn't indicate a security issue was addressed. This appears to be routine documentation cleanup.
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 dba844a88..a6f33f03b 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 @@ -120,7 +119,0 @@ Aurora DSQL uses optimistic concurrency control (OCC), a lock-free approach that -**Relationships and referential integrity** - - -Aurora DSQL supports foreign key relationships between tables, including ` JOIN ` operations. For referential integrity, implement validation in your application layer. While enforcing referential integrity can be valuable, cascading operations (like cascading deletes) can create unexpected performance issues—for example, deleting an order with 1,000 line items becomes a 1,001-row transaction. Many customers avoid foreign key constraints for this reason. - -**Design pattern:** Implement referential integrity checks in your application layer, use eventual consistency patterns, or leverage AWS services for data validation. -