Why is the ML Specialist not seeing the instance visible in the VPC?

By:
In: MLS-C01
Tagged:
With: 1 Comment
A Machine Learning Specialist is using an Amazon SageMaker notebook instance in a private subnet of a corporate VPC.The ML Specialist has important data stored on the Amazon SageMaker notebook instance’s Amazon EBS volume, and needs to take a snapshot of that EBS volume.However, the ML Specialist cannot find the Amazon SageMaker notebook instance’s EBS volume or Amazon EC2 instance within the VPC.

Why is the ML Specialist not seeing the instance visible in the VPC?

Amazon SageMaker notebook instances are based on the EC2 instances within the customer account, but they run outside of VPCs.

Amazon SageMaker notebook instances are based on the Amazon ECS service within customer accounts.

Amazon SageMaker notebook instances are based on EC2 instances running within AWS service accounts.

Amazon SageMaker notebook instances are based on AWS ECS instances running within AWS service accounts.

Explanations:

Amazon SageMaker notebook instances run within the VPC, but the instances are not directly visible in the VPC because they use a special setup managed by AWS, where the networking is abstracted.

Amazon SageMaker notebook instances are not based on Amazon ECS. ECS is used for container orchestration, not for managing SageMaker notebook instances.

Amazon SageMaker notebook instances are based on EC2 instances that are managed by AWS service accounts and not directly visible in the customer’s VPC. The networking is abstracted by AWS.

Amazon SageMaker notebook instances are not based on AWS ECS instances. ECS is a service for managing containers, not for managing SageMaker notebook instances.

2025-10-08

1 Comment

  1. Isaac
    Author

    I suspect that the answer is:
    Amazon SageMaker notebook instances are based on EC2 instances running within AWS service accounts.

Leave a Reply

Your email address will not be published. Required fields are marked *

ten + 8 =