SageMaker execution role is over-permissioned

What this check finds

An IAM role used by a SageMaker notebook or training job grants admin-equivalent permissions (for example full IAM, iam:PassRole on everything with a way to launch compute, or AdministratorAccess), or read access to every S3 bucket, that no explicit Deny in the role cancels. Code running on the notebook or in the training container can use all of it.

Passing looks like: SageMaker execution roles are scoped to what they use.

How to fix it

Replace the role's broad grants with the actions the workload uses: start from AmazonSageMaker role guidance, scope s3 to the buckets the job reads and writes, and remove IAM write and wildcard PassRole.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

AI risk mappings

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More SageMaker checks

• HighSageMaker notebook instance has direct internet access
• HighSageMaker training job has no checkpoint configuration
• MediumDistributed SageMaker training job does not encrypt traffic between containers
• MediumSageMaker endpoint not deployed inside VPC
• MediumSageMaker endpoint variant runs on one instance
• MediumSageMaker model has no VPC configuration
• MediumSageMaker monitoring schedule encrypts neither its output nor its volumes with a KMS key
• MediumSageMaker notebook instance allows IMDSv1

All SageMaker checks