AWS Machine Learning Specialty study materials
AWS Machine Learning Specialty study resources

AWS Machine Learning Specialty (AWS) study plan

AWS Machine Learning Specialty · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Modeling & Exploratory Data Analysis

  • Map each major SageMaker built-in algorithm family to the problem type it solves (regression, classification, clustering, dimensionality reduction, NLP, computer vision, forecasting)

  • Describe the SageMaker training job lifecycle end to end: estimator, container image, input channels, output artifacts, and distributed training modes

  • Compute accuracy, precision, recall, F1, ROC-AUC, and RMSE by hand from a small confusion matrix and state when each one misleads

  • Profile a real dataset with Data Wrangler and load it into S3 and Feature Store

Your checkpoint

A one-page algorithm-selection cheat sheet plus a notebook that profiles a real dataset and reports six evaluation metrics with a written note on which metric the business problem favors and why.

Week 2

Modeling & Exploratory Data Analysis

  • Train three different built-in algorithms on the same dataset and compare validation results on a common metric

  • Run an automatic model tuning job and interpret the objective metric, ranges, and best-training-job output

  • Apply regularization and class-imbalance techniques (weighting, resampling, threshold shifting) and measure the effect

  • Detect and remediate skewed features, missing values, and outliers using Data Wrangler and SageMaker Processing

  • Read a correlation matrix and a PCA projection to justify dropping or keeping specific features

Your checkpoint

A tuning report containing job logs for three algorithms, a comparison table of validation metrics, a feature-drop justification, and a one-paragraph recommendation.

Week 3

Modeling & Exploratory Data Analysis

  • Package a Bring-Your-Own-Script or framework estimator and run it through a complete training job

  • Configure a Bayesian hyperparameter search with sensible static and categorical ranges and a defensible objective metric

  • Generate a SageMaker Clarify explainability and bias report and interpret the feature-attribution output

  • Establish a per-run record of parameters, metrics, and artifacts so experiments are reproducible

Your checkpoint

An end-to-end notebook that trains a BYO-script model, runs a tuning job, and exports a Clarify bias and explainability report with a short interpretation section.

Week 4

Exploratory Data Analysis & Data Engineering

  • Compare Parquet, ORC, Avro, and CSV on query cost and compression, and select a partition scheme for a stated query pattern

  • Query S3 data with Athena and cut bytes scanned using partitioning plus columnar compression

  • Convert raw semi-structured logs into partitioned columnar data with Glue ETL or DataBrew recipes

  • Answer one stated business question from the curated data with a chart or dashboard

Your checkpoint

A data-lake mini-project: raw CSV to partitioned Parquet in S3 to an Athena query, documented with a before/after bytes-scanned and runtime table.

Week 5

Data Engineering & Exploratory Data Analysis

  • Stream records through Kinesis Data Streams or Firehose into S3 and query the landed data with Athena

  • Orchestrate a multi-step pipeline with Glue workflows or Step Functions and configure retry and failure handling

  • Apply imputation, encoding, and scaling at scale with Spark on Glue or EMR Serverless

  • Distinguish Feature Store online versus offline stores and explain which serves training versus low-latency inference

Your checkpoint

A pipeline diagram plus a run log of a streaming ingest to transform to query flow, with retry behavior and failure handling written down.

Week 6

Data Engineering & Machine Learning Implementation and Operations

  • Deploy one trained model to a real-time endpoint and to a batch transform job, then compare latency, cost, and operational overhead

  • Configure endpoint autoscaling, instance selection, and a multi-model endpoint for a stated traffic pattern

  • Lock down the pipeline with IAM execution roles, VPC endpoints, KMS encryption, and least-privilege S3 bucket policies

  • Automate training, registration, and deployment with SageMaker Pipelines and the Model Registry

Your checkpoint

A commit-to-endpoint pipeline that trains, registers a model version, and updates an endpoint, shipped with the IAM policy file and a cost-estimate table.

Week 7

Machine Learning Implementation and Operations & Modeling

  • Configure model monitor for data drift and bias drift and interpret what a triggered violation means

  • Diagnose a failing or degraded endpoint using CloudWatch metrics, logs, and Debugger output

  • Choose between A/B testing, shadow deployment, and blue/green rollout for a given risk profile and justify the choice

  • Close two self-identified weak modeling areas (for example time-series forecasting, recommendation, or text algorithms)

Your checkpoint

An operations runbook covering five incident scenarios, each with the detecting metric, its threshold, and the remediation step.

Week 8

Modeling & Machine Learning Implementation and Operations

  • Complete two full-length timed practice exams and log every missed question by domain

  • Re-derive each missed answer from primary AWS documentation and record the exact doc section

  • Explain the main SageMaker cost drivers (training hours, endpoint uptime, storage, and data processing) and identify where to cut spend

  • Rehearse selection rules: Glue versus EMR versus Athena, batch versus real time, built-in versus custom container, single versus multi-model endpoint

Your checkpoint

A scored practice-exam log with domain-level accuracy, every sub-80% area tagged to the documentation link that fixes it, and a written go/no-go decision on the exam date.

Milestones

Week 2: Given an unfamiliar business problem, select and justify both a built-in algorithm and the primary evaluation metric in under three minutes without notes.

Week 4: Design an S3 data lake layout (format, partitioning, compression, catalog) that answers a stated query at minimum bytes scanned, and defend each choice.

Week 6: Trace a model from source commit to live endpoint, naming the IAM and KMS control at each hop and the most likely failure mode at each.

Week 8: Two timed practice exams completed with at least 80% accuracy in all four domains and a remediation link recorded for every miss.