aws-cleanrooms

Diagnoses AWS Clean Rooms permission failures and CloudWatch logging issues for ML jobs.

Updated Jul 21, 2026
Ready to run
npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill aws-cleanrooms-richardnroman
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: aws-cleanrooms
Source: https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform/tree/main/.agents/skills/aws-cleanrooms
Command: npx skills add https://github.com/richardnroman/Synthetic-Data-Exchange-Licensing-Platform --skill aws-cleanrooms-richardnroman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AWS Clean Rooms collaborations fail with opaque access denied errors and missing CloudWatch logs for custom ML training and inference jobs, and tracing the root cause across IAM roles, S3 bucket policies, KMS keys, and Lake Formation permissions is time-consuming and error-prone. ## Core Features & Use Cases - Permission Debugging: Systematically checks IAM role policies (inline and managed), S3 bucket policies, KMS key policies, Lake Formation grants, and cross-account trust configurations to pinpoint access failures. - ML Logging Diagnostics: Verifies Configured Model Algorithm Association privacy configurations, ML Configuration roles, and CloudWatch log groups to explain why training or inference job logs are not published. - Structured Diagnosis Reports: Produces a standardized output with error classification, pass/fail diagnostic results, root cause, and exact CLI fix commands. - Use Case: A customer reports that their Clean Rooms ML trained model shows PUBLISH_FAILED for logs. The Skill walks through the privacy configuration, ML Configuration role permissions, and log group checks, then identifies the missing logs:PutLogEvents permission and provides the exact IAM policy fix. ## Quick Start Diagnose why my Clean Rooms membership is getting an access denied error on a protected query in region us-east-1 with membership ID abc123.

Frequently Asked Questions about aws-cleanrooms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug access denied errors in AWS Clean Rooms?▼

Classify the error as result writing, data access, table association, or cross-account failure, then check IAM role policies, S3 bucket policies, KMS key policies, and Lake Formation grants in sequence. Verify the trust policy allows cleanrooms.amazonaws.com and check for explicit Deny statements.

Why are CloudWatch logs missing for Clean Rooms ML trained models?▼

Missing logs typically result from an empty containerLogs privacy configuration on the Configured Model Algorithm Association, a missing ML Configuration, or the ML Configuration role lacking logs:CreateLogGroup, logs:CreateLogStream, and logs:PutLogEvents permissions on /aws/cleanroomsml/* log groups.

What IAM permissions does a Clean Rooms data access role need?▼

For Glue/S3-backed configured tables, the role needs glue:GetDatabase, glue:GetTable, glue:GetPartitions, glue:BatchGetPartition, s3:GetObject, s3:GetBucketLocation, and s3:ListBucket. If the bucket uses SSE-KMS, it also needs kms:Decrypt and kms:DescribeKey on the specific key.

Does Lake Formation affect Clean Rooms table access?▼

Yes. If Lake Formation enforces fine-grained access (empty default permissions in data lake settings), IAM Glue permissions alone are insufficient. The role needs explicit SELECT and DESCRIBE grants on the database and table, unless IAM_ALLOWED_PRINCIPALS is granted.

Why does StartProtectedQuery fail even with cleanrooms permissions?▼

The caller also needs dependent actions like cleanrooms:GetCollaborationAnalysisTemplate, cleanrooms:GetSchema, and S3 output permissions. Also check whether AWSCleanRoomsFullAccessNoQuerying is attached, since it explicitly denies StartProtectedQuery and cannot be overridden.