SageMaker Studio and ML Environments
Explore the AWS SageMaker Studio ecosystem and its environments tailored for different ML personas and stages. Understand how Studio, Studio Classic, and Studio Lab differ, learn about Data Wrangler for data preparation, and see how Canvas enables no-code ML. Discover integration with tools like Git, CI/CD pipelines, and AWS services that support automated production ML workflows.
SageMaker Studio is a unified, web-based integrated development environment for the entire machine learning life cycle on AWS. This lesson walks through the SageMaker Studio ecosystem, covering Studio, Studio Classic, Studio Lab, Data Wrangler, Canvas, and supported IDEs. Each component maps to a specific stage of the ML pipeline and serves a distinct persona, whether that persona is a data scientist iterating on notebooks, an ML engineer building production pipelines, or a business analyst generating predictions without code.
Note: The exam frequently tests your ability to distinguish SageMaker Studio (an ML life cycle hub) from AWS Glue (ETL and data cataloging). Studio handles ML-focused workflows, and Glue handles broader data integration tasks.
Different ML personas benefit from different environments within the SageMaker Studio ecosystem, and the exam expects you to match tools to use cases precisely. The sections that follow break down each component, its integration points, and the trade-offs that drive architectural decisions.
Studio environment options and trade-offs
Three distinct environments exist under the SageMaker Studio umbrella, each targeting different use cases across the ML life cycle.
SageMaker Studio is the latest-generation, fully integrated ML IDE. It supports JupyterLab
SageMaker Studio Classic is the legacy, notebook-focused predecessor. It provides a single-user JupyterServer experience without the Spaces abstraction. SageMaker Studio Classic remains available for backward compatibility, ...