# AWS Clean Rooms Lets You Pinpoint SQL Query Issues With Execution Logs

Hi everyone, Shii-chan here! Today's update is about AWS Clean Rooms, the data collaboration platform.

## What was announced?

According to AWS What's New, AWS Clean Rooms now lets you export privacy-enhanced analysis logs for SQL analyses. For SQL queries run inside a Clean Rooms collaboration, you can now export privacy-enhanced logs, including Spark execution details, to an S3 bucket.

## The story so far

AWS Clean Rooms lets companies and their partners jointly analyze data without exposing or copying each other's underlying data. But when a query ran slower than expected or didn't behave as planned, there wasn't really a way to see what was happening inside Spark's execution. The very privacy protections that make Clean Rooms useful also made it harder to look inside for optimization or troubleshooting.

## What changes

Collaboration owners can now grant members the ability to export analysis logs, either when creating a collaboration or by submitting a change request for an existing one. Once granted, a member can export privacy-enhanced analysis logs to any S3 path they choose after a query runs. For example, a third-party measurement provider collaborating with a publisher could spot an anomalous data skew causing a query to run slower than usual, cutting time-to-resolution and helping optimize costs.

## Wrap-up

- You can now export privacy-enhanced analysis logs for Clean Rooms SQL queries to S3
- Spark execution details are visible, making it easier to optimize and troubleshoot queries
- Export permission is granted to members at collaboration creation or via a change request
- Check the AWS Regions table for availability

If you've ever been stuck puzzling over query performance in a multi-partner data collaboration, this is a welcome update!