Amazon SageMaker Guide: Building, Training and Deploying ML

What Is Amazon SageMaker?

Building a machine learning model on a laptop is fairly easy. Amazon SageMaker is built for the next part: getting a model into production reliably, securely and at scale, which is where most organizations struggle. Infrastructure, distributed training, model versioning, endpoint management and governance can take months of engineering before a single prediction reaches a customer, and data scientists often spend more time on infrastructure and data preparation than on modeling.

Amazon SageMaker is a fully managed platform from Amazon Web Services that covers the entire machine learning lifecycle, from data preparation and model training to deployment, monitoring, and governance. Rather than stitching together standalone tools, SageMaker provides an integrated environment where data scientists, ML engineers, and analysts can collaborate on a shared platform with enterprise-grade security built in.

Amazon SageMaker Since 2017

Originally launched in 2017, SageMaker has changed a lot. On July 30, 2026, AWS also moved several SageMaker AI features to maintenance mode and closed them to new customers: Augmented AI (A2I), Clarify, Debugger, Geospatial, Ground Truth, Model Monitor, Role Manager and Studio Lab. Existing customers can keep using them. At re:Invent 2024, AWS announced the “next generation” of SageMaker: expanding it from a pure ML platform into a unified data, analytics, and AI environment. As part of this evolution, the original SageMaker was renamed SageMaker AI and now sits alongside a new component called SageMaker Unified Studio.

In short, this change reflects a broader industry shift. Organizations no longer treat ML as a siloed function: they need their data engineering, analytics, and machine learning teams working on the same governed data, in the same workspace, with shared security policies. Previously, teams had to switch between separate AWS consoles for data processing (EMR, Glue), SQL analytics (Athena, Redshift), ML development (SageMaker), and generative AI (Bedrock). The next generation of SageMaker unifies all of these into a single, governed platform, reducing context-switching and ensuring that everyone operates on the same source of truth.

Amazon SageMaker by the Numbers

SageMaker is used across industries, and AWS lists customers such as Roche, Toyota, Swiss Life, Natera, BASF, Cisco (Webex) and Figma, from pharmaceuticals and automotive to financial services and healthcare.

Where Amazon SageMaker Fits in the AWS AI Ecosystem

Understanding the distinction between SageMaker and Amazon Bedrock is critical, because many teams confuse them:

• Amazon SageMaker: Build, train, and deploy your own models. So choose SageMaker when you need to train custom models on proprietary data, require full control over the ML lifecycle, or are working with traditional ML workloads (classification, regression, forecasting, anomaly detection).
• Amazon Bedrock: Access pre-trained foundation models via API. Or choose Bedrock when you want to use existing AI models for generative AI applications without managing training infrastructure.

In practice, many organizations use both. Bedrock handles generative AI inference while SageMaker manages custom model training, fine-tuning, and MLOps pipelines. So they are complementary layers of a complete AI strategy, not competing services. Also, within SageMaker Unified Studio, you can access Bedrock’s abilities directly: building generative AI applications alongside your custom ML workflows in the same governed workspace. This integration means you do not have to choose between platforms; you can leverage the strengths of each depending on the task at hand.

How Amazon SageMaker Works

SageMaker is a managed layer over AWS compute (EC2 and EKS), storage (S3 and EBS) and container orchestration. In addition, it provides a control plane for each phase of the ML lifecycle and hides the infrastructure work that used to slow teams down, by handling provisioning, scaling, teardown and cleanup across the workflow.

The Two Components of Next-Generation Amazon SageMaker

Since re:Invent 2024, SageMaker consists of two primary components working together:

• SageMaker Unified Studio: A single, integrated development environment that brings together tools from Amazon EMR, AWS Glue, Amazon Athena, Amazon Redshift, Amazon Bedrock, and SageMaker AI. It provides one workspace for data preparation, SQL analytics, big data processing, model development, and generative AI application building, eliminating the need to jump between separate AWS consoles.
• Data and AI Governance: Enterprise-level security and data management throughout the entire data and AI lifecycle. For example, this includes SageMaker Catalog for data discovery, fine-grained access controls, data lineage tracking, and responsible AI policies.

The Amazon SageMaker Lifecycle: Build Phase

SageMaker organizes the machine learning workflow into three core phases, each supported by purpose-built tools.

First, prepare your data, explore features, and write training code. SageMaker provides fully managed Jupyter notebooks, a built-in Data Agent that generates SQL from natural language, and integration with S3 data lakes and Redshift data warehouses. Also, SageMaker Feature Store lets you create, share, and reuse engineered features across teams: preventing duplicated effort and ensuring consistency. Also, SageMaker Data Wrangler provides a visual interface for data transformation, allowing you to clean, normalize, and encode features without writing code. For teams working with unstructured data, Ground Truth provides managed labeling workflows that combine human annotators with active learning to reduce labeling costs by up to 70%.

The ML Lifecycle: Train Phase

Next, launch distributed training jobs on managed infrastructure without provisioning servers. SageMaker handles instance allocation, scales across multiple GPUs or nodes, and automatically shuts down resources when training completes. Also, SageMaker supports all major frameworks including PyTorch, TensorFlow, XGBoost, Scikit-learn, Hugging Face, and custom containers, so you are never locked into a proprietary framework. Beyond framework support, SageMaker Debugger, which profiled training jobs for bottlenecks, is closed to new customers since July 30, 2026, so new projects should use framework profilers and CloudWatch metrics instead. Automatic Model Tuning (hyperparameter optimization) also runs parallel training jobs with different settings and picks the best-performing combination.

The ML Lifecycle: Deploy Phase

Finally, push trained models to managed endpoints for real-time inference, batch transform jobs, or serverless endpoints. SageMaker handles autoscaling, health monitoring, A/B testing with traffic splitting, and shadow deployments. So you can roll out new model versions with zero downtime and automatically roll back if quality degrades. Also, SageMaker Model Monitor continuously evaluates deployed models for data drift, prediction drift, bias drift, and feature attribution drift: alerting you when model quality begins to degrade so you can retrain before business impact occurs.

Open Lakehouse Architecture

The next generation of SageMaker is built on an open lakehouse architecture. This unifies access to data across Amazon S3 data lakes, Amazon Redshift data warehouses, and external federated data sources using Apache Iceberg as the open table format. As a result, you can query all your data with any Iceberg-compatible tool or engine, without moving or duplicating data between systems.

So this eliminates data silos and ensures that your ML training datasets, analytics queries, and governance policies all operate on the same governed data layer. Previously, data teams often maintained separate copies of data in S3 for ML training and in Redshift for business analytics: leading to inconsistencies, stale data, and duplicated storage costs. With the lakehouse architecture, both workloads read from the same source of truth.

Also, the Iceberg table format provides critical abilities for ML workflows: time travel (query data as it existed at any point in time), schema evolution (add or modify columns without rewriting data), and partition evolution (change partitioning strategies without data movement). For ML teams, time travel is particularly valuable: it lets you reproduce exactly which data was used to train any historical model version, a requirement for regulatory compliance and debugging model behavior.

Core Features and Abilities

Since its launch, SageMaker’s feature set has grown extensively. Below are the abilities that matter most for teams building production ML systems.

Advanced Training Infrastructure

For organizations training large models, SageMaker provides purpose-built infrastructure beyond standard GPU instances. SageMaker HyperPod now supports Amazon EKS in addition to Slurm-based orchestration: integrating seamlessly with existing Kubernetes-based training pipelines. Also, support for AWS Trainium chips (purpose-built for ML training) offers 30-40% better price-performance than comparable GPU options, with Trainium3 expected to deliver an additional 40% improvement in early 2026.

Managed Spot Training is another critical cost optimization feature. It uses spare EC2 capacity for training jobs at significant discounts compared to on-demand pricing. SageMaker automatically handles interruptions by checkpointing progress and resuming when capacity becomes available, so you save on compute without risking lost training progress.

MLOps and Model Lifecycle Management

Moving beyond individual experiments, SageMaker Pipelines provides the infrastructure for operationalizing ML workflows. Pipelines lets you define each step of your ML process, data processing, training, evaluation, registration, and deployment, as a directed acyclic graph (DAG) that executes automatically. Combined with Model Registry for versioning and approval workflows, this creates a CI/CD pipeline for machine learning.

SageMaker Model Monitor checks deployed models for data quality drift, model quality drift, bias drift and feature attribution drift, and raises CloudWatch alerts when drift passes your thresholds. Model Monitor moved to maintenance mode and closed to new customers on July 30, 2026, so existing users can keep it, while new projects should plan monitoring with CloudWatch metrics and their own drift checks or another tool.

SageMaker Clarify provides bias detection and explainability, which matters in regulated industries where decisions on loans, insurance, diagnoses or hiring must be explained to regulators, auditors and affected people. Clarify also moved to maintenance mode and closed to new customers on July 30, 2026.

Talk to an ExpertTaking a model from notebook to production? Plan your SageMaker setup with us.

SageMaker Pricing Model and Cost Optimization

SageMaker pricing is usage-based: you pay for the compute, storage, and data processing resources you consume, with no upfront commitments required. However, the pricing has multiple moving parts that can lead to unexpected costs if not managed carefully.

Key Amazon SageMaker Cost Dimensions

Rather than listing specific dollar amounts that change over time, here are the primary cost drivers you need to understand:

• Training compute: Billed per second of instance usage during training jobs. Instance costs vary dramatically based on type: CPU instances cost a fraction of GPU instances, and Trainium-based instances offer better price-performance than comparable GPUs. So choosing the right instance type for your workload is the single highest-impact cost decision.
• Inference endpoints: Billed per hour of endpoint uptime, regardless of traffic volume. Real-time endpoints run continuously, so idle endpoints accumulate cost. Or serverless inference endpoints scale to zero when unused, charging only for active processing time.
• Notebook instances: Billed per hour of uptime. Forgetting to stop notebook instances after use is one of the most common sources of wasted SageMaker spend.
• Storage: S3 storage for training data, model artifacts, and outputs. EBS volumes attached to notebook and training instances also incur charges.
• Data processing: Costs for SageMaker Processing jobs, Feature Store operations, and Data Wrangler transformations.

Strategies to Control Costs

Based on our experience managing SageMaker deployments for enterprise clients, these strategies deliver the most significant savings:

• Leverage Managed Spot Training: This feature uses spare EC2 capacity at significant discounts for training jobs. SageMaker handles interruptions automatically through checkpointing, resuming training when capacity becomes available. For fault-tolerant workloads, spot training can reduce compute costs substantially without increasing total training time.
• Right-size instance types aggressively: Start training on smaller instances and scale up only when training time or memory constraints require it. In our experience, many workloads are over-provisioned from the start: teams default to large GPU instances for tasks that run well on CPU or smaller GPU instances.
• Switch to serverless inference where possible: For workloads with variable or unpredictable traffic, serverless endpoints eliminate idle costs entirely by scaling to zero between requests. This is particularly effective for internal tools, batch scoring applications, and development environments.
• Implement lifecycle configurations for notebooks: Automatically stop notebook instances after a configurable period of inactivity. Surprisingly, this single automation can save thousands per month across a team of data scientists who forget to shut down instances at the end of the day.
• Monitor costs proactively with tags and Cost Explorer: Tag all SageMaker resources by team, project, and environment. Use AWS Cost Explorer and Budgets to set spending alerts and identify the highest-cost areas. Without tagging, cost attribution across teams becomes nearly impossible.
• Consider AWS Trainium for large training jobs: According to AWS, Trainium2-based instances offer 30-40% better price-performance than comparable GPU instances. Migration needs some code changes, but the savings can be large for teams that train often.

Security, Privacy, and Compliance

Without a doubt, SageMaker is designed for enterprise environments where data sensitivity and regulatory compliance are paramount. Every component, from notebooks to training jobs to inference endpoints, operates within the AWS security boundary.

Amazon SageMaker Data Protection Controls

SageMaker provides several critical security abilities. First, all data is encrypted at rest using AWS KMS and in transit using TLS. Second, training jobs and endpoints run inside your VPC with no internet access by default: isolating your ML workloads from the public internet. Third, IAM policies provide fine-grained access control over every SageMaker API action, resource, and data asset. Fourth, SageMaker supports network isolation mode for training jobs, ensuring that containers cannot make outbound network calls during training: a critical control for sensitive data environments.

Also, SageMaker Unified Studio extends governance across the entire data and AI lifecycle through SageMaker Catalog. This provides centralized data discovery with AI-generated metadata, fine-grained access policies, sensitive data detection, data lineage tracking, and responsible AI guardrails. So organizations can maintain compliance and auditability from raw data through model deployment. Also, data quality monitoring automatically validates datasets against defined rules, alerting teams when incoming data deviates from expected distributions: preventing silent model degradation caused by upstream data issues.

Also, for organizations operating in highly regulated environments, SageMaker supports model cards that document model behavior, intended use cases, and evaluation results. Combined with ML lineage tracking that records every artifact, parameter, and transformation in the model development process, SageMaker creates a complete audit trail that satisfies regulatory scrutiny.

Compliance Standards

Amazon SageMaker is in scope for SOC 1/2/3, PCI DSS, ISO 27001, ISO 27017, ISO 27018, FedRAMP, HIPAA, and GDPR. Also, VPC isolation, private connectivity via PrivateLink, and encryption at every layer make SageMaker suitable for the most sensitive workloads in financial services, healthcare, and government.

What’s New in Amazon SageMaker (2024-2026)

The 2024-2026 period represents the most significant transformation in SageMaker’s history. Here are the key milestones:

The Custom Silicon Advantage

The hardware behind SageMaker training is changing quickly. Trainium2 chips are available in SageMaker HyperPod clusters, and AWS says they offer 30-40% better price-performance than comparable GPU instances for training. AWS has also announced Trainium3. SageMaker still supports a full range of NVIDIA GPU instances, so teams can pick the hardware that fits their workload and budget.

Real-World SageMaker Use Cases

SageMaker serves teams building custom ML, from classic predictive analytics to fine-tuning generative AI models. These are the production use cases we implement most often for clients:

Amazon SageMaker vs Azure Machine Learning

If you are evaluating ML platforms across cloud providers, here is how SageMaker compares with Microsoft’s Azure Machine Learning:

Making the Right Platform Decision

Both are mature, enterprise-grade ML platforms. Your cloud ecosystem is the primary decision factor. If your organization runs on AWS, SageMaker provides the deepest integration with S3, Redshift, EMR, and the broader AWS stack. Conversely, if you are a Microsoft-centric organization, Azure ML integrates natively with Azure Synapse, Power BI, and Microsoft Fabric.

However, SageMaker’s differentiators in 2026 extend beyond basic ML abilities. The Unified Studio provides a single workspace for data engineering, SQL analytics, ML development, and generative AI: an integrated experience that Azure achieves only by combining multiple separate services (Azure ML, Synapse, Power BI). Also, the open lakehouse architecture based on Apache Iceberg ensures data portability. Also, custom chip support through AWS Trainium and Inferentia delivers cost-effective training and inference that Azure cannot match without NVIDIA GPU pricing.

For organizations evaluating multi-cloud strategies, SageMaker’s reliance on open frameworks (PyTorch, TensorFlow, Iceberg) and containerized workloads means that trained models and training code are portable, even though the orchestration layer is AWS-specific. Your ML intellectual property is never locked in. Also, the open lakehouse architecture based on Apache Iceberg ensures that your data remains accessible to any compatible query engine, providing an additional layer of portability that proprietary data warehouse formats cannot match.

Getting Started with Amazon SageMaker

Setting up SageMaker requires creating a domain and project. Here is a step-by-step walkthrough:

Creating Your Domain and Project

Navigate to the Amazon SageMaker console in the AWS Management Console. Select Set up SageMaker to create a unified domain: this configures user authentication, networking, default storage, and execution roles. The domain setup establishes the security boundary for all SageMaker activities in your account.

Next, create a new project within SageMaker Unified Studio. Projects organize your notebooks, datasets, models, and deployment artifacts into governed workspaces with access controls. Each project can have its own team members, data connections, and compute configurations, enabling multiple teams to work independently while sharing the same governed infrastructure.

Also, you can connect data sources during project setup. SageMaker supports direct connections to S3, Redshift, Athena, AWS Glue Data Catalog, and third-party federated sources. Once connected, your data is discoverable through SageMaker Catalog with AI-generated metadata, so team members can search for datasets without filing support tickets.

Launching Your First Training Job

Below is a minimal Python example using the SageMaker SDK to train an XGBoost model:

import sagemaker
from sagemaker import Session
from sagemaker.inputs import TrainingInput
from sagemaker.xgboost import XGBoost

# Initialize session
session = Session()
role = sagemaker.get_execution_role()
bucket = session.default_bucket()

# Configure the estimator
estimator = XGBoost(
    entry_point='train.py',
    role=role,
    instance_count=1,
    instance_type='ml.m5.xlarge',
    framework_version='1.7-1',
    output_path=f's3://{bucket}/models/'
)

# Launch training
estimator.fit({
    'train': TrainingInput(f's3://{bucket}/data/train.csv'),
    'validation': TrainingInput(f's3://{bucket}/data/val.csv')
})

Then SageMaker provisions the instance, runs your training script, saves the model artifact to S3, and terminates the instance automatically. So you only pay for the actual training time: no idle compute charges.

Or for a no-code experience, use Autopilot in Unified Studio: upload a CSV dataset, specify the target column, and Autopilot automatically builds, trains, and ranks multiple models, providing full visibility into the generated code and explanations for each candidate model.

SageMaker Best Practices and Pitfalls

Based on our experience deploying SageMaker across enterprise environments, these practices consistently determine whether ML projects succeed or stall.

Production Deployment Recommendations

• Use SageMaker Pipelines from the start: Even for early experiments, define your workflow as a pipeline. This makes the transition from experimentation to production repeatable and auditable, rather than relying on ad-hoc notebook runs that cannot be reproduced.
• Monitor deployed models for drift: Model quality degrades as real-world data shifts. Existing users can keep SageMaker Model Monitor, which detects data, prediction and feature attribution drift; new projects should plan drift monitoring with CloudWatch metrics and their own checks, since Model Monitor is closed to new customers.
• Tag every resource: Apply consistent tags (team, project, environment, cost center) to all SageMaker resources. This enables cost attribution, access control policies, and operational visibility across teams.
• Use Feature Store for consistency: Centralize feature engineering in SageMaker Feature Store rather than duplicating feature logic across notebooks. This ensures that training and inference use identical feature transformations, eliminating a common source of training-serving skew.
• Automate cleanup: Implement automated shutdown of notebook instances, deletion of old training artifacts, and retirement of unused endpoints. Orphaned resources are the leading cause of unexpected SageMaker bills.

Our ServiceData Analytics, Business Intelligence and Artificial Intelligence

Frequently Asked Questions About Amazon SageMaker

References

1. SageMaker AI Features Moving to Maintenance July 30, 2026: AWS What’s New — AWS Service Availability Updates, June 2026
2. Next Generation of SageMaker and Unified Studio: AWS — Amazon SageMaker
3. Trainium2 30-40% Better Price-Performance: AWS — AWS Trainium
4. Customers: AWS — Amazon SageMaker AI Customers