SageMaker notebook instance allows IMDSv1

What this check finds

A SageMaker notebook instance's minimum instance metadata service version is 1. A server-side request forgery in code running on the notebook can read its execution role's credentials from IMDSv1 without a token.

Passing looks like: SageMaker notebook requires IMDSv2.

How to fix it

aws sagemaker update-notebook-instance --notebook-instance-name NAME --instance-metadata-service-configuration MinimumInstanceMetadataServiceVersion=2 (stop the instance first).

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 execution role is over-permissioned
• 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

All SageMaker checks