SageMaker Automatic Model Tuning now supports Delete API
Share
Services
Amazon SageMaker Automatic Model Tuning now provides an API to programmatically delete tuning jobs. This gives you the ability to clean up the tuning jobs that you no longer would like to see in the ListHyperParameterTuningJob APIs, reuse tuning job names, and streamline your tuning job history.
Starting today, you can delete your tuning jobs using the new DeleteHyperParameterTuningJob API. You have now the flexibility to reuse job names for different tuning experiments as well as the capability to eliminate previous tuning jobs, be it for reasons related to security standards or any other consideration. Whenever you have tuning jobs in a terminal state (Stopped, Completed, or Failed), you can use the new API to delete them.
You can use the DeleteHyperParameterTuningJob API directly if you have admin access to your account, or you can specify ‘allow’ access to the sagemaker:DeleteHyperParameterTuningJob IAM action if you use your account with a specific policy template. Note that deleting the tuning job does not affect the training jobs that the tuning job created.
The new functionality is now available for SageMaker Automatic Model Tuning in all commercial [AWS Regions](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/). To learn more, please visit the [API reference guide](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API%5FTuningJobCompletionCriteria.html), the [technical documentation](https://docs.aws.amazon.com/sagemaker/latest/dg/automatic-model-tuning-define-metrics-variables.html), or SageMaker Automatic Model Tuning [web page](https://aws.amazon.com/sagemaker/automatic-model-tuning/).
What else is happening at Amazon Web Services?
Read update
Services
Share
Read update
Services
Share
Amazon Managed Service for Prometheus now supports configuring a minimum firing period for alerts
October 16th, 2024
Services
Share