SageMaker Studio apps have direct internet egress

What this check finds

A SageMaker Studio domain has AppNetworkAccessType=PublicInternetOnly, the AWS default, so its apps send traffic to the internet directly, outside your VPC controls, while holding the execution role. This is outbound access: signing in to Studio still needs IAM or SSO.

Passing looks like: SageMaker Studio apps send traffic through your VPC.

How to fix it

Use VpcOnly: aws sagemaker update-domain --domain-id ID --app-network-access-type VpcOnly, with subnets and VPC endpoints for the services the apps use. Delete running apps 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