Resource Management Operations
Introduction & Overview
Welcome to your second lesson in managing ML resources with the SageMaker AI Console. In the previous lesson, you learned to navigate and explore your console environment—finding training jobs, checking endpoints, and understanding what's currently running. Now you'll learn to actively manage these resources by making updates, removing unused components, and keeping your environment clean and cost-effective.
Our focus is on four essential management operations: updating endpoint configurations to optimize performance and costs, deleting unused endpoints, removing endpoint configurations that are no longer needed, and cleaning up obsolete models from your registry. By the end, you'll be able to confidently modify running deployments and maintain a well-organized ML infrastructure.
Editing Endpoint Runtime Configuration
One of the most common management tasks you'll perform is updating endpoint configurations to better match your actual needs. Whether you need more computational power for increased traffic or want to reduce costs by right-sizing over-provisioned resources, the SageMaker console makes these updates straightforward.
The following video demonstrates how to access an endpoint's configuration and make runtime updates through the console interface.
Understanding how to update endpoint configurations gives you the flexibility to adapt your deployments as requirements change, ensuring optimal performance while controlling costs.
Deleting Endpoints
When endpoints are no longer needed, removing them is one of the most effective ways to reduce AWS costs immediately. Once deleted, the endpoint stops immediately and can't be recovered, though you can recreate it later using the same model and configuration.
Watch the next video to see how to identify and delete unused endpoints through the console safely.
Mastering endpoint deletion helps you maintain cost-effective deployments by removing resources that are no longer serving a business purpose.
Deleting Endpoint Configurations
After you delete an endpoint, the endpoint configuration that defined its deployment settings still exists in your environment. These configurations specify instance types, scaling settings, and other deployment parameters, but once they're no longer used by any endpoints, they become clutter that should be removed to maintain organization.
Before deleting an endpoint configuration, you need to ensure no active endpoints are using it. The console shows you which endpoints, if any, are associated with each configuration. Once you've confirmed a configuration is unused, deletion is permanent and immediate.
The following video demonstrates how to identify unused endpoint configurations and remove them safely.
Keeping your endpoint configurations clean makes it easier to find and reuse the configurations you actually need for future deployments.
