Git Secrets policy Amazon EMR Studio

Amazon EMR Studio provides fine-grained IAM permissions to control user actions within the Studio environment, including Git integration

Permissions for Git secrets are managed via AWS Secrets Manager, using tag-based access control for user-level granularity

The for-use-with-amazon-emr-managed-user-policies tag is automatically added to new Git secrets for user-level access control

Policies must grant secretsmanager:GetSecretValue with a condition matching the user’s ID to the secret’s tag for secure Git credential access

Administrators should remove broad service-level GetSecretValue permissions in favor of user-level, tag-based permissions for tighter security

Policies should include permissions for tagging secrets, passing roles, and managing editors, clusters, and S3 access for logs and notebooks