AWS clean-rooms documentation change
Summary
Simplified collaboration member roles by removing job-related capabilities, removed sections about analytics engine selection and member invitations
Security assessment
Changes focus on feature deprecation (jobs) and documentation reorganization rather than security improvements. Maintains existing security controls around query access without adding new security content.
Diff
diff --git a/clean-rooms/latest/userguide/working-with-collaborations.md b/clean-rooms/latest/userguide/working-with-collaborations.md index 73d8319a4..6fce0d0bd 100644 --- a/clean-rooms/latest/userguide/working-with-collaborations.md +++ b/clean-rooms/latest/userguide/working-with-collaborations.md @@ -7 +7 @@ -A _collaboration_ is a secure logical boundary in AWS Clean Rooms in which members can perform analysis on configured tables. +A _collaboration_ is a secure logical boundary in AWS Clean Rooms in which members can perform SQL queries on configured tables. @@ -11 +11 @@ Any member in AWS Clean Rooms can create a collaboration. -The collaboration creator can designate a single member to analyze configured tables and receive results. However, the collaboration creator might want to prevent the member who can run the analysis from having access to the query results. In that case, the collaboration creator can designate one [member to who can query](./glossary.html#glossary-member-who-can-query) or [one member who can run queries and jobs](./glossary.html#glossary-member-who-can-run-queries-jobs) and another [member who can receive results](./glossary.html#glossary-member-who-can-receive-results). +The collaboration creator can designate a single member to query and receive results. However, the collaboration creator might want to prevent the member who can query from having access to the query results. In that case, the collaboration creator can designate one [member to who can query](./glossary.html#glossary-member-who-can-query) and another [member who can receive results](./glossary.html#glossary-member-who-can-receive-results). @@ -13 +13 @@ The collaboration creator can designate a single member to analyze configured ta -In most cases, the member who can query or the member who can query and run jobs is also the [member paying for compute costs](./glossary.html#glossary-member-paying-for-query-compute). However, the collaboration creator can configure a different member to be responsible for paying for the query compute costs. +In most cases, the member who can query is also the [member paying for query compute costs](./glossary.html#glossary-member-paying-for-query-compute). However, the collaboration creator can configure a different member to be responsible for paying for the query compute costs. @@ -19,2 +18,0 @@ For information about how to create a collaboration using the AWS SDKs, see the - * [Selecting an analytics engine type in AWS Clean Rooms](./select-analytics-engine-type.html) - @@ -31,2 +28,0 @@ For information about how to create a collaboration using the AWS SDKs, see the - * [Inviting members to a collaboration](./invite-members.html) - @@ -50 +46 @@ Set up service roles for AWS Clean Rooms ML -Selecting an analytics engine type +Creating a collaboration