AWS clean-rooms: Clean Rooms doc history: CACHE TABLE disallowed-column entry added
Summary
Adds a November 10, 2026 change-log entry announcing that columns listed in the `disallowedOutputColumns` control of a custom analysis rule can now be used in CACHE TABLE statements (as with subqueries/CTEs), removing the need to convert the cached table to a CTE, while the control still blocks the column from the final projection.
Security assessment
Changelog entry recording the same relaxation of the Clean Rooms `disallowedOutputColumns` privacy control, noting the final-projection block still applies. It is a policy/behavior documentation change with data-inference implications rather than a vulnerability fix or advisory, so it is not security_issue_related; impact is limited to a changelog page.
Evidence
+Use disallowed output columns in CACHE TABLE statements| You can now use a column listed in the `disallowedOutputColumns` control of a custom analysis rule in a CACHE TABLE statement, as you can in a subquery or CTE. You no longer need to convert the cached table to a CTE. The control still blocks the column from the final projection of the query.
Diff
diff --git a/clean-rooms/latest/userguide/doc-history.md b/clean-rooms/latest/userguide/doc-history.md index c07b7a4..7e6f26e 100644 --- a//clean-rooms/latest/userguide/doc-history.md +++ b//clean-rooms/latest/userguide/doc-history.md @@ -14,0 +15 @@ Change| Description| Date +Use disallowed output columns in CACHE TABLE statements| You can now use a column listed in the `disallowedOutputColumns` control of a custom analysis rule in a CACHE TABLE statement, as you can in a subquery or CTE. You no longer need to convert the cached table to a CTE. The control still blocks the column from the final projection of the query. For more information about the `disallowedOutputColumns` control, see [Disallowed output columns](https://docs.aws.amazon.com/clean-rooms/latest/userguide/disallowed-output-columns.html).| November 10, 2026