AWS clean-rooms: Extended TLS in-transit encryption statement to include Databricks
Summary
Updated the data protection page to state that data in transit is encrypted via TLS/HTTPS for S3, Athena, Snowflake, and now Databricks sources.
Security assessment
The change documents encryption-in-transit guarantees (TLS/HTTPS) for an additional data source, which is security best-practice documentation rather than a fix for a specific vulnerability.
Evidence
+AWS Clean Rooms uses Transport Layer Security (TLS) for encryption in transit. Communication with AWS Clean Rooms is always done over HTTPS so your data is always encrypted in transit, regardless of whether it's stored in Amazon S3, Amazon Athena, Snowflake, or Databricks. This includes all data in transit when using Clean Rooms ML.
Diff
diff --git a/clean-rooms/latest/userguide/data-protection.md b/clean-rooms/latest/userguide/data-protection.md index 5cbebfd..da2bb74 100644 --- a//clean-rooms/latest/userguide/data-protection.md +++ b//clean-rooms/latest/userguide/data-protection.md @@ -52 +52 @@ When using an ID mapping table within AWS Clean Rooms, the service encrypts all -AWS Clean Rooms uses Transport Layer Security (TLS) for encryption in transit. Communication with AWS Clean Rooms is always done over HTTPS so your data is always encrypted in transit, regardless of whether it's stored in Amazon S3, Amazon Athena, or Snowflake. This includes all data in transit when using Clean Rooms ML. +AWS Clean Rooms uses Transport Layer Security (TLS) for encryption in transit. Communication with AWS Clean Rooms is always done over HTTPS so your data is always encrypted in transit, regardless of whether it's stored in Amazon S3, Amazon Athena, Snowflake, or Databricks. This includes all data in transit when using Clean Rooms ML.