An ML Specialist uses a SageMaker notebook instance in a private subnet and stores important data on its attached EBS volume. They cannot find the notebook instance's EC2 instance or EBS volume inside their VPC. Why is the instance not visible in the customer's VPC?

SageMaker notebook instances are provisioned on EC2 infrastructure managed by AWS within an AWS service account, not directly in your customer account's VPC. While you can configure the notebook instance to access resources within your private VPC, the underlying EC2 instance itself remains abstracted and is not visible as an EC2 resource or EBS volume within your VPC console. This architecture provides isolation and managed services. The options suggesting they run outside VPCs or are implemented using ECS within the customer account are incorrect. While ECS is used by SageMaker for other services like training jobs, notebook instances specifically leverage EC2.