- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
It seems like SageMaker doesn't let you pick and choose exactly which subnet to use when you've got multiple ones for your deployments. While it's not ideal, SageMaker decides which subnet to deploy based on its internal logic, primarily for availability and operational efficiency.
Unfortunately, there's no straightforward way to specify a "preferred" subnet directly in the setup. People usually just provide a list of subnets, and SageMaker works out the rest. It might seem a bit limiting, especially when you're trying to control your deployment environments closely.
One thing you might think about (though it's a bit of a hack and comes with its own risks) is adjusting the available IPs in your secondary subnet. But, this approach is like walking a tightrope without a net – it's tricky and could lead to other problems.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa