SageMaker notebook instance not in a VPC

What this check finds

A SageMaker notebook instance has no subnet, so it runs outside any VPC you control: its traffic does not pass your security groups, NACLs or VPC endpoints.

Passing looks like: SageMaker notebook runs inside a VPC.

How to fix it

Recreate the notebook instance with --subnet-id and --security-group-ids in a private subnet (the subnet cannot be added to an existing instance), with DirectInternetAccess=Disabled.

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