1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
0
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.
respondido hace 2 años
You mean to create a NAT gateway for all the subnets associated with the model with Elastic IPs allocated right?
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace un año
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