- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hello,
It's possible that SageMaker resources were not fully cleaned up after your previous experiment, leading to unexpected ongoing charges. A few things to check:
-
Check Cost Explorer for the specific SageMaker resources, like notebook instances or endpoints, and their statuses. Idle resources will still incur charges.
-
Ensure any notebook instances or endpoints were properly deleted after the experiment. Running or idle resources will continue to be billed until they are fully removed.
-
Refer to the AWS documentation for steps to properly shut down notebook instances and delete endpoints to ensure all related resources are cleaned up. Commands like sagemaker delete-endpoint need to be run.
Maybe this repost can also help https://repost.aws/questions/QUvfuWg_JBTiiTU9My71BVTQ/how-do-i-turn-off-sagemaker-when-not-in-use
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 anni fa