In Sagemaker endpoint, pip download fails when connected through VPC
Pip download fails in my instance when sagemaker is connected through VPC. It is successful when VPC is not specified. I have internet gateway configured for my public subnets. I was able to pip download successfully in EC2 with same security groups and subnets. Is this any bug in sagemaker side?
And also, can we log into EC2 instance that sagemaker created? It is more of like a blackbox testing without it.
When specifying a VPC config, ENIs are launched into your VPC which your Endpoint will use to communicate within your VPC. These ENIs have private IPs. In order to communicate with the internet you would need to make use of a NAT. SageMaker Endpoints are managed and it is currently not possible to SSH into the EC2 instance(s) backing your Endpoint.
You mean to create a NAT gateway for all the subnets associated with the model with Elastic IPs allocated right?
Relevant questions
Pushing to SQS through VPC Endpoint from lambda in private VPC fails
asked a year agoSagemaker Endpoint is not created when deploying HuggingFace Model using it.
asked 3 months agoWhy does my kernal keep dying when I try to import Hugging Face BERT models to Amazon SageMaker?
Accepted AnswerSageMaker notebook instance in VPC failed to connect to local database
Accepted Answerasked 3 years agoUnable to resolve the private dns name of a Sagemaker runtime VPC interface endpoint
asked 3 months agoCan't download to my EC2 windows instance through Internet Explorer
asked a year agoWhich connection method when using SageMaker Notebook through VPC Interface Endpoint?
Accepted AnswerWhy does my kernel keep restarting when I try to download pre-trained Hugging Face BERT models weights to Amazon SageMaker?
asked 3 months agoIn Sagemaker endpoint, pip download fails when connected through VPC
asked 6 months agoGround Truth in VPC
Accepted Answerasked 4 months ago
Currently, logging into EC2 instance that SageMaker created in not possible. What endpoint is this? Is it possible to test by creating a SageMaker notebook in that VPC