Amazon SageMaker for ML Workflows

Amazon SageMaker was renamed Amazon SageMaker AI, while many existing API namespaces and resource names continue to use SageMaker. It provides a managed environment for common ML tasks such as training jobs, hosted inference, and model workflows. Teams can use built-in frameworks or bring their own containers, and can connect the service with AWS storage, identity, logging, and pipeline tools. A training job packages code, data locations, instance configuration, and output artifacts. Managed infrastructure provisions compute for the job and stores outputs where configured. Hosted endpoints keep capacity available for online requests, while batch workflows can score larger datasets without an always-on endpoint. Pipelines can connect steps such as preprocessing, training, evaluation, and registration, though teams still define how decisions and validation gates work. Managed services reduce some operations work but introduce cloud-specific configuration. Identity roles control access to data and artifacts. Networking, container images, quotas, encryption, logs, and region choice affect deployment. A training job that completes does not prove the model was evaluated correctly, and a model registry entry does not by itself establish production approval. Cost depends on chosen compute, duration, storage, data movement, logs, endpoint uptime, and optional managed features. Online endpoints can incur charges while provisioned even when request volume is low. Training resources may bill during startup or job execution according to provider rules. Check current AWS pricing and account limits for the exact region and instance family before estimating. A useful first project creates one repeatable training job, evaluates its artifact, and deploys a bounded endpoint only if the use case needs one. Track the model, data, code, configuration, and costs. Shut down or delete temporary resources after experiments and verify what storage or endpoint capacity remains.