1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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.
beantwortet vor 2 Jahren
You mean to create a NAT gateway for all the subnets associated with the model with Elastic IPs allocated right?
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 6 Monaten
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