AWS clean-rooms documentation change

Service: clean-rooms · 2025-04-03 · Documentation low

File: clean-rooms/latest/userguide/edit-collaboration.md

Summary

Added documentation for updating collaboration analytics engine to Spark and instructions for turning off CloudWatch log storage

Security assessment

The 'Turn off log storage' section documents security-adjacent logging controls but doesn't address a specific vulnerability. Log management is a security feature but there's no evidence of patching a security issue.

Diff

diff --git a/clean-rooms/latest/userguide/edit-collaboration.md b/clean-rooms/latest/userguide/edit-collaboration.md
index 12197fac7..499b4cdbb 100644
--- a//clean-rooms/latest/userguide/edit-collaboration.md
+++ b//clean-rooms/latest/userguide/edit-collaboration.md
@@ -5 +5 @@
-Edit collaboration name and descriptionEdit collaboration logs settingsEdit collaboration tagsEdit membership tagsEdit associated table tagsEdit analysis template tagsEdit differential privacy policy tags
+Edit collaboration name and descriptionUpdate collaboration analytics engineTurn off log storageEdit collaboration logs settingsEdit collaboration tagsEdit membership tagsEdit associated table tagsEdit analysis template tagsEdit differential privacy policy tags
@@ -9 +9,3 @@ Edit collaboration name and descriptionEdit collaboration logs settingsEdit coll
-Learn how to edit the different parts of a collaboration.
+As a collaboration creator, you can edit the different parts of a collaboration.
+
+For information about how to edit a collaboration using the AWS SDKs, see the _[AWS Clean Rooms API Reference](https://docs.aws.amazon.com/clean-rooms/latest/apireference/Welcome.html)_.
@@ -14,0 +17,4 @@ Learn how to edit the different parts of a collaboration.
+  * Update collaboration analytics engine
+
+  * Turn off log storage
+
@@ -44 +50 @@ After you create the collaboration, you can only edit the collaboration name and
-  5. For **Details** , edit the **Name** and **Description** of the collaboration.
+  5. On the **Edit collaboration** page, for **Details** , edit the **Name** and **Description** of the collaboration.
@@ -46,0 +53,60 @@ After you create the collaboration, you can only edit the collaboration name and
+
+
+
+
+## Update collaboration analytics engine
+
+After you create the collaboration, you can change the analytics engine from AWS Clean Rooms SQL to Spark.
+
+###### Note
+
+Changing the analytics engine from AWS Clean Rooms SQL to Spark might break existing workflows.
+
+###### To update the collaboration analytics engine
+
+  1. Sign in to the AWS Management Console and open the [AWS Clean Rooms console](https://console.aws.amazon.com/cleanrooms/home) with your AWS account (if you haven't yet done so).
+
+  2. In the left navigation pane, choose **Collaborations**.
+
+  3. Choose the collaboration that you created.
+
+  4. On the collaboration detail page, choose **Actions** , and then choose **Edit collaboration**. 
+
+  5. On the **Edit collaboration** page, for **Analytics engine** ,
+
+     * If **AWS Clean Rooms SQL** is selected, choose **Spark**.
+
+     * If **Spark** is selected, choose **Submit a support ticket** to submit a support ticket to change the analytics engine to AWS Clean Rooms SQL.
+
+  6. Choose **Save changes**.
+
+
+
+
+## Turn off log storage
+
+If you have enabled **Analysis logging** , you can edit whether the analysis logs are stored in your Amazon CloudWatch Logs account.
+
+###### To turn off log storage
+
+  1. Sign in to the AWS Management Console and open the [AWS Clean Rooms console](https://console.aws.amazon.com/cleanrooms/home) with your AWS account (if you haven't yet done so).
+
+  2. In the left navigation pane, choose **Collaborations**.
+
+  3. Choose the collaboration that has analysis logging turned on.
+
+  4. On the collaboration detail page, choose **Actions** , and then choose **Turn off log storage**. 
+
+###### Note
+
+A warning appears, indicating the following:
+
+     * New queries will no longer be logged to your CloudWatch account.
+
+     * Existing logs will be preserved according to your current retention settings.
+
+     * If you reactivate logging in the future, it will only apply to queries made after reactivation.
+
+     * This change affects only your logs - other team members' logging settings remain unchanged.
+
+  5. Choose **Turn off**.