Distributed SageMaker training job does not encrypt traffic between containers

What this check finds

A SageMaker training job on more than one instance that is running, or ran in the last 90 days, has EnableInterContainerTrafficEncryption off. Model parameters and training data pass between instances unencrypted.

Passing looks like: Distributed SageMaker training encrypts traffic between containers.

How to fix it

Set EnableInterContainerTrafficEncryption=true for distributed training jobs (SDK estimator: encrypt_inter_container_traffic=True).

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
• 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