- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
When you delete a notebook instance, SageMaker removes the ML compute instance, and deletes the ML storage volume as well as the network interface associated with the notebook instance.
In addition to the answer above, see the doc here for deleting Studio notebooks - https://docs.aws.amazon.com/sagemaker/latest/dg/studio-tasks-update-apps.html
The above statements are valid for a Notebook Instance, whereas your post suggests you are using a Studio Notebook (Studio-Notebook:ml.t3.medium). Make sure to delete the KernelGateway apps. The storage volume is not deleted if you delete the app. You will need to delete the Studio user profile and the Studio domain (instructions here - https://docs.aws.amazon.com/sagemaker/latest/dg/gs-studio-delete-domain.html), and the underlying EFS volume.
You could also try to stop and then delete the notebook instance if for some reason SageMaker failed to remove it for you.
https://docs.aws.amazon.com/cli/latest/reference/sagemaker/list-notebook-instances.html https://docs.aws.amazon.com/cli/latest/reference/sagemaker/stop-notebook-instance.html
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
You will see in studio that there is an icon that looks like a power on button. A circle with a square on it on the left column of studio. You can click on it to see what running instances you have. You can then click on the instance and click the power cycle button.