AWS clean-rooms: Note that SQL-only controls cause PySpark jobs to fail on intermediate tables
Summary
Added a note stating that some analysis rule controls (disallowed output columns, differential privacy, additional analyses) apply only to SQL queries and that a PySpark job referencing a table with these controls fails to start, with a link to the controls section.
Security assessment
Reinforces enforcement behavior of privacy/output controls for intermediate tables and warns that PySpark jobs referencing such tables are blocked; useful hardening/awareness information but no specific vulnerability is described.
Evidence
+Some analysis rule controls apply only to SQL queries, including disallowed output columns, differential privacy, and additional analyses. A PySpark job that references a table with any of these controls fails to start. For more information, see [Controls that apply only to SQL queries](./custom-considerations.html#custom-sql-only-controls).
Diff
diff --git a/clean-rooms/latest/userguide/intermediate-table-analysis-rule.md b/clean-rooms/latest/userguide/intermediate-table-analysis-rule.md index 6dca251..8fad0c1 100644 --- a//clean-rooms/latest/userguide/intermediate-table-analysis-rule.md +++ b//clean-rooms/latest/userguide/intermediate-table-analysis-rule.md @@ -68,0 +69,4 @@ Review the **Columns available for analysis** table, which shows the column name +###### Note + +Some analysis rule controls apply only to SQL queries, including disallowed output columns, differential privacy, and additional analyses. A PySpark job that references a table with any of these controls fails to start. For more information, see [Controls that apply only to SQL queries](./custom-considerations.html#custom-sql-only-controls). +