AWS Certified Data Engineer – Associate DEA-C01 Exam Learning Path

AWS Certified Data Engineer - Associate DEA-C01

AWS Certified Data Engineer – Associate DEA-C01 Exam Learning Path

  • Just cleared the AWS Certified Data Engineer – Associate DEA-C01 exam with a score of 930/1000.
  • AWS Certified Data Engineer – Associate DEA-C01 exam is the latest AWS exam released on 12th March 2024.

AWS Certified Data Engineer - Associate DEA-C01

📋 Exam Guide Updated – Version 1.1 (December 2025)

AWS released Version 1.1 of the DEA-C01 exam guide in December 2025 with significant updates:

  • New skills added: LLM integration for data processing, open table formats (Apache Iceberg), vector index types (HNSW, IVF), vectorization concepts (Amazon Bedrock knowledge base), SageMaker Unified Studio governance
  • New in-scope services: Amazon Aurora, Amazon Q, Amazon Bedrock, Amazon Kendra, AWS Data Exchange, Amazon S3 Tables
  • Services removed from scope: AWS Cloud9, AWS CodeCommit, AWS Schema Conversion Tool (AWS SCT)
  • Service deprecations removed from out-of-scope: Amazon Honeycode, Amazon WorkDocs, Amazon Timestream, Amazon CodeWhisperer

Refer DEA-C01 Exam Guide Revisions for full details.

AWS Certified Data Engineer – Associate DEA-C01 Exam Content

  • Data Engineer exam validates skills and knowledge in core data-related AWS services, ability to ingest and transform data, orchestrate data pipelines while applying programming concepts, design data models, manage data life cycles, and ensure data quality.
  • Exam also validates a candidate’s ability to complete the following tasks:
    • Ingest and transform data, and orchestrate data pipelines while applying programming concepts.
    • Choose an optimal data store, design data models, catalog data schemas, and manage data lifecycles.
    • Operationalize, maintain, and monitor data pipelines. Analyze data and ensure data quality.
    • Implement appropriate authentication, authorization, data encryption, privacy, and governance. Enable logging
  • (New in v1.1) Integrate Large Language Models (LLM) for data processing.
  • (New in v1.1) Manage open table formats (e.g., Apache Iceberg).
  • (New in v1.1) Apply storage services including vector index types (HNSW, IVF) and services like Amazon Aurora PostgreSQL and Amazon MemoryDB.
  • (New in v1.1) Use infrastructure as code (IaC) for repeatable resource deployment (AWS CloudFormation, AWS CDK).

Refer AWS Certified Data Engineer – Associate DEA-C01 Exam Guide

AWS Certified Data Engineer – Associate DEA-C01 Exam Summary

  • DEA-C01 exam consists of 65 questions in 130 minutes, and the time is more than sufficient if you are well-prepared.
  • DEA-C01 exam includes two types of questions, multiple-choice and multiple-response.
  • DEA-C01 has a scaled score between 100 and 1,000. The scaled score needed to pass the exam is 720.
  • Associate exams currently cost $ 150 + tax.
  • You can get an additional 30 minutes if English is your second language by requesting Exam Accommodations. It might not be needed for Associate exams but is helpful for Professional and Specialty ones.
  • AWS exams can be taken either remotely or online, I prefer to take them online as it provides a lot of flexibility. Just make sure you have a proper place to take the exam with no disturbance and nothing around you.
  • Also, if you are taking the AWS Online exam for the first time try to join at least 30 minutes before the actual time as I have had issues with both PSI and Pearson with long wait times.

AWS Certified Data Engineer – Associate DEA-C01 Exam Resources

AWS Certified Data Engineer – Associate DEA-C01 Exam Topics

  • DEA-C01 Exam covers the data engineering aspects in terms of data ingestion, transformation, orchestration, designing data models, managing data life cycles, and ensuring data quality.
  • (Updated v1.1) Exam now also covers LLM integration, open table formats (Iceberg), vector databases, and generative AI services like Amazon Bedrock and Amazon Q.

Analytics

  • Ensure you know and cover all the services in-depth, as 80% of the exam focuses on topics like Glue, Athena, Kinesis, and Redshift.
  • AWS Analytics Services Cheat Sheet
  • Glue
    • DEA-C01 covers Glue in great detail.
    • AWS Glue is a fully managed, ETL service that automates the time-consuming steps of data preparation for analytics.
    • supports server-side encryption for data at rest and SSL for data in motion.
    • Glue ETL engine to Extract, Transform, and Load data that can automatically generate Scala or Python code.
    • Glue Data Catalog is a central repository and persistent metadata store to store structural and operational metadata for all the data assets. It works with Apache Hive as its metastore.
    • (New – June 2026) Glue Data Catalog now supports business context and semantic search, enabling data discovery by semantic meaning with glossary terms and custom metadata fields.
    • Glue Crawlers scan various data stores to automatically infer schemas and partition structures to populate the Data Catalog with corresponding table definitions and statistics.
    • Glue Job Bookmark tracks data that has already been processed during a previous run of an ETL job by persisting state information from the job run.
    • Glue Streaming ETL enables performing ETL operations on streaming data using continuously running jobs.
    • Glue provides a flexible scheduler that handles dependency resolution, job monitoring, and retries.
    • Glue Studio offers a graphical interface for authoring AWS Glue jobs to process data allowing you to define the flow of the data sources, transformations, and targets in the visual interface and generating Apache Spark code on your behalf.
    • Glue Data Quality helps reduce manual data quality efforts by automatically measuring and monitoring the quality of data in data lakes and pipelines. (Updated) Now supports rule labeling for organizing and analyzing data quality results by category, team, or domain.
    • Glue DataBrew helps prepare, visualize, clean, and normalize data directly from the data lake, data warehouses, and databases, including S3, Redshift, Aurora, and RDS.
    • Glue Flex execution option helps to reduce the costs of pre-production, test, and non-urgent data integration workloads by up to 34% and is ideal for customer workloads that don’t require fast jobs start times.
    • Glue FindMatches transform helps identify duplicate or matching records in the dataset, even when the records do not have a common unique identifier and no fields match exactly.
    • (New) AWS Glue 5.1 (GA Nov 2025) introduces support for Apache Iceberg format version 3.0 (deletion vectors, row lineage), Iceberg Materialized Views, and Spark-native fine-grained access control with AWS Lake Formation for data writes.
    • (New) Glue Interactive Sessions now support Spark Connect for interactive workloads, enabling step-by-step debugging and incremental PySpark development.
    • (Deprecation Note) AWS Glue for Ray will no longer be open to new customers starting April 30, 2026. For similar capabilities, explore Amazon EKS.
  • Kinesis
    • Understand Kinesis Data Streams and Amazon Data Firehose (formerly Kinesis Data Firehose) in-depth.
    • Know Kinesis Data Streams vs Amazon Data Firehose
      • Know Kinesis Data Streams is open-ended for both producer and consumer. It supports KCL and works with Spark.
      • Know Amazon Data Firehose is open-ended for producers only. Data is stored in S3, Redshift, OpenSearch, Splunk, Snowflake, and other 3rd-party analytics services.
      • Amazon Data Firehose works in batches with minimum 60secs intervals and in near-real time.
      • Amazon Data Firehose supports out-of-the-box transformation and custom transformation using Lambda
    • (Rename – Feb 2024) Amazon Kinesis Data Firehose has been renamed to Amazon Data Firehose. The service functionality remains the same.
    • Kinesis supports encryption at rest using server-side encryption
    • Kinesis supports Interface VPC endpoint to keep traffic between the VPC and Kinesis Data Streams from leaving the Amazon network and doesn’t require an internet gateway, NAT device, VPN connection, or Direct Connect connection.
    • Kinesis Producer Library supports batching
    • Amazon Managed Service for Apache Flink (formerly Kinesis Data Analytics)
      • (Rename – Aug 2023) Amazon Kinesis Data Analytics has been renamed to Amazon Managed Service for Apache Flink.
      • helps transform and analyze streaming data in real time using Apache Flink.
      • supports anomaly detection using Random Cut Forest ML
      • supports reference data stored in S3.
      • (EOL – Jan 2026) Kinesis Data Analytics for SQL applications reached end of support on January 27, 2026. Migrate to Amazon Managed Service for Apache Flink for real-time stream processing workloads.
  • Redshift
    • Redshift is also covered in depth.
    • Redshift Advanced include
      • Redshift Distribution Style determines how data is distributed across compute nodes and helps minimize the impact of the redistribution step by locating the data where it needs to be before the query is executed.
      • Redshift Enhanced VPC routing forces all COPY and UNLOAD traffic between the cluster and the data repositories through the VPC.
      • Workload management (WLM) enables users to flexibly manage priorities within workloads so that short, fast-running queries won’t get stuck in queues behind long-running queries.
      • Redshift Spectrum
        • helps query structured and semistructured data from files in S3 without having to load the data into Redshift tables.
        • cannot access data from Glacier.
      • Federated Query feature allows querying and analyzing data across operational databases, data warehouses, and data lakes.
      • Short query acceleration (SQA) prioritizes selected short-running queries ahead of longer-running queries.
      • Concurrency Scaling helps support thousands of concurrent users and concurrent queries, with consistently fast query performance.
      • Redshift Serverless is a serverless option of Redshift that makes it more efficient to run and scale analytics in seconds without the need to set up and manage data warehouse infrastructure. (Updated) AI-driven scaling and optimization is now the default for all new Serverless workgroups, using ML to predict compute needs and automatically adjust resources.
      • Streaming ingestion provides low-latency, high-speed ingestion of stream data from Kinesis Data Streams and Managed Streaming for Apache Kafka into a Redshift provisioned or Redshift Serverless materialized view.
      • Redshift data sharing can securely share access to live data across Redshift clusters, workgroups, AWS accounts, and AWS Regions without manually moving or copying the data.
      • Redshift Data API provides a secure HTTP endpoint and integration with AWS SDKs to help access Redshift data with web services–based applications, including AWS Lambda, SageMaker notebooks, and AWS Cloud9.
      • (New) Amazon Redshift RG is a new Graviton-powered instance family that delivers up to 2.4x faster performance than RA3 at 30% lower price per vCPU.
      • (New) Redshift now supports autonomics for multi-cluster environments, extending ATO, ATS, Auto Vacuum, and Auto Analyze across consumer clusters.
    • Redshift Best Practices w.r.t selection of Distribution style, Sort key, importing/exporting data
      • COPY command which allows parallelism, and performs better than multiple COPY commands
      • COPY command can use manifest files to load data
      • COPY command handles encrypted data
    • Redshift Resizing cluster options (elastic resize did not support node type changes before, but does now)
    • Redshift supports encryption at rest and in transit
    • Redshift supports encrypting an unencrypted cluster using KMS. However, you can’t enable hardware security module (HSM) encryption by modifying the cluster. Instead, create a new, HSM-encrypted cluster and migrate your data to the new cluster.
    • Know Redshift views to control access to data.
  • Athena
    • is a serverless, interactive analytics service built on open-source frameworks, supporting open-table and file formats.
    • provides a simplified, flexible way to analyze data in an S3 data lake and 30 data sources, including on-premises data sources or other cloud systems using SQL or Python without loading the data.
    • integrates with Amazon Quick (formerly QuickSight) for visualizing the data or creating dashboards.
    • uses a managed Glue Data Catalog to store information and schemas about the databases and tables for the data stored in S3.
    • Workgroups can be used to separate users, teams, applications, or workloads, to set limits on the amount of data each query or the entire workgroup can process, and to track costs.
    • Athena best practices
      • Data partitioning,
      • Partition projection, and
      • Columnar file formats like ORC or Parquet as they support compression and are splittable.
    • (New) Athena for Apache Spark is available in SageMaker notebooks with live Spark UI debugging, Lake Formation table-level access controls, and Spark Connect support.
    • (New) Athena now offers managed connectors for 12 data sources (DynamoDB, PostgreSQL, MySQL, Snowflake) without deploying or maintaining connector resources.
    • (Updated v1.1) Exam now tests SQL skills in both Redshift and Athena for querying data and creating views.
  • Elastic Map Reduce
    • Understand EMRFS
      • Use Consistent view to make sure S3 objects referred by different applications are in sync. Although, it is not needed now.
    • Know EMR Best Practices (hint: start with many small nodes instead of few large nodes)
    • Know EMR Encryption options
      • supports SSE-S3, SS3-KMS, CSE-KMS, and CSE-Custom encryption for EMRFS
      • supports LUKS encryption for local disks
      • supports TLS for data in transit encryption
      • supports EBS encryption
    • Hive metastore can be externally hosted using RDS, Aurora, and AWS Glue Data Catalog
    • (New) Amazon EMR Serverless eliminates local storage provisioning for Apache Spark workloads, reducing data processing costs by up to 20% and preventing job failures from disk capacity constraints.
    • (New) EMR Serverless supports interactive sessions with Spark Connect for development from SageMaker Unified Studio notebooks and IDEs.
    • (New) Apache Spark upgrade agent for EMR uses AI to analyze code, identify required changes, and perform automated transformations for version upgrades.
  • OpenSearch
    • OpenSearch is a search service that supports indexing, full-text search, faceting, etc.
    • OpenSearch can be used for analysis and supports visualization using OpenSearch Dashboards which can be real-time.
    • OpenSearch Service Storage tiers support Hot, UltraWarm, and Cold and the data can be transitioned using Index State management.
  • Amazon Quick (formerly QuickSight)
    • (Rename – Oct 2025) Amazon QuickSight has been rebranded to Amazon Quick (also referred to as Amazon Quick Suite), expanding from a standalone BI service to a comprehensive analytics and AI platform.
    • Know Supported Data Sources
    • Amazon Quick provides IP addresses that need to be whitelisted to access the data store.
    • Amazon Quick provides direct integration with Microsoft AD
    • Amazon Quick supports row-level security using dataset rules to control access to data at row granularity based on permissions associated with the user interacting with the data.
    • Amazon Quick supports ML insights as well
    • Amazon Quick supports users defined via IAM or email signup.
    • (New) Amazon Q generative SQL integration helps generate SQL for Redshift or Athena queries using natural language.
  • AWS Lake Formation
    • is an integrated data lake service that helps to discover, ingest, clean, catalog, transform, and secure data and make it available for analysis.
    • automatically manages access to the registered data in S3 through services including AWS Glue, Athena, Redshift, Amazon Quick, and EMR
    • provides central access control for the data, including table-and-column-level access controls, and encryption for data at rest.
    • (New) Lake Formation now supports Spark-native fine-grained access control for data writes in AWS Glue 5.1.
    • (New) Lake Formation integrates with Amazon S3 Tables for cross-account data mesh architectures without copying data or managing cross-account S3 bucket policies.
  • Simple Storage Service – S3 as a storage service
    • S3 storage classes with lifecycle policies based on usage to provide cost-effective storage solutions.
    • S3 Event Notifications integrates with SNS and Lambda for real-time data processing
    • (New – Dec 2024) Amazon S3 Tables provide fully managed Apache Iceberg tables optimized for analytics workloads with up to 3x faster query throughput and 10x higher transactions per second compared to self-managed tables. Includes automatic compaction, snapshot management, and unreferenced file cleanup.
  • Data Pipeline
    • ⚠️ Closed to New Customers (July 2024): AWS closed new customer access to AWS Data Pipeline effective July 25, 2024. Existing customers can continue to use the service. No new features or region expansions are planned. Consider migrating to AWS Step Functions, Amazon MWAA, or AWS Glue workflows.
  • Step Functions help build distributed applications, automate processes, orchestrate microservices, and create data and ML pipelines.
    • Provides native integrations with over 200 AWS services and external third-party APIs.
    • (New) Step Functions added 28 new service integrations including Amazon Bedrock AgentCore and Amazon S3 Vectors.
  • (New) Amazon Managed Workflows for Apache Airflow (MWAA)
    • A managed service to run Apache Airflow for workflow orchestration at scale without managing infrastructure.
    • Now supports Apache Airflow 3.x with redesigned UI, API-based task execution, and scheduler-based backfills.
    • (New – Nov 2025) Amazon MWAA Serverless eliminates operational overhead with true serverless scaling and cost optimization.
    • Know when to use MWAA vs Step Functions: MWAA is ideal for complex data pipelines with many dependencies; Step Functions is better for event-driven serverless workflows.
  • AppFlow is a fully managed integration service to securely exchange data between software-as-a-service (SaaS) applications, such as Salesforce, and AWS services, such as Simple Storage Service (S3) and Redshift.

New In-Scope Services (Added in Exam Guide v1.1)

  • Amazon Bedrock
    • A fully managed service for building generative AI applications with foundation models.
    • (New in v1.1) Exam now tests ability to integrate LLMs for data processing and vectorization concepts using Bedrock knowledge bases.
    • Understand how to use Bedrock for data enrichment, text extraction, and unstructured data processing in pipelines.
  • Amazon Q
    • AI-powered assistant that generates SQL, provides data insights, and helps with data integration tasks.
    • Amazon Q generative SQL helps speed up deriving insights from Redshift and Glue Data Catalog data.
  • Amazon S3 Tables
    • Fully managed Apache Iceberg tables in S3, optimized for analytics workloads.
    • Automatic table maintenance: compaction, snapshot management, unreferenced file cleanup.
    • Integrates with Glue Data Catalog, Redshift, EMR, Athena, and SageMaker.
    • Delivers up to 3x faster query performance and 10x higher TPS vs self-managed Iceberg tables.
  • Amazon Aurora
    • Now in scope for the exam, particularly for vector indexing (HNSW with Aurora PostgreSQL) and as a data source for analytics pipelines.
  • Amazon Kendra
    • Intelligent search service powered by ML, useful for searching across data catalogs and documentation.
  • AWS Data Exchange
    • Service to find, subscribe to, and use third-party data in the cloud for analytics.
  • Amazon SageMaker Unified Studio
    • (New – GA March 2025) A single development environment bringing together data engineering, analytics, and ML workflows.
    • Combines functionality from Athena, EMR, Glue, Redshift, MWAA, and SageMaker Studio.
    • (v1.1) Exam tests use of domain, domain units, and projects for SageMaker Unified Studio governance.
    • Amazon SageMaker Catalog enables business data catalog creation and management with data lineage tracking.
  • Open Table Formats (Apache Iceberg)
    • (New in v1.1) Exam now requires understanding of managing open table formats like Apache Iceberg.
    • Key concepts: table versioning, time travel, schema evolution, partition evolution, compaction.
    • AWS services supporting Iceberg: S3 Tables, Glue, EMR, Athena, Redshift.
  • Vector Databases & Indexes
    • (New in v1.1) Understand vector index types like HNSW (Hierarchical Navigable Small World) and IVF (Inverted File Index).
    • Know services supporting vector storage: Aurora PostgreSQL (pgvector), Amazon MemoryDB, Amazon Bedrock Knowledge Bases.
    • Understand vectorization concepts and embedding generation for AI/ML pipelines.

Security, Identity & Compliance

  • Identity and Access Management (IAM)
    • Understand IAM Roles
    • (Updated v1.1) Understand authorization methods: role-based, tag-based, and attribute-based access control.
    • (Updated v1.1) Construct custom policies that meet the principle of least privilege.
  • Key Management Service (KMS) provides key management for encryption at rest.
  • AWS Secrets Manager
    • helps protect secrets needed to access applications, services, and IT resources.
  • Amazon Macie is a security service that uses machine learning to automatically discover, classify, and protect sensitive data in S3.
  • (New v1.1) Understand data sovereignty requirements and how to maintain them.
  • (New v1.1) Enable encryption in transit or before transit for data.

Management & Governance Tools

  • Understand AWS CloudWatch for Logs and Metrics.
  • CloudWatch Logs Subscription Filters can be used to route data to Kinesis Data Streams, Amazon Data Firehose, and Lambda.
  • (Updated v1.1) AWS Config for viewing configuration changes that have occurred in an account.

On the Exam Day

  • Make sure you are relaxed and get some good night’s sleep. The exam is not tough if you are well-prepared.
  • If you are taking the AWS Online exam
    • Try to join at least 30 minutes before the actual time as I have had issues with both PSI and Pearson with long wait times.
    • The online verification process does take some time and usually, there are glitches.
    • Remember, you would not be allowed to take the exam if you are late by more than 30 minutes.
    • Make sure you have your desk clear, no hand-watches, or external monitors, keep your phones away, and nobody can enter the room.

Finally, All the Best 🙂

AWS Redshift Advanced

AWS Redshift Advanced

  • Redshift Distribution Style determines how data is distributed across compute nodes and helps minimize the impact of the redistribution step by locating the data where it needs to be before the query is executed.
  • Redshift enhanced VPC routing forces all COPY and UNLOAD traffic between the cluster and the data repositories through the VPC.
  • Redshift workload management (WLM) enables users to flexibly manage priorities within workloads so that short, fast-running queries won’t get stuck in queues behind long-running queries.
  • Redshift Spectrum helps query and retrieve structured and semistructured data from files in S3 without having to load the data into Redshift tables.
  • Redshift Federated Query feature allows querying and analyzing data across operational databases, data warehouses, and data lakes.
  • Zero-ETL Integrations facilitate point-to-point data movement from operational databases to Redshift without the need to build and manage data pipelines.
  • Redshift Data Sharing enables live, transactionally consistent data sharing across Redshift clusters without copying data.
  • Redshift Serverless automatically provisions and scales data warehouse capacity without managing infrastructure.

Distribution Styles

  • Table distribution style determines how data is distributed across compute nodes and helps minimize the impact of the redistribution step by locating the data where it needs to be before the query is executed.
  • Redshift supports four distribution styles; AUTO, EVEN, KEY, or ALL.

KEY distribution

  • A single column acts as a distribution key (DISTKEY) and helps place matching values on the same node slice.
  • As a rule of thumb, choose a column that:
    • Is uniformly distributed – Otherwise skew data will cause unbalances in the volume of data that will be stored in each compute node leading to undesired situations where some slices will process bigger amounts of data than others and causing bottlenecks.
    • acts as a JOIN column – for tables related to dimensions tables (star-schema), it is better to choose as DISTKEY the field that acts as the JOIN field with the larger dimension table, so that matching values from the common columns are physically stored together, reducing the amount of data that needs to be broadcasted through the network.

EVEN distribution

  • distributes the rows across the slices in a round-robin fashion, regardless of the values in any particular column
  • Choose EVEN distribution
    • when the table does not participate in joins
    • when there is not a clear choice between KEY and ALL distribution.

ALL distribution

  • Whole table is replicated in every compute node.
  • ensures that every row is collocated for every join that the table participates in.
  • ideal for relatively slow-moving tables, tables that are not updated frequently or extensively.
  • Small dimension tables DO NOT benefit significantly from ALL distribution, because the cost of redistribution is low.

AUTO distribution

  • Redshift assigns an optimal distribution style based on the size of the table data for e.g. apply ALL distribution for a small table and as it grows changes it to Even distribution
  • Amazon Redshift applies AUTO distribution, by default.
  • Redshift’s automatic table optimization (ATO) continuously monitors query patterns and can automatically adjust distribution keys and sort keys for optimal performance.

Sort Key

  • Sort keys define the order in which the data will be stored.
  • Sorting enables efficient handling of range-restricted predicates.
  • Only one sort key per table can be defined, but it can be composed of one or more columns.
  • Redshift stores columnar data in 1 MB disk blocks. The min and max values for each block are stored as part of the metadata. If the query uses a range-restricted predicate, the query processor can use the min and max values to rapidly skip over large numbers of blocks during table scans
  • The are two kinds of sort keys in Redshift: Compound and Interleaved.

Compound Keys

  • A compound key is made up of all of the columns listed in the sort key definition, in the order, they are listed.
  • A compound sort key is more efficient when query predicates use a prefix, or query’s filter applies conditions, such as filters and joins, which is a subset of the sort key columns in order.
  • Compound sort keys might speed up joins, GROUP BY and ORDER BY operations, and window functions that use PARTITION BY and ORDER BY.

Interleaved Sort Keys

  • An interleaved sort key gives equal weight to each column in the sort key, so query predicates can use any subset of the columns that make up the sort key, in any order.
  • An interleaved sort key is more efficient when multiple queries use different columns for filters.
  • Don’t use an interleaved sort key on columns with monotonically increasing attributes, such as identity columns, dates, or timestamps.
  • Use cases involve performing ad-hoc multi-dimensional analytics, which often requires pivoting, filtering, and grouping data using different columns as query dimensions.
  • Note: AWS recommends using compound sort keys for most workloads. Interleaved sort keys require more maintenance (VACUUM REINDEX) and have higher overhead.

Constraints

  • Redshift does not support Indexes.
  • Redshift supports UNIQUE, PRIMARY KEY, and FOREIGN KEY constraints, however, they are only for informational purposes.
  • Redshift does not perform integrity checks for these constraints and is used by the query planner, as hints, in order to optimize executions.
  • Redshift does enforce NOT NULL column constraints.

Redshift Enhanced VPC Routing

  • Redshift enhanced VPC routing forces all COPY and UNLOAD traffic between the cluster and the data repositories through the VPC.
  • Without enhanced VPC routing, Redshift would route traffic through the internet, including traffic to other services within the AWS network.
  • Enhanced VPC routing is now supported for zero-ETL integration warehouses (as of September 2024), enabling secure data replication within the VPC.

Redshift Workload Management

  • Redshift workload management (WLM) enables users to flexibly manage priorities within workloads so that short, fast-running queries won’t get stuck in queues behind long-running queries.
  • Redshift provides query queues, in order to manage concurrency and resource planning. Each queue can be configured with the following parameters:
    • Slots: number of concurrent queries that can be executed in this queue.
    • Working memory: percentage of memory assigned to this queue.
    • Max. Execution Time: the amount of time a query is allowed to run before it is terminated.
  • Queries can be routed to different queues using Query Groups and User Groups.
  • As a rule of thumb, it is considered a best practice to have separate queues for long running resource-intensive queries and fast queries that don’t require big amounts of memory and CPU.
  • By default, Redshift configures one queue with a concurrency level of five, which enables up to five queries to run concurrently, plus one predefined Superuser queue, with a concurrency level of one.
  • A maximum of eight queues can be defined, with each queue configured with a maximum concurrency level of 50. The maximum total concurrency level for all user-defined queues (not including the Superuser queue) is 50.
  • Redshift WLM supports two modes – Manual and Automatic
    • Automatic WLM supports queue priorities.
    • Automatic WLM is the recommended mode and uses ML to dynamically allocate resources.
  • Query Monitoring Rules (QMR) define metrics-based performance boundaries for WLM queues and specify actions when a query exceeds those boundaries.
    • Up to 25 rules per queue, with a limit of 25 rules across all queues.
    • Each rule includes up to three conditions (predicates) and one action (log, cancel, hop, or change priority).
    • Queue-based QMR is now supported in Redshift Serverless (2026), enabling granular workload control.

Redshift Concurrency Scaling

  • Concurrency Scaling helps support thousands of concurrent users and concurrent queries, with consistently fast query performance.
  • With Concurrency scaling, Redshift automatically adds additional cluster capacity to process an increase in both read and write queries.
  • Queries run on the main cluster or a concurrency-scaling cluster returns the most current data.
  • Queries sent to the concurrency-scaling cluster can be managed by configuring WLM queues.
  • Concurrency scaling now supports more types of write queries (INSERT, CREATE TABLE AS, UPDATE, DELETE), expanding beyond read-only scaling.

Redshift Short Query Acceleration – SQA

  • Short query acceleration (SQA) prioritizes selected short-running queries ahead of longer-running queries.
  • SQA runs short-running queries in a dedicated space, so that SQA queries aren’t forced to wait in queues behind longer queries.
  • SQA only prioritizes queries that are short-running and are in a user-defined queue.

Redshift Loading Data

  • A COPY command is the most efficient way to load a table.
    • COPY command is able to read from multiple data files or multiple data streams simultaneously.
    • Redshift allocates the workload to the cluster nodes and performs the load operations in parallel, including sorting the rows and distributing data across node slices.
    • COPY command supports loading data from S3, EMR, DynamoDB, and remote hosts such as EC2 instances using SSH.
    • COPY supports decryption and can decrypt the data as it performs the load if the data is encrypted
    • COPY can then speed up the load process by uncompressing the files as they are read if the data is compressed.
    • COPY command can be used with COMPUPDATE set to ON to analyze and apply compression automatically based on sample data.
    • Optimizing storage for narrow tables (multiple rows few columns) by using Single COPY command instead of multiple COPY commands, as it would not work well due to hidden fields and compression issues.
  • Auto Copy
    • Auto-copy (GA October 2024) provides the ability to automate copy statements by tracking S3 folders and ingesting new files without customer intervention.
    • Without Auto-copy, a copy statement immediately starts the file ingestion process for existing files.
    • Auto-copy extends the existing copy command and provides the ability to
      • Automate file ingestion process by monitoring specified S3 paths for new files
      • Re-use copy configurations, reducing the need to create and run new copy statements for repetitive ingestion tasks and
      • Keep track of loaded files to avoid data duplication.
  • Streaming Ingestion
    • Redshift supports streaming ingestion from Amazon Kinesis Data Streams, Amazon MSK, Confluent Managed Cloud, and self-managed Apache Kafka clusters.
    • Streaming ingestion uses materialized views to ingest data from streams directly into Redshift tables for near real-time analytics.
    • Supports cascading refresh of nested materialized views on streaming sources (2025).
  • INSERT command
    • Clients can connect to Amazon Redshift using ODBC or JDBC and issue ‘insert’ SQL commands to insert the data.
    • INSERT command is much less efficient than using COPY as they are routed through the single leader node.

Redshift Resizing Cluster

  • Elastic resize
    • Use elastic resize to change the node type, number of nodes, or both.
    • If only the number of nodes is changed, then queries are temporarily paused and connections are held open if possible.
    • During the resize operation, the cluster is read-only.
    • Elastic resize takes 10–15 minutes.
  • Classic resize
    • Use classic resize to change the node type, number of nodes, or both.
    • During the resize operation, data is copied to a new cluster and the source cluster is read-only
    • Classic resize takes 2 hours – 2 days or longer, depending on the data’s size
  • Snapshot and restore with classic resize
    • To keep the cluster available during a classic resize, create a snapshot, make a copy of an existing cluster, then resize the new cluster.

Redshift Spectrum

  • Redshift Spectrum helps query and retrieve structured and semistructured data from files in S3 without having to load the data into Redshift tables.
  • Redshift Spectrum queries employ massive parallelism to execute very fast against large datasets. Much of the processing occurs in the Redshift Spectrum layer, and most of the data remains in S3.
  • Multiple clusters can concurrently query the same dataset in S3 without the need to make copies of the data for each cluster.
  • Redshift Spectrum resides on dedicated Redshift servers that are independent of the existing cluster.
  • Redshift Spectrum pushes many compute-intensive tasks, such as predicate filtering and aggregation, down to the Redshift Spectrum layer.
  • Redshift Spectrum also scales automatically, based on the demands of the queries, and can potentially use thousands of instances to take advantage of massively parallel processing.
  • Supports external data catalog using Glue, Athena, or Hive metastore
  • Supports querying Apache Iceberg tables and S3 Tables (purpose-built tabular storage with Iceberg support, launched at re:Invent 2024).
  • Iceberg query performance has improved up to 3x year-over-year through optimizations including Glue Data Catalog statistics, dynamic partition elimination, and parallel manifest file processing.
  • Supports incremental refresh for materialized views on data lake tables, eliminating the need for full recomputation when new data arrives.
  • Redshift cluster and the S3 bucket must be in the same AWS Region.
  • Redshift Spectrum external tables are read-only. You can’t COPY or INSERT to an external table.

Redshift Federated Query

  • Redshift Federated Query feature allows querying and analyzing data across operational databases, warehouses, and lakes.
  • Redshift Federated Query allows integrating queries on live data in RDS for PostgreSQL, Aurora PostgreSQL, RDS for MySQL, and Aurora MySQL with queries across Redshift and S3.
  • Supports both PostgreSQL and MySQL engines for federated access.

Zero-ETL Integrations

  • Zero-ETL integrations facilitate point-to-point data movement from operational databases to Redshift without the need to build and manage custom data pipelines.
  • Provides near real-time analytics on transactional data within seconds of it being written to the source.
  • Supported Sources:
    • Amazon Aurora MySQL-Compatible Edition (first zero-ETL source)
    • Amazon Aurora PostgreSQL-Compatible Edition (GA October 2024)
    • Amazon RDS for MySQL (GA September 2024)
    • Amazon DynamoDB (GA October 2024)
    • Self-managed databases (MySQL, PostgreSQL) via CDC replication
    • Enterprise Applications (re:Invent 2024): Salesforce, Zendesk, ServiceNow, SAP, Facebook Ads, Instagram Ads, Pardot, and Zoho CRM
  • Key Features:
    • Data filtering to selectively extract tables and schemas using regular expressions
    • Support for incremental and auto-refresh materialized views on replicated data
    • Configurable change data capture (CDC) refresh rates
    • Cross-account integrations within the same region
    • Supports both Redshift Serverless workgroups and provisioned clusters using RA3 instance types
    • Compatible with enhanced VPC routing and Multi-AZ deployments

Redshift Data Sharing

  • Redshift Data Sharing allows securely sharing live, transactionally consistent data between Redshift clusters without physically copying or moving data.
  • Supports cross-account and cross-Region data sharing.
  • For cross-account data sharing, both the producer and consumer cluster must be encrypted.
  • Producer clusters create datashares; consumer clusters associate with them via a two-way handshake for cross-account sharing.
  • Multi-data warehouse writes through data sharing (GA November 2024) allows writing to shared Redshift databases from multiple data warehouses, enabling distributed ETL workloads.
  • Supports data sharing with data lake tables, enabling unified access across warehouses and data lakes.
  • Works with both RA3 provisioned clusters and Redshift Serverless.
  • Integrated with AWS Lake Formation for fine-grained access control on shared data.

Redshift Serverless

  • Redshift Serverless automatically provisions and scales data warehouse capacity to deliver fast performance without managing infrastructure.
  • Pay only for compute capacity when the data warehouse is active, measured in Redshift Processing Units (RPUs).
  • Each RPU provides 16 GB of memory; base capacity ranges from 4 RPUs to 1024 RPUs.
  • Starting capacity as low as 4 RPUs ($1.50/hour), making it cost-effective for smaller workloads.
  • AI-driven scaling and optimization (GA October 2024, default for new workgroups April 2026):
    • Automatically learns workload patterns and adjusts compute resources based on query complexity, data volume, and scan size.
    • Offers a price-performance slider with five profiles from “Optimized for Cost” to “Optimized for Performance.”
    • Deploys automatic optimizations including materialized views and table design optimization.
    • Up to 10x price-performance improvement for variable workloads.
  • Serverless Reservations (April 2025): Commit to specific RPUs for a one-year term with 20% (no-upfront) or 24% (all-upfront) discount off on-demand rates.
  • Supports all Redshift features including data sharing, streaming ingestion, federated queries, and zero-ETL integrations.

Redshift Multi-AZ Deployments

  • Multi-AZ deployments (GA November 2023 for RA3 clusters) support running the data warehouse across multiple Availability Zones simultaneously.
  • Provides high availability by continuing operations during unforeseen failure scenarios in a single AZ.
  • Available for RA3 provisioned clusters in most commercial regions and GovCloud (US).
  • Compatible with zero-ETL integrations for highly available near real-time analytics.

Redshift Node Types

  • RG Instances (GA May 2026) – Latest generation powered by AWS Graviton processors
    • Up to 2.2x faster for data warehouse workloads and 2.4x faster for data lake workloads compared to RA3.
    • 30% lower price per vCPU compared to RA3 instances.
    • Includes a custom-built vectorized data lake query engine that processes Apache Iceberg and Parquet data on cluster nodes.
    • Available in rg.xlarge and rg.4xlarge node types.
    • Recommended upgrade path from RA3 instances.
  • RA3 Instances – Managed storage with separate compute and storage scaling
    • Available in ra3.xlplus, ra3.4xlarge, ra3.16xlarge, and ra3.large sizes.
    • Managed storage automatically tiers data between high-performance SSD and S3.
    • RA3.large (GA October 2024) offers a cost-effective migration path from DC2.large.
  • DC2 Instances – Dense compute with local SSD storage (legacy, migration to RA3/RG recommended)

Redshift Generative AI Integration

  • Amazon Q generative SQL (GA September 2024) in Redshift Query Editor allows users to express queries in natural language and receive SQL code recommendations.
  • Amazon Bedrock Integration (October 2024) enables invoking large language models (LLMs) from SQL commands for tasks like text generation, summarization, sentiment analysis, and language translation.
  • Amazon Bedrock Knowledge Bases supports natural language querying to retrieve structured data from Redshift warehouses, automatically translating questions into SQL.

Redshift SageMaker Lakehouse

  • Amazon SageMaker Lakehouse (re:Invent 2024) unifies data across S3 data lakes and Redshift warehouses.
  • Provides access via Apache Iceberg open standards for use with any Iceberg-compatible engine.
  • Existing Redshift data warehouses can be published to SageMaker Lakehouse, opening warehouse data with Iceberg REST API.
  • Supports creating new data lake tables using Redshift Managed Storage (RMS) as native storage.
  • Offers integrated access controls and fine-grained permissions through Lake Formation across all engines.

Redshift Behavior Changes and Deprecations

  • Python UDFs End of Support (June 30, 2026)
    • Creation of new Python UDFs blocked since October 30, 2025.
    • Existing Python UDFs will stop functioning after June 30, 2026.
    • Migration: Use Lambda UDFs which provide better integration, flexibility, scalability, and security.
  • ODBC 1.x Driver End of Support: September 30, 2026. Migrate to ODBC 2.x driver.
  • Minimum TLS Version: TLS 1.2 minimum required starting January 31, 2026.
  • Materialized View Auto-REFRESH Behavior Change: After February 27, 2026, auto-refresh respects workload priorities.

AWS Certification Exam Practice Questions

  • Questions are collected from Internet and the answers are marked as per my knowledge and understanding (which might differ with yours).
  • AWS services are updated everyday and both the answers and questions might be outdated soon, so research accordingly.
  • AWS exam questions are not updated to keep up the pace with AWS updates, so even if the underlying feature has changed the question might not be updated
  • Open to further feedback, discussion and correction.
  1. A Redshift data warehouse has different user teams that need to query the same table with very different query types. These user teams are experiencing poor performance. Which action improves performance for the user teams in this situation?
    1. Create custom table views.
    2. Add interleaved sort keys per team.
    3. Maintain team-specific copies of the table.
    4. Add support for workload management queue hopping.
  2. A company needs to replicate data from their Aurora PostgreSQL database to Redshift for near real-time analytics without building custom ETL pipelines. Which approach requires the LEAST operational overhead?
    1. Set up AWS Glue jobs to periodically extract and load data
    2. Use Amazon Kinesis Data Firehose to stream changes
    3. Configure Aurora PostgreSQL zero-ETL integration with Redshift
    4. Create Lambda functions triggered by DynamoDB Streams
  3. An organization uses Redshift Serverless and wants to optimize for cost during off-peak hours while maintaining performance during peak business hours. Which feature best addresses this requirement?
    1. Manual RPU scaling with CloudWatch alarms
    2. Concurrency Scaling with WLM queue configuration
    3. AI-driven scaling and optimization with cost-optimized profile
    4. Scheduled pause and resume of the Serverless workgroup
  4. A company wants to share live data from their Redshift cluster with a partner organization’s Redshift cluster in a different AWS account without copying data. What is the recommended approach?
    1. Use Redshift Spectrum with cross-account S3 access
    2. Set up AWS Data Exchange for data delivery
    3. Configure cross-account Redshift Data Sharing
    4. Use AWS Glue ETL to replicate data to the partner account
  5. A team wants to perform sentiment analysis on customer feedback stored in Redshift without moving data to a separate ML service. Which Redshift feature enables this?
    1. Redshift ML with SageMaker Autopilot
    2. Export to S3 and use Comprehend
    3. Amazon Redshift integration with Amazon Bedrock using SQL commands
    4. Redshift federated query to an NLP endpoint
  6. A company is migrating from RA3 instances and wants better price-performance for both data warehouse and data lake workloads. Which instance type should they consider?
    1. DC2.8xlarge for compute-intensive workloads
    2. RA3.16xlarge with AQUA enabled
    3. RG instances powered by AWS Graviton
    4. Redshift Serverless with 1024 RPU base capacity

Amazon Athena – Serverless Interactive Query Service

Athena

Amazon Athena

  • Amazon Athena is a serverless, interactive analytics service built on open-source frameworks, supporting open-table and file formats.
  • provides a simplified, flexible way to analyze petabytes of data in an S3 data lake and 30+ data sources, including on-premises data sources or other cloud systems using SQL or Python without loading the data.
  • is built on open-source Trino and Presto engines and Apache Spark frameworks, with no provisioning or configuration effort required.
  • supports Athena for Apache Spark, enabling serverless Spark applications for advanced analytics and machine learning workloads.
  • features Athena SQL v3 engine with improved performance, enhanced SQL capabilities, and better cost optimization.
  • offers Capacity Reservations with flexible options including 1-minute minimum reservations (down from 60 minutes), 4 DPU minimum (down from 24 DPU), auto-scaling, and per-query DPU controls for predictable performance and cost optimization.
  • is highly available and runs queries using compute resources across multiple facilities, automatically routing queries appropriately if a particular facility is unreachable
  • can process unstructured, semi-structured, and structured datasets.
  • integrates with QuickSight for visualizing the data or creating dashboards.
  • supports various standard data formats, including CSV, TSV, JSON, ORC, Avro, and Parquet.
  • supports modern table formats including Apache Iceberg, Delta Lake, and Apache Hudi for ACID transactions and time travel queries.
  • supports compressed data in Snappy, Zlib, LZO, ZSTD, and GZIP formats. You can improve performance and reduce costs by compressing, partitioning, and using columnar formats.
  • enables cross-region querying to analyze data stored across multiple AWS regions from a single query interface.
  • can handle complex analysis, including large joins, window functions, and arrays
  • uses a managed Glue Data Catalog to store information and schemas about the databases and tables that you create for the data stored in S3
  • uses schema-on-read technology, which means that the table definitions are applied to the data in S3 when queries are being applied. There’s no data loading or transformation required. Table definitions and schema can be deleted without impacting the underlying data stored in S3.
  • supports fine-grained access control with AWS Lake Formation which allows for centrally managing permissions and access control for data catalog resources in the S3 data lake.
  • integrates with Amazon DataZone for comprehensive data governance, cataloging, and discovery across the organization.
  • supports AWS Clean Rooms integration for privacy-preserving collaborative analytics without sharing raw data.
  • integrates with Amazon SageMaker Lakehouse for unified data access across data lakes and data warehouses with federated catalogs and Lake Formation governance controls.
  • supports Amazon S3 Tables integration to query Apache Iceberg tables stored in S3 Table Buckets with automated table management (compaction, snapshot management, garbage collection).
  • offers Managed Query Results that automatically stores, secures, and manages query result data at no cost, eliminating the need to provision S3 buckets for query results.
Athena
Source: Amazon

Athena Capacity Reservations

  • Capacity Reservations provide dedicated serverless capacity in the form of Data Processing Units (DPU) for mission-critical workloads, isolated from other queries in the account.
  • Capacity is fully managed by Athena and held for as long as needed, with no impact on account-level concurrency quotas.
  • 1-Minute Reservations (Feb 2026): Reserve capacity for as little as 1 minute (down from 60 minutes) with a minimum of 4 DPU (down from 24 DPU), enabling savings up to 95% for workloads completing in under an hour.
  • Auto-Scaling (Nov 2025): Built-in auto-scaling solution using AWS Step Functions that monitors CloudWatch utilization metrics at 1-minute granularity and automatically adjusts DPU capacity based on configurable thresholds.
  • DPU Cost and Performance Controls (Nov 2025): Set minimum and maximum DPU limits (4 to 124 DPU in increments of 4) at the workgroup level or per-query level to balance cost efficiency, concurrency, and performance.
  • Per-query DPU usage is now reported in the Athena console and via GetQueryExecution/BatchGetQueryExecution APIs for complete visibility into capacity utilization.
  • Workgroups are assigned to Capacity Reservations, and Athena automatically routes queries from assigned workgroups to reserved capacity.
  • Supports both on-demand (per-query scan-based) pricing and Capacity Reservations (DPU-hour based) pricing models.

Athena Workgroups

  • Athena workgroups can be used to separate users, teams, applications, or workloads, to set limits on amount of data each query or the entire workgroup can process, and to track costs.
  • Resource-level identity-based policies can be used to control access to a specific workgroup.
  • Workgroups help view query-related metrics in CloudWatch, control costs by configuring limits on the amount of data scanned, create thresholds, and trigger actions, such as SNS, when these thresholds are breached.
  • Workgroups now support query result reuse and caching to reduce costs and improve performance for repeated queries.
  • Enhanced cost controls with per-query data scanning limits and automatic query termination for runaway queries.
  • Workgroup-level encryption settings and fine-grained access controls for improved security governance.
  • Workgroups can be configured with Capacity Reservations for consistent performance and predictable costs.
  • IAM Identity Center Workgroups: Athena supports workgroups with IAM Identity Center authentication mode, enabling federated identity across AWS services like Athena and Amazon EMR Studio with trusted identity propagation.
  • Managed Query Results: Workgroups can use managed query results, removing the need to create or manage S3 buckets for storing query results. Results are available for 24 hours at no cost.
  • Workgroups integrate with IAM, CloudWatch, Simple Notification Service, and AWS Cost and Usage Reports as follows:
    • IAM identity-based policies with resource-level permissions control who can run queries in a workgroup.
    • Athena publishes the workgroup query metrics to CloudWatch if you enable query metrics.
    • SNS topics can be created that issue alarms to specified workgroup users when data usage controls for queries in a workgroup exceed the established thresholds.
    • Workgroup tag can be configured as a cost allocation tag in the Billing and Cost Management console and the costs associated with running queries in that workgroup appear in the Cost and Usage Reports with that cost allocation tag.
    • AWS CUR 2.0 now supports direct Athena and Redshift integration for analyzing cost data using standard SQL.

Athena Federated Queries

  • Athena Federated Query enables querying data across multiple sources including Amazon DynamoDB, Amazon RDS, Amazon Redshift, on-premises databases, and third-party sources like Snowflake without moving data.
  • Managed Connectors (Apr 2026): Athena now offers managed connectors for 12 data sources including DynamoDB, PostgreSQL, MySQL, and Snowflake. Athena automatically sets up and manages connector resources, registering the data source as a federated catalog in AWS Glue Data Catalog—no Lambda function deployment required.
  • Two types of connectors:
    • AWS Glue Data Catalog federated connectors – Use Glue connections with fine-grained governance through Lake Formation.
    • Athena data catalog federated connectors – Legacy connectors that require a Lambda function in your account.
  • Federated Passthrough Queries: Run queries on federated data sources using the native query language of the data source itself, pushing the full query down for execution.
  • Predicate Pushdown: Optimized connectors use dynamic filtering and expanded predicate pushdown to perform more operations at the source, reducing data transfer and improving performance.
  • SageMaker Lakehouse Integration: Federated catalogs through SageMaker Lakehouse enable unified data access with Lake Formation column-level, row-level, and cell-level security controls.
  • Supports cross-account federated queries to access data in other AWS accounts.
  • Federated views allow creating and querying views on federated data sources.

Athena Best Practices

  • Partition the data
    • which helps keep the related data together based on column values such as date, country, and region.
    • Athena supports Hive partitioning and advanced partition projection with custom expressions.
    • Use dynamic partition pruning for improved query performance with complex partition schemes.
    • Consider partition evolution strategies when using modern table formats like Iceberg.
    • Pick partition keys that will support the queries
    • Partition projection is an Athena feature that stores partition information not in the Glue Data Catalog but as rules in the properties of the table in AWS Glue.
  • Compression
    • Compressing the data can speed up queries significantly, as long as the files are either of an optimal size or the files are splittable.
    • Smaller data sizes reduce the data scanned from S3, resulting in lower costs of running queries and reduced network traffic.
    • Athena supports ZSTD compression with configurable compression levels for fine-tuned performance-size tradeoffs.
  • Optimize file sizes
    • Queries run more efficiently when data scanning can be parallelized and when blocks of data can be read sequentially.
  • Modern file formats and optimization
    • Columnar storage formats like ORC and Parquet remain optimal for analytical workloads.
    • Apache Iceberg tables provide ACID transactions, schema evolution, and time travel capabilities.
    • Delta Lake integration enables reliable data lakes with ACID guarantees.
    • Use Z-ordering and data clustering techniques for improved query performance.
    • S3 Table Buckets provide purpose-built storage for Iceberg tables with automated compaction, snapshot management, and garbage collection.
    • A splittable file can be read in parallel by the execution engine in Athena, whereas an unsplittable file can’t be read in parallel.
  • Query optimization and performance
    • Leverage query result caching and reuse for frequently executed queries.
    • Use EXPLAIN and ANALYZE statements to understand query execution plans.
    • Use the Cost-Based Optimizer (CBO) with AWS Glue column statistics for improved join reordering and aggregation pushdown.
    • Implement query performance monitoring with CloudWatch Insights.
    • Consider Capacity Reservations with DPU controls for consistent performance requirements.
    • Optimize queries by using appropriate WHERE clauses and avoiding SELECT * statements.
    • Use managed query results to eliminate S3 bucket management overhead for ad-hoc queries.

Security and Governance

  • Enhanced Lake Formation Integration: Row-level and cell-level security controls for fine-grained data access, now extended to federated catalogs through SageMaker Lakehouse.
  • Tag-Based Access Control (TBAC): Lake Formation TBAC now supports federated catalogs including S3 Tables, Redshift data warehouses, and federated data sources like DynamoDB, MySQL, and Snowflake.
  • Data Masking and Anonymization: Built-in functions for protecting sensitive data during queries.
  • Cross-Account Access: Secure data sharing across AWS accounts with resource-based policies and federated catalog governance.
  • Audit and Compliance: Comprehensive query logging and data lineage tracking through AWS CloudTrail and DataZone.
  • Encryption Enhancements: AWS recommends SSE-KMS encryption over SSE-S3 or CSE-KMS. Support for customer-managed KMS keys and field-level encryption.
  • Identity-Based Access Control: Integration with AWS IAM for fine-grained permissions, role-based access, and IAM Identity Center for trusted identity propagation.
  • VPC Endpoints: Private connectivity to Athena SQL and Athena Spark (PrivateLink support added Apr 2026) without internet gateway requirements.

Advanced Use Cases and Patterns

  • Machine Learning Integration: Query results can be directly used with Amazon SageMaker for ML model training and inference.
  • Real-time Analytics: Near real-time querying of streaming data from Kinesis Data Firehose with minimal latency.
  • Federated Queries: Query data across multiple sources including RDS, Redshift, DynamoDB, Snowflake, and on-premises databases using managed connectors or Lambda-based connectors.
  • Data Mesh Architecture: Athena serves as a query engine for decentralized data architectures with domain-specific data products, supported by SageMaker Lakehouse federated catalogs.
  • Serverless ETL Pipelines: Combine Athena with AWS Step Functions and Lambda for fully serverless data processing workflows.
  • Cost Optimization Patterns: Use Capacity Reservations with auto-scaling for predictable workloads, on-demand for sporadic queries, and DPU controls for fine-grained cost management.
  • Multi-Account Analytics: Centralized analytics across multiple AWS accounts using cross-account access patterns and federated catalogs.
  • Hybrid Cloud Analytics: Query on-premises data alongside cloud data using federated query capabilities and managed connectors.
  • S3 Table Buckets: Use Athena to query purpose-built Apache Iceberg tables in S3 Table Buckets for optimized analytics with automated maintenance.
  • Cost and Usage Analysis: AWS CUR 2.0 integrates directly with Athena and Redshift for analyzing AWS billing data without custom data warehouses.

AWS Certification Exam Practice Questions

  • Questions are collected from Internet and the answers are marked as per my knowledge and understanding (which might differ with yours).
  • AWS services are updated everyday and both the answers and questions might be outdated soon, so research accordingly.
  • AWS exam questions are not updated to keep up the pace with AWS updates, so even if the underlying feature has changed the question might not be updated
  • Open to further feedback, discussion and correction.
  1. A SysOps administrator is storing access logs in Amazon S3 and wants to use standard SQL to query data and generate a report without having to manage infrastructure. Which AWS service will allow the SysOps administrator to accomplish this task?
    1. Amazon Inspector
    2. Amazon CloudWatch
    3. Amazon Athena
    4. Amazon RDS
  2. A Solutions Architect must design a storage solution for incoming billing reports in CSV format. The data does not need to be scanned frequently and is discarded after 30 days. Which service will be MOST cost-effective in meeting these requirements?
    1. Import the logs into an RDS MySQL instance
    2. Use AWS Data pipeline to import the logs into a DynamoDB table
    3. Write the files to an S3 bucket and use Amazon Athena to query the data
    4. Import the logs to an Amazon Redshift cluster
  3. A data engineering team needs to implement ACID transactions and time travel queries on their data lake. They want to maintain compatibility with existing Athena queries while adding these capabilities. Which solution should they choose?
    1. Migrate to Amazon Redshift Spectrum
    2. Use Amazon EMR with Apache Hive
    3. Implement Apache Iceberg tables with Athena
    4. Use AWS Glue with Delta Lake format
  4. An organization wants to share analytical insights with external partners without exposing raw data. They need to perform collaborative analytics while maintaining data privacy. Which AWS service integration with Athena would be most appropriate?
    1. AWS Lake Formation with external account access
    2. AWS Clean Rooms with Athena integration
    3. Amazon QuickSight with embedded dashboards
    4. AWS DataSync with cross-account replication
  5. A company wants to optimize costs for their Athena workloads that have predictable query patterns and consistent performance requirements. Which Athena feature should they implement?
    1. Athena Federated Query
    2. Athena for Apache Spark
    3. Athena Capacity Reservations
    4. Athena Query Result Reuse
  6. A data platform team runs mission-critical dashboards that peak during morning hours and decrease throughout the day. They want dedicated capacity that adjusts automatically to match demand without manual intervention. Which combination of Athena features should they use?
    1. On-demand pricing with query result caching
    2. Capacity Reservations with manual DPU adjustments
    3. Capacity Reservations with auto-scaling solution
    4. Multiple workgroups with data scanning limits
  7. A company needs to query data stored in Amazon DynamoDB, PostgreSQL, and Snowflake from Athena without deploying or maintaining Lambda functions. Which Athena feature provides the simplest setup?
    1. Athena data catalog federated connectors with custom Lambda
    2. AWS Glue ETL jobs to copy data to S3
    3. Athena managed connectors registered as Glue Data Catalog federated catalogs
    4. Amazon Redshift Spectrum with external schemas
  8. A data analyst wants to run ad-hoc queries in Athena without configuring an S3 bucket for query results. Which Athena feature enables this workflow?
    1. Athena Query Result Reuse
    2. Athena Workgroup encryption settings
    3. Athena Managed Query Results
    4. Athena UNLOAD statement
  9. An organization wants to store tabular data in Apache Iceberg format with automated table maintenance including compaction and snapshot management, and query it using Athena. Which S3 feature should they use?
    1. S3 Intelligent-Tiering with lifecycle policies
    2. S3 Table Buckets
    3. S3 Express One Zone with directory buckets
    4. S3 Standard with AWS Glue crawlers
  10. A security team needs to enforce column-level and row-level access controls on Athena queries across federated data sources spanning multiple accounts. Which service combination provides the most comprehensive governance? (Select TWO)
    1. Amazon SageMaker Lakehouse with federated catalogs
    2. Amazon DataZone with data subscriptions
    3. AWS Lake Formation with tag-based access control (TBAC)
    4. AWS IAM policies with condition keys
    5. Amazon Macie with sensitive data discovery

References

AWS Certified Machine Learning -Specialty (MLS-C01) Exam Learning Path

AWS Machine Learning - Specialty Certification

⚠️ AWS Certified Machine Learning – Specialty (MLS-C01) RETIRED

The MLS-C01 exam was retired on March 31, 2026. The last day to take this exam has passed. Certification holders will still have an active certification for 3 years from the date it was earned.

This content is maintained for historical reference and foundational ML knowledge.

Replacement Certifications:

AWS Certified Machine Learning – Specialty (MLS-C01) Exam Learning Path

  • Finally Re-certified the updated AWS Certified Machine Learning – Specialty (MLS-C01) certification exam after 3 months of preparation.
  • In terms of the difficulty level of all professional and specialty certifications, I find this to be the toughest, partly because I am still diving deep into machine learning and relearned everything from basics for this certification.
  • Machine Learning is a vast specialization in itself and with AWS services, there is a lot to cover and know for the exam. This is the only exam, where the majority of the focus is on concepts outside of AWS i.e. pure machine learning. It also includes AWS Machine Learning and Data Engineering services.

AWS Certified Machine Learning – Specialty (MLS-C01) Exam Content

  • AWS Certified Machine Learning – Specialty (MLS-C01) exam validates
    • Select and justify the appropriate ML approach for a given business problem.
    • Identify appropriate AWS services to implement ML solutions.
    • Design and implement scalable, cost-optimized, reliable, and secure ML solutions.

Refer AWS Certified Machine Learning – Specialty Exam Guide for details

AWS Certified Machine Learning – Specialty Domains

AWS Certified Machine Learning – Specialty (MLS-C01) Exam Summary

  • Specialty exams are tough, lengthy, and tiresome. Most of the questions and answers options have a lot of prose and a lot of reading that needs to be done, so be sure you are prepared and manage your time well.
  • MLS-C01 exam has 65 questions to be solved in 170 minutes which gives you roughly 2 1/2 minutes to attempt each question.
  • MLS-C01 exam includes two types of questions, multiple-choice and multiple-response.
  • MLS-C01 has a scaled score between 100 and 1,000. The scaled score needed to pass the exam is 750.
  • Specialty exams currently cost $ 300 + tax.
  • You can get an additional 30 minutes if English is your second language by requesting Exam Accommodations. It might not be needed for Associate exams but is helpful for Professional and Specialty ones.
  • As always, mark the questions for review, move on, and come back to them after you are done with all.
  • As always, having a rough architecture or mental picture of the setup helps focus on the areas that you need to improve. Trust me, you will be able to eliminate 2 answers for sure and then need to focus on only the other two. Read the other 2 answers to check the difference area and that would help you reach the right answer or at least have a 50% chance of getting it right.
  • AWS exams can be taken either remotely or online, I prefer to take them online as it provides a lot of flexibility. Just make sure you have a proper place to take the exam with no disturbance and nothing around you.
  • Also, if you are taking the AWS Online exam for the first time try to join at least 30 minutes before the actual time as I have had issues with both PSI and Pearson with long wait times.

AWS ML/AI Certification Replacements (2024-2026)

AWS restructured its AI/ML certification portfolio in 2024-2026. The MLS-C01 was retired and replaced by three new certifications:

CertificationLevelCodeFocus
ML Engineer – AssociateAssociateMLA-C01Build, deploy, operationalize ML pipelines on AWS
AI PractitionerFoundationalAIF-C01AI/ML/GenAI concepts, responsible AI, AWS AI services
Generative AI Developer – ProfessionalProfessionalAIP-C01Production GenAI apps with Amazon Bedrock, RAG, agents

Note: The ML knowledge from MLS-C01 remains highly relevant for MLA-C01 and AIP-C01 exams. The core ML concepts (algorithms, evaluation, feature engineering) covered below are foundational for all three new certifications.

AWS Certified Machine Learning – Specialty (MLS-C01) Exam Resources

AWS Certified Machine Learning – Specialty (MLS-C01) Exam Topics

  • AWS Certified Machine Learning – Specialty exam covers a lot of Machine Learning concepts. It digs deep into Machine learning concepts, most of which are not related to AWS.
  • AWS Certified Machine Learning – Speciality exam covers the E2E Machine Learning lifecycle, right from data collection, transformation, making it usable and efficient for Machine Learning, pre-processing data for Machine Learning, training and validation, and implementation.

Machine Learning Concepts

  • Exploratory Data Analysis
    • Feature selection and Engineering
      • remove features that are not related to training
      • remove features that have the same values, very low correlation, very little variance, or a lot of missing values
      • Apply techniques like Principal Component Analysis (PCA) for dimensionality reduction i.e. reduce the number of features.
      • Apply techniques such as One-hot encoding and label encoding to help convert strings to numeric values, which are easier to process.
      • Apply Normalization i.e. values between 0 and 1 to handle data with large variance.
      • Apply feature engineering for feature reduction e.g. using a single height/weight feature instead of both features.
    • Handle Missing data
      • remove the feature or rows with missing data
      • impute using Mean/Median values – valid only for Numeric values and not categorical features also does not factor correlation between features
      • impute using k-NN, Multivariate Imputation by Chained Equation (MICE), Deep Learning – more accurate and helps factors correlation between features
    • Handle unbalanced data
      • Source more data
      • Oversample minority or Undersample majority
      • Data augmentation using techniques like Synthetic Minority Oversampling Technique (SMOTE).
  • Modeling
    • Know about Algorithms – Supervised, Unsupervised and Reinforcement and which algorithm is best suitable based on the available data either labelled or unlabelled.
      • Supervised learning trains on labeled data e.g. Linear regression. Logistic regression, Decision trees, Random Forests
      • Unsupervised learning trains on unlabelled data e.g. PCA, SVD, K-means
      • Reinforcement learning trained based on actions and rewards e.g. Q-Learning
    • Hyperparameters
      • are parameters exposed by machine learning algorithms that control how the underlying algorithm operates and their values affect the quality of the trained models
      • some of the common hyperparameters are learning rate, batch, epoch (hint: If the learning rate is too large, the minimum slope might be missed and the graph would oscillate. If the learning rate is too small, it requires too many steps which would take the process longer and is less efficient)
  • Evaluation
    • Know difference in evaluating model accuracy
      • Use Area Under the (Receiver Operating Characteristic) Curve (AUC) for Binary classification
      • Use root mean square error (RMSE) metric for regression
    • Understand Confusion matrix
      • A true positive is an outcome where the model correctly predicts the positive class. Similarly, a true negative is an outcome where the model correctly predicts the negative class.
      • A false positive is an outcome where the model incorrectly predicts the positive class. A false negative is an outcome where the model incorrectly predicts the negative class.
      • Recall or Sensitivity or TPR (True Positive Rate): Number of items correctly identified as positive out of total true positives- TP/(TP+FN) (hint: use this for cases like fraud detection, cost of marking non fraud as frauds is lower than marking fraud as non-frauds)
      • Specificity or TNR (True Negative Rate): Number of items correctly identified as negative out of total negatives- TN/(TN+FP) (hint: use this for cases like videos for kids, the cost of dropping few valid videos is lower than showing few bad ones)
    • Handle Overfitting problems
      • Simplify the model, by reducing the number of layers
      • Early Stopping – form of regularization while training a model with an iterative method, such as gradient descent
      • Data Augmentation
      • Regularization – technique to reduce the complexity of the model
      • Dropout is a regularization technique that prevents overfitting
      • Never train on test data

Machine Learning Services

  • Amazon SageMaker AI (renamed from Amazon SageMaker in Dec 2024)
    • Note: At re:Invent 2024, AWS introduced the next generation of Amazon SageMaker — a unified platform for data, analytics, and AI. The original SageMaker was renamed to Amazon SageMaker AI, which retains focus on building, training, and deploying ML models. The new Amazon SageMaker Unified Studio (GA March 2025) provides a single workspace for data engineering, analytics, ML, and GenAI development.
    • supports both File mode, Pipe mode, and Fast File mode
      • File mode loads all of the data from S3 to the training instance volumes VS Pipe mode streams data directly from S3
      • File mode needs disk space to store both the final model artifacts and the full training dataset. VS Pipe mode which helps reduce the required size for EBS volumes.
      • Fast File mode combines the ease of use of the existing File Mode with the performance of Pipe Mode.
    • Using RecordIO format allows algorithms to take advantage of Pipe mode when training the algorithms that support it.
    • supports Model tracking capability to manage up to thousands of machine learning model experiments
    • supports automatic scaling for production variants. Automatic scaling dynamically adjusts the number of instances provisioned for a production variant in response to changes in your workload
    • provides pre-built Docker images for its built-in algorithms and the supported deep learning frameworks used for training & inference
    • SageMaker Automatic Model Tuning
      • is the process of finding a set of hyperparameters for an algorithm that can yield an optimal model.
      • Best practices
        • limit the search to a smaller number as the difficulty of a hyperparameter tuning job depends primarily on the number of hyperparameters that Amazon SageMaker has to search
        • DO NOT specify a very large range to cover every possible value for a hyperparameter as it affects the success of hyperparameter optimization.
        • log-scaled hyperparameter can be converted to improve hyperparameter optimization.
        • running one training job at a time achieves the best results with the least amount of compute time.
        • Design distributed training jobs so that you get they report the objective metric that you want.
    • know how to take advantage of multiple GPUs (hint: increase learning rate and batch size w.r.t to the increase in GPUs)
    • AWS Inferentia and Inferentia2 chips provide high-performance ML inference acceleration. (Note: Elastic Inference was deprecated in April 2023; use Inferentia-based instances or SageMaker inference components instead.)
    • SageMaker AI Inference options:
      • Real-time inference is ideal for online inferences that have low latency or high throughput requirements.
      • Serverless Inference is ideal for intermittent or unpredictable traffic patterns as it manages all of the underlying infrastructure with no need to manage instances or scaling policies.
      • Batch Transform is suitable for offline processing when large amounts of data are available upfront and you don’t need a persistent endpoint.
      • Asynchronous Inference is ideal when you want to queue requests and have large payloads with long processing times.
    • SageMaker Model deployment allows deploying multiple variants of a model to the same SageMaker endpoint to test new models without impacting the user experience
      • Production Variants
        • supports A/B or Canary testing where you can allocate a portion of the inference requests to each variant.
        • helps compare production variants’ performance relative to each other.
      • Shadow Variants
        • replicates a portion of the inference requests that go to the production variant to the shadow variant.
        • logs the responses of the shadow variant for comparison and not returned to the caller.
        • helps test the performance of the shadow variant without exposing the caller to the response produced by the shadow variant.
    • SageMaker Managed Spot training can help use spot instances to save cost and with Checkpointing feature can save the state of ML models during training
    • SageMaker Feature Store – helps to create, share, and manage features for ML development. A centralized store for features and associated metadata so features can be easily discovered and reused.
    • SageMaker Debugger provides tools to debug training jobs and resolve problems such as overfitting, saturated activation functions, and vanishing gradients.
    • SageMaker Model Monitor monitors the quality of machine learning models in production and can help set alerts for deviations in model quality.
    • SageMaker Data Wrangler reduces the time to aggregate and prepare tabular and image data for ML from weeks to minutes.
    • SageMaker Experiments lets you create, manage, analyze, and compare machine learning experiments.
    • SageMaker Clarify helps detect potential bias and explain model predictions.
    • SageMaker Model Governance provides systematic visibility into ML model development, validation, and usage.
    • SageMaker Autopilot is an automated machine learning (AutoML) feature that automates the end-to-end process of building, training, tuning, and deploying ML models.
    • SageMaker Neo enables machine learning models to train once and run anywhere in the cloud and at the edge.
    • SageMaker HyperPod (launched 2023) provides resilient infrastructure for large-scale foundation model training with automatic fault recovery, reducing training costs by up to 40%.
    • SageMaker JumpStart is an ML hub for evaluating, comparing, and deploying foundation models (FMs) from leading providers including pre-trained models, solution templates, and example notebooks.
    • SageMaker Canvas provides a no-code visual interface for generating accurate ML predictions. It now also supports time-series forecasting (replacing Amazon Forecast for new customers).
    • SageMaker API and SageMaker Runtime support VPC interface endpoints powered by AWS PrivateLink.
    • Algorithms:
      • Blazing text provides Word2vec and text classification algorithms
      • DeepAR provides supervised learning algorithm for forecasting scalar (one-dimensional) time series (hint: train for new products based on existing products sales data).
      • Factorization machines provide supervised classification and regression tasks, helps capture interactions between features within high dimensional sparse datasets economically.
      • Image classification algorithm is a supervised learning algorithm that supports multi-label classification.
      • IP Insights is an unsupervised learning algorithm that learns the usage patterns for IPv4 addresses.
      • K-means is an unsupervised learning algorithm for clustering.
      • k-nearest neighbors (k-NN) algorithm is an index-based algorithm for classification or regression.
      • Latent Dirichlet Allocation (LDA) is an unsupervised algorithm to identify topics shared by documents within a text corpus.
      • Neural Topic Model (NTM) is an unsupervised algorithm to organize a corpus of documents into topics based on statistical distribution.
      • Linear models are supervised learning algorithms for classification or regression problems.
      • Object Detection algorithm detects and classifies objects in images using a single deep neural network.
      • Principal Component Analysis (PCA) is an unsupervised algorithm for dimensionality reduction.
      • Random Cut Forest (RCF) is an unsupervised algorithm for anomaly detection.
      • Sequence to Sequence is a supervised algorithm where input is a sequence of tokens and output is another sequence (hint: text summarization).
      • XGBoost is an optimized distributed gradient boosting algorithm for classification and regression.
  • SageMaker Ground Truth
    • provides automated data labeling using machine learning
    • helps build highly accurate training datasets quickly using Amazon Mechanical Turk
    • provides annotation consolidation to improve accuracy of data object labels
    • automated data labeling uses ML to label portions of data automatically without human workers

Machine Learning & AI Managed Services

  • Amazon Bedrock (launched 2023, major updates 2024-2026)
    • Fully managed service offering access to hundreds of foundation models (FMs) from leading AI companies (Anthropic, Meta, Mistral, Amazon, etc.) via a unified API.
    • Key capabilities: model evaluation, guardrails for responsible AI, knowledge bases (RAG), agents for task automation, fine-tuning, and model customization.
    • Bedrock AgentCore (2026) provides production-grade runtime for AI agents with orchestration and scaling.
    • Critical for the new AIP-C01 (Generative AI Developer) certification.
  • Amazon Q Business (GA April 2024)
    • Generative AI-powered assistant for finding information, gaining insight, and taking action using enterprise data.
    • Connects to 40+ enterprise data sources while respecting existing access controls.
    • Evolved from and supersedes many Amazon Kendra use cases for intelligent search.
  • Amazon Kendra – intelligent search service using NLP and ML algorithms. Still available but increasingly complemented/replaced by Amazon Q Business for enterprise search use cases.
  • Comprehend – natural language processing (NLP) service to find insights and relationships in text. Identifies language, extracts key phrases, entities, sentiment analysis, and topic modeling.
  • Lex – provides conversational interfaces using voice and text for building chatbots.
  • Polly – text-to-speech. Supports SSML tags (prosody) for adjusting speech rate, pitch, or volume. Supports pronunciation lexicons.
  • Rekognition – analyze images and video. Identifies objects, people, text, scenes, and activities.
  • Translate – natural and fluent language translation.
  • Transcribe – automatic speech recognition (ASR), speech-to-text.
  • Textract – extracts text, handwriting, and data from scanned documents using ML.
  • Augmented AI (Amazon A2I) – ML service for building human review workflows.
  • Amazon Forecast⚠️ No longer available to new customers (closed July 29, 2024). Existing customers can continue using the service. AWS recommends migrating to Amazon SageMaker Canvas for time-series forecasting.
  • AWS Panorama⚠️ End of Support: May 31, 2026. AWS Panorama brought computer vision to on-premises camera networks. After EOL, the service and appliances will no longer function. Consider alternatives like Amazon Rekognition, SageMaker Edge, or partner solutions.

Analytics

  • Make sure you know and understand data engineering concepts mainly in terms of data capture, migration, transformation, and storage.
  • Kinesis
    • Understand Kinesis Data Streams and Amazon Data Firehose (renamed from Kinesis Data Firehose in Feb 2024) in depth
    • Amazon Managed Service for Apache Flink (renamed from Kinesis Data Analytics in Aug 2023) can process and analyze streaming data using Apache Flink and integrates with Data Streams and Data Firehose. Note: Kinesis Data Analytics for SQL was discontinued January 27, 2026.
    • Know Kinesis Data Streams vs Data Firehose
      • Know Kinesis Data Streams is open ended on both producer and consumer. It supports KCL and works with Spark.
      • Know Data Firehose is open ended for producer only. Data is stored in S3, Redshift, and OpenSearch.
      • Data Firehose works in batches with minimum 60secs interval.
      • Amazon Data Firehose supports data transformation and record format conversion using Lambda function (hint: can be used for transforming csv or JSON into parquet)
    • Kinesis Video Streams provides a fully managed service to ingest, index, store, and stream live video.
  • OpenSearch (formerly ElasticSearch) is a search service that supports indexing, full-text search, faceting, etc.
  • AWS Data Pipeline⚠️ Closed to new customers (July 25, 2024). Existing customers can continue to use the service. AWS recommends migrating to AWS Glue, Step Functions, or Amazon MWAA (Managed Apache Airflow).
  • AWS Glue is a fully managed ETL (extract, transform, and load) service
    • helps setup, orchestrate, and monitor complex data flows.
    • Glue Data Catalog is a central repository to store structural and operational metadata for all data assets.
    • Glue Crawler connects to a data store, extracts the schema, and populates the Glue Data Catalog with metadata.
    • Glue DataBrew is a visual data preparation tool that enables users to clean and normalize data without writing any code.
  • DataSync is an online data transfer service that simplifies, automates, and accelerates moving data between storage systems and services.

Security, Identity & Compliance

  • Security is covered very lightly. (hint: SageMaker AI can read data from KMS-encrypted S3. Make sure the KMS key policies include the role attached with SageMaker)

Management & Governance Tools

  • Understand AWS CloudWatch for Logs and Metrics. (hint: SageMaker AI is integrated with CloudWatch and logs and metrics are all stored in it)

Storage

  • Understand Data Storage Options – Know patterns for S3 vs RDS vs DynamoDB vs Redshift. (hint: S3 is, by default, the data storage option or Big Data storage, and look for it in the answer.)

Whitepapers and articles

AWS SageMaker Built-in Algorithms Summary

SageMaker Built-in Algorothms

SageMaker AI Built-in Algorithms

📌 Naming Update (December 2024): On December 3, 2024, Amazon SageMaker was renamed to Amazon SageMaker AI. The “SageMaker” brand now refers to the next-generation unified platform for data, analytics, and AI. All built-in algorithms remain available under SageMaker AI.

  • SageMaker AI provides a suite of built-in algorithms, pre-trained models, and pre-built solution templates to help data scientists and ML practitioners get started on training and deploying ML models quickly.
  • SageMaker AI also provides SageMaker JumpStart with pre-trained foundation models (including LLMs like LLaMA, BLOOM, Falcon) for generative AI tasks such as text generation, summarization, and question answering.

SageMaker AI Built-in Algorithms

Tabular Data – Classification & Regression

AutoGluon-Tabular

  • is an open-source AutoML framework that succeeds by ensembling models and stacking them in multiple layers.
  • automatically performs data processing, model selection, and hyperparameter tuning.
  • used for both classification and regression tasks on tabular data.
  • supports CPU and GPU (single instance only) training.

CatBoost

  • is an implementation of the gradient-boosted trees algorithm that introduces ordered boosting and an innovative algorithm for processing categorical features.
  • used for both classification and regression tasks.
  • handles categorical features natively without requiring manual encoding.
  • supports CPU (single instance only) training.

LightGBM

  • is an implementation of the gradient-boosted trees algorithm that adds two novel techniques for improved efficiency and scalability.
  • uses Gradient-based One-Side Sampling (GOSS) and Exclusive Feature Bundling (EFB).
  • used for both classification and regression tasks.
  • supports CPU (single instance only) training.

TabTransformer

  • is a novel deep tabular data modeling architecture built on self-attention-based Transformers.
  • converts categorical features into contextual embeddings using Transformer layers.
  • used for both classification and regression tasks.
  • supports CPU and GPU (single instance only) training.

XGBoost (eXtreme Gradient Boosting)

  • is a popular and efficient open-source implementation of the gradient boosted trees algorithm.
  • Gradient boosting is a supervised learning algorithm that attempts to accurately predict a target variable by combining an ensemble of estimates from a set of simpler, weaker models.
  • supports both classification and regression tasks.
  • supports distributed training across multiple instances.

Linear Learner

  • are supervised learning algorithms used for solving either classification or regression problems.
  • learns a linear function for regression or a linear threshold function for classification.
  • supports distributed training.

K-nearest neighbors (k-NN) algorithm

  • is an index-based algorithm.
  • uses a non-parametric method for classification or regression.
  • For classification problems, the algorithm queries the k points that are closest to the sample point and returns the most frequently used label of their class as the predicted label.
  • For regression problems, the algorithm queries the k closest points to the sample point and returns the average of their feature values as the predicted value.

Factorization Machine

  • is a general-purpose supervised learning algorithm used for both classification and regression tasks.
  • extension of a linear model designed to capture interactions between features within high dimensional sparse datasets economically, such as click prediction and item recommendation.

Text-based

BlazingText algorithm

  • provides highly optimized implementations of the Word2vec and text classification algorithms.
  • Word2vec algorithm
    • useful for many downstream natural language processing (NLP) tasks, such as sentiment analysis, named entity recognition, machine translation, etc.
    • maps words to high-quality distributed vectors, whose representation is called word embeddings
    • word embeddings capture the semantic relationships between words.
  • Text classification
    • is an important task for applications performing web searches, information retrieval, ranking, and document classification
  • provides the Skip-gram and continuous bag-of-words (CBOW) training architectures

Text Classification – TensorFlow

  • is a supervised learning algorithm that supports transfer learning with many pretrained models from the TensorFlow Hub.
  • uses deep learning networks such as BERT which are highly accurate for text classification.
  • takes text as input and outputs probability for each of the class labels.
  • useful for sentiment analysis, spam detection, and document categorization.

Sequence to Sequence – seq2seq

  • is a supervised learning algorithm where the input is a sequence of tokens (for example, text, audio), and the output generated is another sequence of tokens.
  • key uses cases are machine translation (input a sentence from one language and predict what that sentence would be in another language), text summarization (input a longer string of words and predict a shorter string of words that is a summary), speech-to-text (audio clips converted into output sentences in tokens)

Forecasting

DeepAR

  • is a supervised learning algorithm for forecasting scalar (one-dimensional) time series using recurrent neural networks (RNN).
  • use the trained model to generate forecasts for new time series that are similar to the ones it has been trained on.
  • supports learning complex patterns from multiple related time series simultaneously.

Clustering

K-means algorithm

  • is an unsupervised learning algorithm for clustering
  • attempts to find discrete groupings within data, where members of a group are as similar as possible to one another and as different as possible from members of other groups

Topic Modelling

Latent Dirichlet Allocation (LDA)

  • is an unsupervised learning algorithm that attempts to describe a set of observations as a mixture of distinct categories.
  • used to discover a user-specified number of topics shared by documents within a text corpus.

Neural Topic Model (NTM)

  • is an unsupervised learning algorithm that is used to organize a corpus of documents into topics that contain word groupings based on their statistical distribution
  • Topic modeling can be used to classify or summarize documents based on the topics detected or to retrieve information or recommend content based on topic similarities.

Feature Reduction

Object2Vec

  • is a general-purpose neural embedding algorithm that is highly customizable
  • can learn low-dimensional dense embeddings of high-dimensional objects.
  • useful for duplicate detection, finding similar items, and relationship prediction.

Principal Component Analysis – PCA

  • is an unsupervised ML algorithm that attempts to reduce the dimensionality (number of features) within a dataset while still retaining as much information as possible.
  • projects data points onto the first few principal components (eigenvectors of the data’s covariance matrix).

Anomaly Detection

Random Cut Forest (RCF)

  • is an unsupervised algorithm for detecting anomalous data points within a data set.
  • detects data points that diverge from otherwise well-structured or patterned data.

IP Insights

  • is an unsupervised learning algorithm that learns the usage patterns for IPv4 addresses.
  • designed to capture associations between IPv4 addresses and various entities, such as user IDs or account numbers
  • useful for detecting suspicious login attempts from anomalous IP addresses.

Computer Vision – CV

Image Classification – MXNet

  • a supervised learning algorithm that supports multi-label classification
  • takes an image as input and outputs one or more labels
  • uses a convolutional neural network (ResNet) that can be trained from scratch or trained using transfer learning when a large number of training images are not available.
  • recommended input format is Apache MXNet RecordIO. Also supports raw images in .jpg or .png format.

Image Classification – TensorFlow

  • is a supervised learning algorithm that supports transfer learning with many pretrained models from the TensorFlow Hub.
  • uses deep learning networks such as MobileNet, ResNet, Inception, and EfficientNet for image classification.
  • takes an image as input and outputs probability for each of the class labels.
  • supports fine-tuning pretrained models for specific image classification tasks.

Object Detection – MXNet

  • detects and classifies objects in images using a single deep neural network.
  • is a supervised learning algorithm that takes images as input and identifies all instances of objects within the image scene.

Object Detection – TensorFlow

  • is a supervised learning algorithm that supports transfer learning with many pretrained models from the TensorFlow Model Garden.
  • takes an image as input and predicts bounding boxes and object labels.
  • uses deep learning networks such as MobileNet, ResNet, Inception, and EfficientNet for object detection.

Semantic Segmentation

  • provides a fine-grained, pixel-level approach to developing computer vision applications.
  • tags every pixel in an image with a class label from a predefined set of classes and is critical to an increasing number of CV applications, such as self-driving vehicles, medical imaging diagnostics, and robot sensing.
  • also provides information about the shapes of the objects contained in the image. The segmentation output is represented as a grayscale image, called a segmentation mask.

SageMaker JumpStart – Pre-trained Models

  • SageMaker JumpStart provides pre-trained foundation models, pre-built solution templates, and example notebooks for popular ML problem types.
  • Foundation models include large language models (LLMs) such as LLaMA, Falcon, BLOOM, FLAN-T5, Mistral, and GPT-J for generative AI tasks.
  • Supports 15+ problem types including:
    • Text Generation, Text Summarization, Question Answering
    • Text Embedding, Named Entity Recognition
    • Image Classification, Object Detection, Instance Segmentation
    • Tabular Classification, Tabular Regression
    • Machine Translation, Sentence Pair Classification
  • Models can be fine-tuned on custom datasets and deployed directly from SageMaker Studio.

SageMaker Autopilot (AutoML)

  • SageMaker Autopilot automatically explores different solutions to find the best model for your data.
  • Analyzes data, selects algorithms, preprocesses data, trains models, and performs hyperparameter optimization.
  • Supports classification, regression, and time-series forecasting problem types.
  • Available as a no-code/low-code option through SageMaker Canvas for business analysts.

AWS Certification Exam Practice Questions

  • Questions are collected from Internet and the answers are marked as per my knowledge and understanding (which might differ with yours).
  • AWS services are updated everyday and both the answers and questions might be outdated soon, so research accordingly.
  • AWS exam questions are not updated to keep up the pace with AWS updates, so even if the underlying feature has changed the question might not be updated
  • Open to further feedback, discussion and correction.
  1. An Analytics team is leading an organization and wants to use anomaly detection to identify potential risks. What Amazon SageMaker AI machine learning algorithms are best suited for identifying anomalies?
    1. Semantic segmentation
    2. K-nearest neighbors
    3. Latent Dirichlet Allocation (LDA)
    4. Random Cut Forest (RCF)
  2. A ML specialist team works for a marketing consulting firm wants to
    apply different marketing strategies per segment of their customer base. Online retailer purchase history from the last 5 years is available, it has been decided to segment the customers based on their purchase history. Which type of machine learning algorithm would give you segmentation based on purchase history in the most expeditious manner?

    1. K-Nearest Neighbors (KNN)
    2. K-Means
    3. Semantic Segmentation
    4. Neural Topic Model (NTM)
  3. A ML specialist team is looking to improve the quality of searches for their library of documents that are uploaded in PDF, Rich Text Format, or ASCII text. It is looking to use machine learning to automate the identification of key topics for each of the documents. What machine learning resources are best suited for this problem? (Select TWO)
    1. BlazingText algorithm
    2. Latent Dirichlet Allocation (LDA) algorithm
    3. Topic Finder (TF) algorithm
    4. Neural Topic Model (NTM) algorithm
  4. A manufacturing company has a large set of labeled historical sales data. The company would like to predict how many units of a particular part should be produced each quarter. Which machine learning approach should be used to solve this problem?
    1. BlazingText algorithm
    2. Random Cut Forest (RCF)
    3. Principal component analysis (PCA)
    4. Linear regression
  5. An agency collects census information with responses for approximately 500 questions from each citizen. Which algorithm would help reduce the number of features?
    1. Factorization machines (FM) algorithm
    2. Latent Dirichlet Allocation (LDA) algorithm
    3. Principal component analysis (PCA) algorithm
    4. Random Cut Forest (RCF) algorithm
  6. A store wants to understand some characteristics of visitors to the store. The store has security video recordings from the past several years. The store wants to group visitors by hair style and hair color. Which solution will meet these requirements with the LEAST amount of effort?
    1. Object detection algorithm
    2. Latent Dirichlet Allocation (LDA) algorithm
    3. Random Cut Forest (RCF) algorithm
    4. Semantic segmentation algorithm
  7. A data scientist needs to build a model that can automatically classify product reviews as positive or negative. The dataset contains millions of labeled reviews. Which SageMaker AI built-in algorithm is MOST suitable for this text classification task with transfer learning?
    1. Sequence-to-Sequence (seq2seq)
    2. BlazingText in Word2Vec mode
    3. Text Classification – TensorFlow
    4. Neural Topic Model (NTM)
  8. A company wants to predict customer churn using a tabular dataset with both numerical and categorical features. The team wants an AutoML approach that automatically ensembles multiple models. Which SageMaker AI built-in algorithm should they use?
    1. XGBoost
    2. Linear Learner
    3. AutoGluon-Tabular
    4. Factorization Machines
  9. A team needs to detect objects in images and draw bounding boxes around them. They want to leverage pretrained models and use transfer learning. Which SageMaker AI algorithm should they choose?
    1. Image Classification – MXNet
    2. Semantic Segmentation
    3. Image Classification – TensorFlow
    4. Object Detection – TensorFlow
  10. A company has tabular data with many categorical features and wants a gradient-boosted trees algorithm that handles categorical features natively without manual encoding. Which algorithm is BEST suited?
    1. XGBoost
    2. LightGBM
    3. CatBoost
    4. Linear Learner

References

AWS AI & Machine Learning Services Cheat Sheet

AWS Machine Learning Services

AWS Machine Learning Services

AWS Machine Learning Services

Amazon Bedrock

  • is a fully managed service providing access to high-performing foundation models (FMs) from leading AI companies (GA September 2023).
  • offers foundation models from AI21 Labs, Amazon (Nova), Anthropic, Cohere, Meta, Mistral AI, OpenAI, and Stability AI through a unified API.
  • enables building and scaling generative AI applications without managing infrastructure.
  • supports model customization including fine-tuning and reinforcement fine-tuning (RFT) with your own data while maintaining data privacy and security.
  • provides serverless experience with pay-per-use pricing.
  • includes capabilities for text generation, chat, image generation, video generation, and embeddings.
  • supports Retrieval Augmented Generation (RAG) with Knowledge Bases and the new Managed Knowledge Base (2026) that abstracts storage, retrieval, embeddings, and re-ranking into a single managed primitive.
  • provides Bedrock Agents for multi-step task automation.
  • includes Amazon Bedrock Guardrails for configurable safety controls including content filtering, topic classification, sensitive information protection, and hallucination detection across both text and images with up to 88% harmful content blocking accuracy.
  • supports OpenAI-compatible API endpoints (2026) including Responses API and Chat Completions API for simplified migration and integration.
  • ensures data is not used to train base models and remains within your AWS environment.
  • includes Amazon Bedrock AgentCore (2026) — a platform to build, connect, deploy, and optimize AI agents with managed harness, observability, guardrails integration, and continuous optimization capabilities.

Amazon Nova Foundation Models

  • is Amazon’s family of proprietary foundation models available exclusively through Amazon Bedrock (launched December 2024 at re:Invent).
  • includes Amazon Nova Micro — a text-only model optimized for speed and lowest cost, ideal for summarization, translation, and classification (128K context).
  • includes Amazon Nova Lite — a low-cost multimodal model processing text, images, and video for tasks like document analysis and visual Q&A.
  • includes Amazon Nova Pro — a balanced multimodal model offering strong accuracy, speed, and cost for a wide range of tasks.
  • includes Amazon Nova Premier — the most capable model for complex reasoning, agentic workflows, and model distillation.
  • includes Amazon Nova Canvas — an image generation model.
  • includes Amazon Nova Reel — a video generation model.
  • includes Amazon Nova Sonic — a speech-to-speech model.
  • Amazon Nova 2 models (Nova 2 Lite and Nova 2 Pro) announced in December 2025 with improved capabilities.
  • all Nova models are among the fastest and most cost-effective in their respective intelligence classes, optimized for RAG and agentic applications.

Amazon Q Developer (formerly CodeWhisperer) → Transitioning to Kiro

  • is a generative AI-powered coding assistant for software developers (rebranded from CodeWhisperer in April 2024).
  • provides real-time code suggestions, completions, and generation based on comments and existing code.
  • supports multiple programming languages including Python, Java, JavaScript, TypeScript, C#, Go, Rust, PHP, Ruby, Kotlin, C, C++, Shell, SQL, and more.
  • integrates with popular IDEs including VS Code, IntelliJ IDEA, PyCharm, WebStorm, and AWS Cloud9.
  • performs security scanning to identify and suggest fixes for vulnerabilities.
  • provides code explanations and documentation generation.
  • assists with debugging, upgrading applications, and troubleshooting.
  • tracks open-source code references and license information.
  • offers free tier for individual developers and paid tier for professional use.
⚠️ Transition Notice (May 2026): Amazon Q Developer IDE plugins and paid subscriptions will reach end-of-support on April 30, 2027. New signups blocked as of May 15, 2026. The successor is Kiro — AWS’s next-generation agentic development environment (IDE and CLI) built on Code OSS and powered by Amazon Bedrock. Kiro includes agentic coding, inline chat, terminal integration, and MCP support. Users have a 12-month transition window.

Amazon Quick (formerly Amazon Q Business)

  • is a generative AI-powered assistant for enterprise use, rebranded from Amazon Q Business to Amazon Quick in April 2026.
  • is described as “the next evolution of Amazon Q Business” — an AI assistant for work that connects to apps, learns workflows, and takes action.
  • answers questions, provides summaries, generates content, and completes tasks based on enterprise data.
  • connects to 40+ enterprise data sources including S3, SharePoint, Salesforce, ServiceNow, Jira, and more.
  • respects existing access controls and permissions from connected data sources.
  • provides conversational interface for employees to access company information.
  • available as a desktop app (Windows and Mac) with Microsoft 365 extensions (Outlook, Word, Teams).
  • offers Free and Plus pricing plans.
  • supports autonomous agents for handling recurring tasks continuously.
  • supports Amazon Q Apps for creating AI-powered applications from conversations.
  • ensures enterprise data privacy and security with data isolation.

Amazon SageMaker AI (formerly Amazon SageMaker)

  • Naming Update (December 2024): On December 3, 2024, Amazon SageMaker was renamed to Amazon SageMaker AI. The “SageMaker” brand now refers to the next-generation unified platform for data, analytics, and AI.
  • Build, train, and deploy machine learning models at scale.
  • fully-managed service that enables data scientists and developers to quickly and easily build, train & deploy machine learning models.
  • enables developers and scientists to build machine learning models for use in intelligent, predictive apps.
  • is designed for high availability with no maintenance windows or scheduled downtimes.
  • allows users to select the number and type of instance used for the hosted notebook, training & model hosting.
  • can be deployed as endpoint interfaces and batch.
  • supports Canary deployment using ProductionVariant and deploying multiple variants of a model to the same SageMaker HTTPS endpoint.
  • supports Jupyter notebooks.
  • Users can persist their notebook files on the attached ML storage volume.
  • Users can modify the notebook instance and select a larger profile through the SageMaker console, after saving their files and data on the attached ML storage volume.
  • includes built-in algorithms for linear regression, logistic regression, k-means clustering, principal component analysis, factorization machines, neural topic modeling, latent dirichlet allocation, gradient boosted trees, seq2seq, time series forecasting, word2vec & image classification
  • algorithms work best when using the optimized protobuf recordIO format for the training data, which allows Pipe mode that streams data directly from S3 and helps faster start times and reduce space requirements
  • provides built-in algorithms, pre-built container images, or extend a pre-built container image and even build your custom container image.
  • supports users custom training algorithms provided through a Docker image adhering to the documented specification.
  • also provides optimized MXNet, Tensorflow, Chainer & PyTorch containers
  • ensures that ML model artifacts and other system artifacts are encrypted in transit and at rest.
  • requests to the API and console are made over a secure (SSL) connection.
  • stores code in ML storage volumes, secured by security groups and optionally encrypted at rest.
  • SageMaker Neo is a capability that enables machine learning models to train once and run anywhere in the cloud and at the edge.

Amazon SageMaker Unified Studio

  • is a unified web-based development environment announced at re:Invent 2024 and GA in March 2025.
  • is part of the next generation of Amazon SageMaker — the center for all data, analytics, and AI.
  • breaks down silos in data and tools, giving data engineers, data scientists, data analysts, and ML developers a single development experience.
  • brings together functionality from Amazon EMR, AWS Glue, Amazon Redshift, Amazon Bedrock, and SageMaker AI Studio.
  • enables discovering data and AI assets from across the organization, then collaborating in projects to securely build and share analytics and AI artifacts.
  • includes SageMaker Lakehouse — unifies data across data lakes, data warehouses, operational databases, and enterprise applications with Apache Iceberg compatibility.
  • includes SageMaker Data and AI Governance for integrated access controls and data governance.
  • offers choice of IDEs including JupyterLab, Code Editor (based on VS Code OSS), and RStudio.
  • Note: The previous “SageMaker Studio” experience was renamed to “SageMaker Studio Classic” (November 2023) and is now part of SageMaker AI.

Amazon SageMaker Canvas

  • is a no-code machine learning service for business analysts (launched November 2021).
  • enables building accurate ML models without writing code or requiring ML expertise.
  • provides visual, point-and-click interface for data preparation and model building.
  • supports tabular, image, and text data for predictions.
  • connects to 50+ data sources including S3, Redshift, Snowflake, and SaaS applications.
  • offers ready-to-use ML models and custom model building capabilities.
  • includes generative AI capabilities (October 2023) for text generation, summarization, and content creation.
  • provides automated feature engineering, algorithm selection, and hyperparameter tuning.
  • enables one-click model deployment and batch predictions.
  • supports collaboration between business analysts and data scientists.
  • is the recommended migration path for Amazon Forecast customers for time-series forecasting.

Amazon SageMaker Clarify

  • provides bias detection, model explainability, and foundation model evaluation capabilities.
  • detects pre-training bias (Class Imbalance, DPL, KL Divergence) and post-training bias (Disparate Impact, Demographic Parity Difference).
  • provides SHAP-based feature importance for individual predictions and partial dependence plots.
  • evaluates foundation models for accuracy, robustness, toxicity, and stereotyping.
  • integrates with Model Monitor for continuous bias drift detection in production.
  • identifies biases in training data and ML models across different groups (age, gender, income, etc.).
  • detects potential bias during data preparation, after model training, and in deployed models.
  • generates detailed reports quantifying different types of possible bias.
  • provides feature importance graphs to explain model predictions.
  • integrates with SageMaker Data Wrangler for bias detection during data preparation.
  • supports continuous monitoring of deployed models for bias drift.
  • helps meet regulatory requirements and ethical AI standards.
  • produces reports for internal presentations and compliance documentation.

Amazon SageMaker HyperPod

  • is purpose-built infrastructure for distributed training at scale (GA November 2023).
  • reduces time to train foundation models by up to 40% with optimized infrastructure.
  • supports GPU-based and AWS Trainium-based instances for cost-effective training.
  • provides automated cluster health monitoring and node replacement.
  • enables training for weeks or months with automated resiliency.
  • automatically saves checkpoints and resumes training from last checkpoint on failure.
  • efficiently distributes models and data across thousands of compute resources.
  • includes preconfigured distributed training libraries for popular frameworks.
  • provides recipes for accelerating foundation model training and fine-tuning.
  • offers flexible training plans to meet timelines and budgets.

Amazon Textract

  • Textract provides OCR and helps add document text detection and analysis to the applications.
  • includes simple, easy-to-use API operations that can analyze image files and PDF files.
  • extracts text, handwriting, tables, and forms from scanned documents.
  • supports Queries for extracting specific information from documents using natural language questions.
  • provides Lending API for automated mortgage document processing.

Amazon Comprehend

  • Comprehend is a managed natural language processing (NLP) service to find insights and relationships in text.
  • identifies the language of the text; extracts key phrases, places, people, brands, or events; understands how positive or negative the text is; analyzes text using tokenization and parts of speech; and automatically organizes a collection of text files by topic.
  • can analyze a collection of documents and other text files (such as social media posts) and automatically organize them by relevant terms or topics.
  • supports custom entity recognition and custom classification for domain-specific NLP.
  • provides Comprehend Medical for extracting medical information such as conditions, medications, dosages, and their relationships.
⚠️ Note (April 2026): Amazon Comprehend topic modeling, event detection, and prompt safety classification features are no longer available to new customers as of April 30, 2026. Existing customers can continue to use these features.

Amazon Lex

  • is a service for building conversational interfaces using voice and text.
  • provides the advanced deep learning functionalities of automatic speech recognition (ASR) for converting speech to text, and natural language understanding (NLU) to recognize the intent of the text, to enable building applications with highly engaging user experiences and lifelike conversational interactions.
  • common use cases of Lex include: Application/Transactional bot, Informational bot, Enterprise Productivity bot, and Device Control bot.
  • leverages Lambda for Intent fulfillment, Cognito for user authentication & Polly for text-to-speech.
  • scales to customers’ needs and does not impose bandwidth constraints.
  • is a completely managed service so users don’t have to manage the scaling of resources or maintenance of code.
  • uses deep learning to improve over time.
  • supports Generative AI features powered by Amazon Bedrock LLMs including:
    • AMAZON.QnAIntent — handles FAQ-style questions using knowledge bases without configuring individual intents.
    • Assisted NLU (2025) — uses LLMs to improve intent classification and slot resolution accuracy while staying within configured intents.
    • Descriptive Bot Builder — generates bot configurations from natural language descriptions.

Amazon Polly

  • text into speech
  • uses advanced deep-learning technologies to synthesize speech that sounds like a human voice.
  • provides dozens of lifelike voices across 60+ languages.
  • supports multiple voice engines:
    • Standard — concatenative synthesis voices.
    • Neural — higher-quality neural TTS voices.
    • Long-Form — optimized for long content like articles and books.
    • Generative (2024-2025) — the most natural-sounding voices using generative AI, with new voices continually added.
  • supports Lexicons to customize pronunciation of specific words & phrases.
  • supports Speech Synthesis Markup Language (SSML) tags like prosody so users can adjust the speech rate, pitch, pauses, or volume.
  • supports bidirectional streaming API for real-time applications.

Amazon Rekognition

  • analyzes image and video
  • identify objects, people, text, scenes, and activities in images and videos, as well as detect any inappropriate content.
  • provides highly accurate facial analysis and facial search capabilities that can be used to detect, analyze, and compare faces for a wide variety of user verification, people counting, and public safety use cases.
  • helps identify potentially unsafe or inappropriate content across both image and video assets and provides detailed labels that help accurately control what you want to allow based on your needs.
  • provides Rekognition Custom Labels (launched December 2019) – an AutoML feature to build custom ML models for detecting specific objects and scenes unique to business needs.
  • Custom Labels requires as few as 10 sample images per label to train custom models.
  • Custom Labels automatically selects optimal ML algorithms and trains models without requiring ML expertise.
  • enables identifying business-specific items like machine parts, product defects, or brand logos.

Amazon Forecast

⚠️ SERVICE CLOSED TO NEW CUSTOMERS (July 29, 2024)
Amazon Forecast is no longer available to new customers. Existing customers can continue using the service. Migration: Use Amazon SageMaker Canvas for time-series forecasting with a no-code interface.
  • Amazon Forecast is a fully managed time-series forecasting service that uses statistical and machine learning algorithms to deliver highly accurate time-series forecasts and is built for business metrics analysis.
  • automatically tracks the accuracy of the model over time as new data is imported.
  • provides six built-in algorithms which include ARIMA, Prophet, NPTS, ETS, CNN-QR, and DeepAR+.
  • integrates with AutoML to choose the optimal model for the datasets.

Amazon SageMaker Ground Truth

  • helps build highly accurate training datasets for machine learning quickly.
  • offers easy access to labelers through Amazon Mechanical Turk and provides them with built-in workflows and interfaces for common labeling tasks.
  • allows using your own labelers or use vendors recommended by Amazon through AWS Marketplace.
  • helps lower labeling costs by up to 70% using automatic labeling, which works by training Ground Truth from data labeled by humans so that the service learns to label data independently.
  • provides annotation consolidation to help improve the accuracy of the data object’s labels.

Amazon Translate

  • provides natural and fluent language translation
  • a neural machine translation service that delivers fast, high-quality, and affordable language translation.
  • Neural machine translation is a form of language translation automation that uses deep learning models to deliver more accurate and natural-sounding translation than traditional statistical and rule-based translation algorithms.
  • allows content localization – such as websites and applications – for international users, and to easily translate large volumes of text efficiently.

Amazon Transcribe

  • provides speech-to-text capability
  • uses a deep learning process called automatic speech recognition (ASR) to convert speech to text quickly and accurately.
  • can be used to transcribe customer service calls, automate closed captioning and subtitling, and generate metadata for media assets to create a fully searchable archive.
  • adds punctuation and formatting so that the output closely matches the quality of manual transcription at a fraction of the time and expense.
  • process audio in batch or near real-time.
  • supports automatic language identification.
  • supports custom vocabulary to generate more accurate transcriptions for domain-specific words and phrases like product names, technical terminology, or names of individuals.
  • supports specifying a list of words to remove from transcripts.
  • provides Transcribe Call Analytics (launched August 2021) for extracting insights from customer conversations.
  • Call Analytics generates turn-by-turn transcripts with speaker identification and sentiment analysis.
  • supports real-time Call Analytics (November 2022) for live conversation insights and agent assistance.
  • provides Transcribe Medical for healthcare and medical transcription with HIPAA eligibility.

Amazon Kendra

  • is an intelligent search service that uses NLP and advanced ML algorithms to return specific answers to search questions from your data.
  • uses its semantic and contextual understanding capabilities to decide whether a document is relevant to a search query.
  • returns specific answers to questions, giving users an experience that’s close to interacting with a human expert.
  • provides a unified search experience by connecting multiple data repositories to an index and ingesting and crawling documents.
  • can use the document metadata to create a feature-rich and customized search experience for the users, helping them efficiently find the right answers to their queries.
  • can be used as a retriever for Amazon Quick (formerly Amazon Q Business) to power enterprise search with generative AI.

Augmented AI (Amazon A2I)

  • Augmented AI (Amazon A2I) is an ML service that makes it easy to build the workflows required for human review.
  • brings human review to all developers, removing the undifferentiated heavy lifting associated with building human review systems or managing large numbers of human reviewers, whether it runs on AWS or not.
  • integrates with Amazon Textract for document processing and Amazon Rekognition for content moderation.
  • supports private review teams, Amazon Mechanical Turk, and AWS Marketplace vendors.

Amazon Personalize

  • Personalize is a fully managed machine learning service that uses data to generate item recommendations.
  • can also generate user segments based on the users’ affinity for certain items or item metadata.
  • generates recommendations primarily based on item interaction data that comes from the users interacting with items in the catalog.
  • includes API operations for real-time personalization, and batch operations for bulk recommendations and user segments.

Amazon Panorama

⚠️ SERVICE END OF SUPPORT — May 31, 2026
AWS will end support for AWS Panorama on May 31, 2026. After this date, you will no longer be able to access the AWS Panorama console or resources, and Panorama devices will become non-functional. Consider migrating to Amazon SageMaker AI with edge deployment or third-party edge CV solutions.
  • brings computer vision to the on-premises camera network.
  • AWS Panorama Appliance or another compatible device can be installed in the data center and registered with AWS Panorama to deploy computer vision applications from the cloud.
  • AWS Panorama Appliance
    • is a compact edge appliance that uses a powerful system-on-module (SOM) that is optimized for ML workloads.
    • can run multiple computer vision models against multiple video streams in parallel and output the results in real-time.
    • is designed for use in commercial and industrial settings and is rated for dust and liquid protection.
  • works with the existing real-time streaming protocol (RTSP) network cameras.

Amazon Fraud Detector

  • Fraud Detector is a fully managed service to identify potentially fraudulent online activities such as online payment fraud and fake account creation.
  • takes care of all the heavy lifting such as data validation and enrichment, feature engineering, algorithm selection, hyperparameter tuning, and model deployment.

AWS IoT Greengrass ML Inference

  • IoT Greengrass helps perform machine learning inference locally on devices, using models that are created, trained, and optimized in the cloud.
  • provides flexibility to use machine learning models trained in SageMaker or to bring your pre-trained model stored in S3.
  • helps get inference results with very low latency to ensure the IoT applications can respond quickly to local events.

Amazon Elastic Inference

⚠️ SERVICE DEPRECATED (April 2023)
Amazon Elastic Inference is no longer available to new customers. Alternatives: Use AWS Inferentia instances (Inf1/Inf2) for better price-performance on inference workloads, or use SageMaker AI real-time inference endpoints with appropriate instance types.
  • helped attach low-cost GPU-powered acceleration to EC2 and SageMaker instances or ECS tasks to reduce the cost of running deep learning inference by up to 75%.
  • supported TensorFlow, Apache MXNet, and ONNX models.

AWS Certification Exam Practice Questions

  • Questions are collected from Internet and the answers are marked as per my knowledge and understanding (which might differ with yours).
  • AWS services are updated everyday and both the answers and questions might be outdated soon, so research accordingly.
  • AWS exam questions are not updated to keep up the pace with AWS updates, so even if the underlying feature has changed the question might not be updated
  • Open to further feedback, discussion and correction.
  1. A company has built a deep learning model and now wants to deploy it using the SageMaker Hosting Services. For inference, they want a cost-effective option that guarantees low latency but still comes at a fraction of the cost of using a GPU instance for your endpoint. As a machine learning Specialist, what feature should be used?
    1. Inference Pipeline
    2. Elastic Inference [Note: Elastic Inference is deprecated. Current recommendation is AWS Inferentia (Inf2) instances for cost-effective inference.]
    3. SageMaker Ground Truth
    4. SageMaker Neo
  2. A machine learning specialist works for an online retail company that sells health products. The company allows users to enter reviews of the products they buy from the website. The company wants to make sure the reviews do not contain any offensive or unsafe content, such as obscenities or threatening language. Which Amazon SageMaker algorithm or service will allow scanning user’s review text in the simplest way?
    1. BlazingText
    2. Transcribe
    3. Semantic Segmentation
    4. Comprehend
  3. A company develops a tool whose coverage includes blogs, news sites, forums, videos, reviews, images, and social networks such as Twitter and Facebook. Users can search data by using Text and Image Search, and use charting, categorization, sentiment analysis, and other features to provide further information and analysis. They want to provide Image and text analysis capabilities to the applications which include identifying objects, people, text, scenes, and activities, and also provide highly accurate facial analysis and facial recognition. What service can provide this capability?
    1. Amazon Comprehend
    2. Amazon Rekognition
    3. Amazon Polly
    4. Amazon SageMaker
  4. A company wants to build generative AI applications using foundation models without managing infrastructure. Which service should they use?
    1. Amazon SageMaker
    2. Amazon Comprehend
    3. Amazon Bedrock
    4. Amazon Lex
  5. A development team wants an AI assistant that provides real-time code suggestions and security scanning in their IDE. Which service should they use?
    1. Amazon CodeGuru
    2. Amazon Q Developer (transitioning to Kiro)
    3. AWS Cloud9
    4. Amazon SageMaker
  6. A business analyst with no ML experience wants to build accurate ML models using a visual interface. Which service should they use?
    1. Amazon SageMaker Studio
    2. Amazon SageMaker Canvas
    3. Amazon Forecast
    4. Amazon Personalize
  7. A company needs to detect bias in their ML models and explain predictions for regulatory compliance. Which service should they use?
    1. Amazon SageMaker Ground Truth
    2. Amazon Inspector
    3. Amazon SageMaker Clarify
    4. AWS Audit Manager
  8. A company wants to train large foundation models for weeks with automated resiliency and checkpoint management. Which service should they use?
    1. Amazon SageMaker Training Jobs
    2. Amazon SageMaker HyperPod
    3. AWS Batch
    4. Amazon EC2 with GPU instances
  9. A contact center wants real-time insights from customer calls including sentiment analysis and agent assistance. Which service should they use?
    1. Amazon Transcribe
    2. Amazon Transcribe Call Analytics
    3. Amazon Comprehend
    4. Amazon Connect
  10. A company wants to build custom image recognition models to identify specific machine parts with minimal training data. Which service should they use?
    1. Amazon Rekognition (standard)
    2. Amazon Rekognition Custom Labels
    3. Amazon SageMaker
    4. Amazon Textract
  11. A company wants to deploy AI agents that can perform multi-step workflows, access enterprise tools, and maintain state across conversations in production. Which service should they use?
    1. Amazon Lex
    2. Amazon SageMaker AI
    3. Amazon Bedrock AgentCore
    4. AWS Step Functions
  12. A company needs Amazon’s own foundation models that offer industry-leading price-performance for text, image, and video generation tasks. Which model family should they use?
    1. Amazon Titan
    2. Amazon Nova
    3. Amazon Comprehend
    4. Amazon SageMaker JumpStart
  13. An enterprise wants a unified platform for data engineering, analytics, ML development, and generative AI that breaks down tool silos. Which service should they use?
    1. Amazon SageMaker AI
    2. Amazon EMR
    3. Amazon SageMaker Unified Studio
    4. AWS Glue
  14. A company wants to implement safety guardrails for their generative AI application to filter harmful content, block prompt injections, and protect sensitive information. Which service should they use?
    1. AWS WAF
    2. Amazon Macie
    3. Amazon Bedrock Guardrails
    4. AWS Shield

References

Amazon SageMaker AI – End-to-End ML Platform

SageMaker Overview

Amazon SageMaker AI

📝 Naming Update (December 2024): On December 3, 2024, Amazon SageMaker was renamed to Amazon SageMaker AI. The “SageMaker” brand now refers to the next-generation unified platform for data, analytics, and AI. SageMaker AI remains available as a standalone service for building, training, and deploying ML models at scale, and is also integrated within the broader next-generation SageMaker platform.

Amazon SageMaker AI is a fully managed machine learning service that enables data scientists, ML engineers, and developers to build, train, and deploy machine learning models at scale. It provides a complete end-to-end ML workflow — from data preparation and model training to deployment and monitoring — while offering the flexibility to use preferred tools, frameworks, and infrastructure.

  • SageMaker AI removes the heavy lifting from each step of the machine learning process, making it easier to develop production-quality models.
  • It is designed for high availability with no maintenance windows or scheduled downtimes, with service stack replication across three facilities in each AWS region.
  • SageMaker AI supports the full ML lifecycle: data labeling, data preparation, feature engineering, training, tuning, deployment, monitoring, and MLOps automation.
  • It integrates with popular ML frameworks including PyTorch, TensorFlow, Hugging Face, scikit-learn, and XGBoost.
  • SageMaker AI is part of the next-generation Amazon SageMaker platform, which unifies data, analytics, and AI in a single governed environment.

SageMaker AI Overview - A diagram showing the complete machine learning workflow from data preparation to model deployment

Next-Generation Amazon SageMaker Platform (Dec 2024)

At AWS re:Invent 2024, AWS unveiled the next generation of Amazon SageMaker — a unified platform for data, analytics, and AI. This represents a major evolution beyond the original ML-focused service.

Platform Components

  • Amazon SageMaker Unified Studio (GA March 2025): A single IDE for data engineering, SQL analytics, ML model development, and generative AI application development. Brings together tools previously spread across EMR, Glue, Redshift, Athena, SageMaker AI, and Bedrock.
  • Amazon SageMaker Lakehouse: An open data architecture built on Apache Iceberg that unifies data across S3 data lakes (including S3 Tables), Redshift data warehouses, and federated sources.
  • Amazon SageMaker Catalog: Governance layer enabling secure discovery, access control, metadata management, lineage tracking, and collaboration for data and AI assets.
  • Amazon SageMaker AI: The ML service (formerly “Amazon SageMaker”) for building, training, and deploying ML models. Includes HyperPod, JumpStart, MLOps, and all inference/training capabilities.

📖 Deep Dive Guides: Bedrock vs SageMaker | RAG Architecture | Prompt Engineering | Responsible AI | AI Services Decision Guide

Deprecated and Discontinued Features

⚠️ Deprecated Services and Features

Feature Status EOL Date Replacement
SageMaker Edge Manager End of Life April 26, 2024 SageMaker Neo + IoT Greengrass
SageMaker Studio Classic End of Maintenance December 31, 2024 SageMaker Studio (new experience)
Amazon Elastic Inference Discontinued April 15, 2023 AWS Inferentia2 (Inf2 instances)
SageMaker Training Compiler No new releases N/A Neuron SDK / framework-native optimizations
Data Wrangler (standalone) Merged into Canvas N/A SageMaker Canvas with Data Wrangler
JupyterLab 1 & 3 (Notebook Instances) End of Support June 30, 2025 JupyterLab 4

SageMaker Studio

SageMaker Studio is the fully integrated development environment (IDE) for machine learning on AWS, providing a web-based visual interface for the entire ML workflow.

  • Provides a unified interface for all ML development tasks — notebooks, code editors, terminals, experiment tracking, and model deployment.
  • Supports JupyterLab notebooks with flexible compute (switch instance types without restarting).
  • Integrates with Amazon Q Developer for AI-assisted code generation and optimization suggestions.
  • Built-in MLflow integration for experiment tracking, model registry, and generative AI observability (serverless MLflow, no infrastructure management).
  • Supports collaborative development — team members share notebooks, experiments, and models within a domain.
  • Integrates MLOps capabilities for CI/CD pipelines and automated workflows.
  • Enables cross-account collaboration while maintaining governance via IAM and SageMaker Role Manager.
Note: SageMaker Studio Classic reached end of maintenance on December 31, 2024. No new Studio Classic applications can be created. Existing workloads should be migrated to the new Studio experience.

SageMaker Unified Studio (Next-Gen Platform)

SageMaker Unified Studio is the development environment for the next-generation SageMaker platform (GA March 2025):

  • Single environment for data engineering, SQL analytics, ML development, and generative AI application building.
  • Serverless notebooks combining SQL queries, Python code, Apache Spark processing, and natural language prompts.
  • Backed by Amazon Athena for Apache Spark, scaling from interactive exploration to petabyte-scale jobs.
  • Integrated with Amazon Bedrock IDE for generative AI application development with guardrails.
  • Project-based collaboration with fine-grained access control via SageMaker Catalog.

SageMaker Canvas

SageMaker Canvas is a no-code/low-code ML service that enables business analysts, citizen data scientists, and non-technical users to build, train, and deploy ML models without writing code.

  • Visual Point-and-Click Interface: Import data, build models, and generate predictions through an intuitive UI.
  • Natural Language Interface: Use natural language to describe data preparation tasks — Canvas translates instructions into transformations automatically.
  • Data Wrangler Integration: Canvas now includes full SageMaker Data Wrangler capabilities with 300+ built-in transforms and access to 50+ data sources (S3, Redshift, Snowflake, SaaS applications).
  • Ready-Made Models: Pre-trained models available for common tasks without needing to build a custom model:
    • Sentiment analysis and text classification
    • Object detection and image classification
    • Document analysis (entity extraction, key-value pairs)
    • Foundation models for text generation (via Bedrock and JumpStart integration)
  • Custom Model Building: Supports tabular prediction (numeric/categorical), time series forecasting, computer vision, and NLP use cases.
  • LLM Fine-Tuning: No-code fine-tuning of foundation models from SageMaker JumpStart and Amazon Bedrock with your own data.
  • Collaboration: Share models and insights with data scientists in SageMaker Studio; models can be deployed to production endpoints.
  • Petabyte-Scale Processing: Data transformation at petabyte scale leveraging distributed compute under the hood.

Model Training

SageMaker AI provides flexible, scalable options for training ML models — from using optimized built-in algorithms to bringing your own custom code and containers.

Built-in Algorithms

SageMaker AI provides numerous built-in algorithms optimized for distributed training at scale:

Tabular Data:

  • XGBoost — Gradient-boosted trees for classification and regression (versions 1.0–3.0)
  • Linear Learner — Linear models for classification and regression
  • CatBoost — Gradient boosting with native categorical feature support
  • LightGBM — Fast gradient boosting framework
  • AutoGluon-Tabular — AutoML for tabular data
  • TabTransformer — Transformer-based tabular model
  • K-Nearest Neighbors (k-NN) — Instance-based classification/regression
  • Factorization Machines — For high-dimensional sparse data

Time Series:

  • DeepAR Forecasting — Autoregressive RNN for time series

Natural Language Processing:

  • BlazingText — Word2Vec and text classification
  • Sequence-to-Sequence — Translation, summarization
  • Object2Vec — Embeddings for paired data

Computer Vision:

  • Image Classification (MXNet) — ResNet-based image classification
  • Object Detection — Identify objects in images
  • Semantic Segmentation — Pixel-level labeling

Unsupervised Learning:

  • K-Means — Clustering
  • Principal Component Analysis (PCA) — Dimensionality reduction
  • Random Cut Forest — Anomaly detection
  • IP Insights — Learn usage patterns for IP addresses
  • Latent Dirichlet Allocation (LDA) — Topic modeling
  • Neural Topic Model (NTM) — Topic modeling with neural networks

For a detailed list with input/output formats, see SageMaker Built-in Algorithms Summary.

Bring Your Own (BYO) Training

  • Script Mode: Use pre-built framework containers (PyTorch, TensorFlow, Hugging Face, scikit-learn, MXNet) and supply your training script.
  • BYO Container: Package your own Docker container with any framework or library and register it with Amazon ECR.
  • BYO Algorithm: Create custom algorithms that integrate with SageMaker’s managed training infrastructure.

Training Data Input Modes

  • File mode: Downloads all data from S3 to the training instance before starting. Best for datasets that fit on disk.
  • Fast File mode: Combines the ease of File mode with streaming performance — data is fetched on demand from S3 with POSIX-compatible access.
  • Pipe mode: Streams data directly from S3 in real time, reducing storage requirements and startup time.
  • Storage options: Amazon S3, Amazon EFS, Amazon FSx for Lustre (recommended for large-scale distributed training).

Distributed Training

SageMaker AI provides built-in distributed training libraries for scaling across multiple GPUs and instances:

  • Data Parallelism: Splits the dataset across multiple GPUs/instances; each processes a subset and synchronizes gradients. Supports AllReduce and parameter server strategies.
  • Model Parallelism: Splits large models across multiple GPUs when a model doesn’t fit in a single GPU’s memory. Supports tensor parallelism and pipeline parallelism.
  • Sharded Data Parallelism: Combines data parallelism with model state sharding (similar to DeepSpeed ZeRO/PyTorch FSDP) to train large models efficiently.
  • Native support for PyTorch DDP, PyTorch FSDP, Horovod, and framework-native distribution strategies.

Managed Spot Training

  • Uses Amazon EC2 Spot Instances to reduce training costs by up to 90% compared to On-Demand instances.
  • SageMaker handles Spot interruptions automatically — checkpoints are saved to S3 and training resumes from the last checkpoint.
  • Specify MaxWaitTimeInSeconds to control the maximum time to wait for Spot capacity.
  • Best suited for fault-tolerant training jobs (not recommended for time-critical training).

Warm Pools

  • Keep training instances in a warm (pre-provisioned) state between consecutive training jobs to eliminate cold start delays.
  • Reduces startup time from minutes to seconds for iterative training workflows (hyperparameter tuning, experiment iterations).
  • Specify KeepAlivePeriodInSeconds to control how long instances remain warm after a job completes.
  • Billed at a reduced rate during the warm period (idle but reserved).

SageMaker HyperPod

SageMaker HyperPod is purpose-built managed infrastructure for training and deploying foundation models at scale. It reduces training time by up to 40% through fault-tolerant infrastructure and automated cluster management.

Core Capabilities

  • Resilient Training Clusters: HyperPod continuously monitors cluster health and automatically detects and recovers from hardware failures without manual intervention. Training resumes from the last saved state.
  • Orchestration Options:
    • Slurm: Traditional HPC job scheduler for multi-node training with familiar sbatch/srun workflows.
    • Amazon EKS: Kubernetes-native orchestration with the HyperPod Training Operator, enabling cloud-native tooling, auto-scaling via Karpenter, and container-based workflows.
  • Automatic Health Checks: Deep health diagnostics (GPU, network, storage) run continuously. Faulty nodes are automatically replaced without stopping the training job.
  • Task Governance: Job queuing, prioritization, scheduling, and fair-share resource allocation via Kueue integration (EKS) or Slurm policies.

Checkpointless Training (Dec 2025)

A paradigm shift that eliminates the need for traditional checkpoint-restart cycles:

  • Enables peer-to-peer state recovery — when a node fails, the training state is reconstructed from peer nodes rather than loading from storage.
  • Achieves 80–93% reduction in recovery time (from 15–30+ minutes to under 2 minutes).
  • Enables up to 95% training goodput on clusters with thousands of AI accelerators.
  • Built on NVIDIA NeMo Framework; available through pre-built HyperPod recipes.
  • Supports both pre-training and fine-tuning (including PEFT/LoRA) for NeMo-supported models.

Elastic Training (Dec 2025)

Automatically scales training jobs based on compute resource availability and workload priority:

  • Training jobs start with the minimum required compute and dynamically scale up or down by adjusting the number of data-parallel replicas.
  • During high utilization, lower-priority elastic jobs scale down gracefully (not forcibly evicted) to yield resources to higher-priority workloads.
  • When capacity becomes available during off-peak periods, elastic jobs automatically scale back up to accelerate training.
  • Uses PyTorch Distributed Checkpoint (DCP) for seamless checkpointing and resumption across different node configurations (world sizes).
  • Supports PyTorch DDP and FSDP frameworks.
  • Integrates with Task Governance (Kueue) for priority-based scheduling and gang scheduling.

HyperPod Training Recipes

Pre-built, optimized recipes that simplify training and fine-tuning of popular foundation models:

  • Support models including DeepSeek-R1, Llama 3, Mistral, and others.
  • Pre-configured for optimal distributed training settings (parallelism strategy, batch size, learning rate).
  • Available for both Slurm and EKS orchestration.
  • Include recipes for checkpointless training and PEFT/LoRA fine-tuning.
  • Reduce time-to-train by eliminating manual configuration of distributed training parameters.

Infrastructure Features

  • Flexible Instance Groups (2026): Specify multiple instance types and subnets within a single instance group, simplifying auto-scaling with Karpenter.
  • Flexible Training Plans: Reserve accelerated compute capacity (P4d, P5, P5e, P5en, Trn1, Trn2) up to 8 weeks in advance with start times as soon as 30 minutes. Now also supports inference endpoints.
  • Custom AMIs: Use custom Amazon Machine Images for specialized software stacks.
  • CMK Integration: Customer-managed encryption keys for data security.
  • Auto-Scaling: Cluster-level auto-scaling with Karpenter on EKS orchestration.

Inference and Model Deployment

SageMaker AI provides multiple deployment options for serving ML models in production, each optimized for different latency, throughput, cost, and payload requirements.

Inference Options Comparison

Inference Type Best For Payload Size Processing Time Key Features
Real-time Low-latency, high-throughput Up to 6 MB Up to 60 seconds Persistent HTTPS endpoint, auto-scaling, A/B testing
Serverless Intermittent/unpredictable traffic Up to 4 MB Up to 60 seconds No instance management, pay-per-use, scales to zero
Batch Transform Offline processing of large datasets GB-scale Hours/Days No persistent endpoint, cost-effective for bulk inference
Asynchronous Large payloads, long processing Up to 1 GB Up to 1 hour Request queuing (SQS), scale to zero, SNS notifications
Bidirectional Streaming (2025) Real-time multi-modal (voice, live transcription) Streaming Continuous Persistent WebSocket, simultaneous send/receive

Inference Components

Inference Components provide an abstraction layer for deploying multiple models on shared infrastructure with fine-grained resource control:

  • Assign dedicated compute resources (CPU, memory, GPU, accelerators) per model component.
  • Define individual scaling policies per model — each component scales independently based on its own traffic patterns.
  • Enable intelligent model packing — SageMaker optimizes placement of multiple models on shared instances for cost efficiency.
  • Rolling Updates (2025): Deploy model updates in configurable batches with CloudWatch alarm-based automatic rollbacks, eliminating the need for duplicate infrastructure during deployments.
  • Container Caching (2026): Stores container images and model artifacts on already-running instances to reduce cold start latency when scaling up.

Multi-Model Endpoints

  • Host thousands of models behind a single endpoint, sharing compute resources.
  • Models are loaded/unloaded dynamically from S3 based on invocation patterns.
  • Support both CPU and GPU-backed models.
  • Cost-effective for scenarios with many models that have sparse or intermittent traffic.

Shadow Testing

  • Validate new models by sending copies of production traffic to a shadow variant without exposing responses to end users.
  • Compare latency, error rates, and response quality between production and shadow models.
  • Supports up to one shadow variant per endpoint.
  • Enables safe testing of model updates, instance type changes, or container modifications before promotion.

Additional Deployment Features

  • Production Variants: A/B testing with configurable traffic splitting between model versions.
  • Inference Pipelines: Chain multiple containers (preprocessing → model → postprocessing) in a single endpoint.
  • Auto-scaling: Target tracking, step scaling, and scheduled scaling policies for endpoints.
  • Inference Recommender: Automatically benchmarks model performance across instance types to recommend the optimal cost/performance configuration.
  • SageMaker Neo: Compile and optimize models for specific hardware targets (CPUs, GPUs, Inferentia, Graviton) for faster inference.

MLOps

SageMaker AI provides a comprehensive set of MLOps tools for automating, governing, and monitoring the ML lifecycle at scale.

SageMaker Pipelines

  • Purpose-built, serverless workflow orchestration for ML and LLMOps automation.
  • Define end-to-end ML workflows as directed acyclic graphs (DAGs) using the Python SDK or a visual drag-and-drop UI.
  • Built-in step types: Processing, Training, Tuning, Transform, Model Registration, Condition, Callback, Lambda, and Quality Check.
  • Supports parameterized pipelines, conditional execution, and caching of previously computed steps.
  • Multi-account support for separating dev/staging/production environments.
  • Integration with CI/CD tools (CodePipeline, Jenkins, GitLab CI) for automated retraining.

Model Registry

  • Central catalog for versioning, managing, and approving trained models before deployment.
  • Tracks model versions with metadata: training metrics, hyperparameters, data lineage, and approval status.
  • Supports model approval workflows (Pending → Approved → Rejected) for governed deployments.
  • Cross-account model sharing for enterprise ML governance.
  • Integrated with Model Cards and ML Lineage for complete audit trails.
  • Now supports generative AI assets — register datasets, custom evaluators, and fine-tuned models with automatic lineage capture.

Model Monitor

  • Continuously monitors deployed models for data quality, model quality, bias drift, and feature attribution drift.
  • Four monitoring types:
    • Data Quality: Detects schema violations, missing values, and statistical drift in input features.
    • Model Quality: Monitors accuracy, precision, recall, and other performance metrics against ground truth.
    • Bias Drift: Detects changes in fairness metrics over time (integrated with Clarify).
    • Feature Attribution Drift: Monitors changes in feature importance and SHAP values.
  • Configurable alerts via CloudWatch alarms when violations exceed thresholds.
  • Schedule monitoring jobs hourly, daily, or on custom schedules.
  • Supports foundation model monitoring including prompt drift and output quality.

Model Cards

  • Standardized documentation for ML models — capture intended use, risk ratings, training details, evaluation results, and ethical considerations.
  • Integrated with Model Registry — automatically attach Model Cards to registered model versions.
  • Export Model Cards as PDF for compliance, audit, and regulatory reporting.
  • Include evaluation metrics, bias reports (from Clarify), and custom business context.

Feature Store

  • Centralized repository for storing, sharing, and managing ML features across teams.
  • Dual-store architecture:
    • Online Store: Low-latency (single-digit ms) feature retrieval for real-time inference. Stores only the latest feature values.
    • Offline Store: Historical feature data in S3 (Parquet format) for training and batch inference. Supports time-travel queries.
  • Features organized into Feature Groups with schema definitions and metadata.
  • Supports feature ingestion via streaming (Kinesis, Kafka) or batch (Processing jobs).
  • Enables feature reuse — create once, use across multiple models and teams.

ML Lineage Tracking

  • Automatically tracks relationships between datasets, algorithms, training jobs, models, and endpoints.
  • Creates an end-to-end graph showing how a deployed model was produced — from raw data through all transformations.
  • Supports reproducibility and audit requirements by recording all inputs, parameters, and outputs.
  • Query lineage via APIs to answer questions like “What data was used to train this model?” or “Which endpoints use this model version?”
  • Now supports generative AI lineage — automatically captures relationships when fine-tuning, evaluating, and deploying foundation models.
    Cross-account lineage sharing — share lineage graphs across ML development and production accounts via AWS RAM or resource policies.
    Query lineage across accounts to trace a production model back to its training data, algorithms, and approval history in the ML account.
    Integrates with Model Registry — lineage automatically captured when registering model versions, including all upstream dependencies.
    Supports compliance requirements — generate end-to-end audit trails showing data provenance, model training history, and deployment decisions across organizational boundaries.

SageMaker AI with MLflow

SageMaker AI provides fully managed, serverless MLflow for tracking experiments, managing models, and observing AI application behavior — without infrastructure management.

  • Serverless MLflow (Dec 2025): Auto-scaling MLflow tracking servers with no server patching, capacity planning, or storage management. Spins up in minutes.
  • MLflow 3.0 Support (Jul 2025): End-to-end observability for generative AI development — experiment tracking, model registry, and tracing for GenAI applications in a single tool.
  • Experiment Tracking: Log parameters, metrics, and artifacts from training runs. Compare experiments with built-in visualization.
  • Model Registry (MLflow): Version and stage models (Staging/Production/Archived) using MLflow’s native model registry alongside SageMaker Model Registry.
  • GenAI Observability: Trace LLM calls, agent interactions, and RAG pipelines. Analyze latency, token usage, and quality metrics across generations.
  • Cross-Account Sharing: Share MLflow tracking servers across AWS accounts with fine-grained access management.
  • Integration with SageMaker AI: Seamless integration with Pipelines, Model Customization (automatic logging during fine-tuning), and training jobs.
  • Migration Support: Tools to migrate self-managed MLflow servers (EC2, on-premises) to SageMaker managed MLflow with minimal disruption.

SageMaker Lakehouse

SageMaker Lakehouse provides a unified, open, and secure data lakehouse architecture that enables analytics and AI on a single copy of data — eliminating data silos and redundant ETL.

  • Apache Iceberg Foundation: Built entirely on the open Apache Iceberg table format, ensuring interoperability with any Iceberg-compatible engine.
  • Unified Data Access: Query data in place across:
    • Amazon S3 data lakes (including S3 Tables with built-in Iceberg support)
    • Amazon Redshift Managed Storage (RMS) — access Redshift tables via Iceberg APIs
    • Federated and third-party data sources
  • Zero-ETL Integration: Stream data from operational databases (DynamoDB, Aurora, RDS) directly into Lakehouse without building ETL pipelines.
  • AWS Glue Iceberg REST Catalog: Serves as the unified catalog, compatible with Spark, Trino, Presto, Databricks, and other engines.
  • Automated Optimization (2026): Catalog-level configuration that automatically compacts, sorts, and optimizes Iceberg tables for query performance.
  • Single Copy of Data: Eliminate data duplication — ML training jobs, BI dashboards, and AI applications all access the same governed data.
  • Fine-Grained Access Control: Row-level and column-level security via AWS Lake Formation integration.
  • S3 Tables Integration (GA March 2025): Access tables stored in Amazon S3 Tables through the Iceberg REST catalog.

SageMaker JumpStart

SageMaker JumpStart provides a model hub with hundreds of pre-trained foundation models and solution templates for accelerated ML development.

  • Foundation Model Hub: Access hundreds of pre-trained, open-source models including:
    • LLMs: Llama 3/3.1/4, DeepSeek-R1, Mistral/Mixtral, Falcon, Qwen
    • Embedding models: BGE, GTE, various sentence transformers
    • Image generation: Stable Diffusion XL, SDXL Turbo
    • Vision models: CLIP, DINOv2, various ViT models
  • One-Click Deployment: Deploy models to real-time endpoints with pre-configured instance types and container settings.
  • Fine-Tuning: Fine-tune foundation models on your data using parameter-efficient methods:
    • Full fine-tuning, LoRA (Low-Rank Adaptation), QLoRA (quantized LoRA)
    • Instruction tuning for task-specific customization
    • Domain adaptation for specialized vocabularies
  • Bedrock Integration: Models deployed via JumpStart can be registered with Amazon Bedrock via Custom Model Import, enabling access through Bedrock APIs with guardrails.
  • Model Evaluation: Evaluate and compare foundation models using SageMaker Clarify’s FM evaluation capabilities.
  • Solution Templates: Pre-built ML solutions for common use cases (fraud detection, demand forecasting, recommendation engines).

SageMaker Ground Truth

SageMaker Ground Truth provides data labeling capabilities using a combination of human labelers and machine learning for automated annotation.

Ground Truth (Self-Service)

  • Create custom labeling workflows for text, image, video, audio, point cloud (3D), and multi-modal data.
  • Automated Data Labeling: Uses active learning to train a labeling model as human labels accumulate — progressively automates labeling, reducing costs by up to 70%.
  • Workforce Options:
    • Amazon Mechanical Turk (public crowd)
    • Private workforce (your in-house annotators)
    • Third-party vendor workforce
  • Built-in task types: bounding boxes, semantic segmentation, named entity recognition, text classification, image classification, and more.
  • Custom task UI via Liquid templates for specialized labeling requirements.
  • Annotation consolidation with configurable consensus algorithms.

Ground Truth Plus (Managed Service)

  • Turnkey labeling service — AWS manages the entire labeling pipeline including workforce, quality control, and project management.
  • Expert AWS-managed annotation team handles complex labeling tasks without you building labeling applications.
  • Generates demonstration data for model customization (RLHF) — captions, summaries, answers, comparative rankings.
  • Reduces labeling costs by up to 40% compared to self-managed labeling.
  • Per-label pricing (bounding box, cuboid, key-value pair, etc.).
  • Supports human-in-the-loop workflows for foundation model customization: preference labeling, reward model training data.

SageMaker Clarify

SageMaker Clarify detects bias in data and models, provides model explainability, and evaluates foundation models.

  • Bias Detection:
    • Pre-training bias metrics: Detect bias in training data before model building (e.g., Class Imbalance, Difference in Proportions of Labels).
    • Post-training bias metrics: Detect bias in model predictions (e.g., Disparate Impact, Demographic Parity Difference).
    • Supports multiple sensitive attributes (race, gender, age, etc.) simultaneously.
  • Explainability:
    • SHAP (SHapley Additive exPlanations): Feature importance values showing how each feature contributes to individual predictions.
    • Partial Dependence Plots: Show marginal effect of features on predictions.
    • Supports both tabular and NLP models.
  • Foundation Model Evaluation:
    • Evaluate FMs for accuracy, robustness, and toxicity using built-in and custom evaluation criteria.
    • Compare multiple FMs from JumpStart to select the best fit for your use case.
    • Supports both automatic evaluation (benchmark metrics) and human evaluation workflows.
  • Integrated with Model Cards for automatic documentation of fairness and explainability insights.
  • Integrated with Model Monitor for continuous bias drift detection in production.
  • Generates compliance-ready reports for regulatory requirements (EU AI Act, Fair Lending).

SageMaker AI vs Amazon Bedrock

Understanding when to use SageMaker AI vs Amazon Bedrock (based on the official AWS Decision Guide, updated June 2025):

Criteria Amazon SageMaker AI Amazon Bedrock
Best For Custom model development, extensive fine-tuning, full infrastructure control, training from scratch Serverless FM inference via API, rapid prototyping, application integration without ML expertise
Target Users Data scientists, ML engineers, developers with ML expertise Developers and businesses without deep ML expertise
Customization Full control: custom architectures, any framework, full fine-tuning, PEFT (LoRA/QLoRA), DPO, RLVR, RLAIF, distillation, pre-training from scratch API-based fine-tuning, continued pre-training, model distillation, custom model import
Model Selection Open-source models via JumpStart (Llama, DeepSeek, Mistral, Falcon, Qwen) — wider selection including specialized models Proprietary + open models (Claude, Amazon Nova/Titan, Llama, Mistral, Cohere, AI21) — includes exclusive proprietary models
Infrastructure Customer-managed instances (GPU, Trainium, Inferentia) — full control over compute, scaling, placement Fully managed/serverless — no instance provisioning or management
Pricing Pay for compute resources (instances, storage, data transfer) — variable based on usage Pay-per-API-call (per token) — simpler, predictable pricing
Deployment Serverful (real-time endpoints, batch) + serverless options; granular control over scaling Serverless by default; no endpoint management
Integration JumpStart models can be imported into Bedrock via Custom Model Import Bedrock IDE available in SageMaker Unified Studio; both accessible from same platform
Use Together Prototype with Bedrock APIs → Fine-tune with SageMaker AI → Deploy via Bedrock (Custom Model Import) or SageMaker endpoints. Most mature enterprises use both.

When to Choose SageMaker AI:

  • You need to train models from scratch or perform extensive custom fine-tuning
  • High token volume with predictable workloads (dedicated instances are more cost-effective)
  • Compliance requires complete VPC data isolation and infrastructure control
  • AI/ML is your core product requiring full customization of model architecture
  • You need specialized hardware (Trainium, specific GPU types) for training

When to Choose Bedrock:

  • You primarily need inference from pre-trained foundation models via API
  • You want serverless, no-infrastructure generative AI integration
  • You need access to proprietary models (Claude, Amazon Nova)
  • Your team lacks deep ML expertise but wants to leverage AI capabilities
  • You need built-in guardrails, RAG (Knowledge Bases), and agent orchestration

AWS ML Accelerators

AWS offers custom silicon optimized for machine learning workloads, providing significant cost-performance advantages over general-purpose GPUs:

  • AWS Trainium2 (GA December 2024):
    • 4x faster, 4x more memory bandwidth, 3x more memory capacity than Trn1.
    • 30–40% better price-performance than GPU-based P5e/P5en instances.
    • Supports training models with hundreds of billions to trillion+ parameters.
    • Available via EC2 Trn2 and Trn2 UltraServer instances.
  • AWS Trainium3 (Announced re:Invent 2025):
    • Built on TSMC 3nm process; delivers 2.52 PFLOPS per chip.
    • Supports NVLink Fusion for hybrid GPU/Trainium clusters.
  • AWS Inferentia2:
    • 3x higher compute, 4x larger memory, up to 10x lower latency vs. first-gen Inferentia.
    • Optimized for LLMs, diffusion models, and vision transformers.
    • Available via EC2 Inf2 instances.
  • AWS Trainium (first gen): EC2 Trn1 instances; up to 50% cost savings over comparable GPUs.

SageMaker AI Pricing

SageMaker AI follows a pay-as-you-go pricing model with no upfront commitments:

  • Notebooks: Billed per instance-hour based on the instance type (ml.t3.medium through ml.p5.48xlarge).
  • Training: Per-second billing for training instance usage; choice of On-Demand, Spot (up to 90% savings), or Reserved (Flexible Training Plans).
  • Inference: Per-second billing for endpoint instances (real-time), per-request (serverless), or per-job (batch).
  • Serverless Model Customization: Pay-per-token pricing for both training and inference — no infrastructure management.
  • Storage: EBS volumes for notebooks, S3 for training data and model artifacts, Feature Store storage fees.
  • Data Labeling: Per-label pricing for Ground Truth (varies by annotation type).

Cost Optimization Features:

  • Managed Spot Training — Up to 90% savings on training jobs
  • Inference Components — Intelligent model packing for multi-model cost efficiency
  • Multi-Model Endpoints — Share infrastructure across hundreds of models
  • Serverless Inference — Scale to zero, pay only for invocations
  • Auto-Scaling — Match compute to demand automatically
  • SageMaker Savings Plans — Up to 64% savings for committed usage (1 or 3 year)
  • Flexible Training Plans — Reserved compute capacity at predictable pricing
  • Trainium/Inferentia Instances — 50–70% cost savings vs. comparable GPUs
  • Warm Pools — Reduce idle time billing between iterative training jobs

Certification Exam Relevance

SageMaker AI is heavily tested across multiple AWS certification exams:

Certification SageMaker AI Coverage
AWS Certified Machine Learning Engineer – Associate (MLA-C01) Core exam focus. Covers SageMaker Pipelines, training, deployment, MLOps, Feature Store, Model Monitor, distributed training, hyperparameter tuning. ~60-70% of questions involve SageMaker AI.
AWS Certified Solutions Architect – Associate (SAA-C03) High-level understanding of SageMaker AI as a managed ML service. Know inference options, when to use SageMaker vs Bedrock, integration with S3/VPC/IAM.
AWS Certified AI Practitioner (AIF-C01) Foundational understanding of SageMaker AI capabilities. Know SageMaker Canvas (no-code), JumpStart, basic training/deployment concepts, and how it compares to Bedrock.
AWS Certified Machine Learning – Specialty (MLS-C01) Deep coverage of SageMaker algorithms, training optimization, deployment strategies, security, and ML lifecycle. Being replaced by MLA-C01.

AWS Certification Exam Practice Questions

  • Questions are collected from various sources and answers reflect our understanding, which may differ from yours.
  • AWS services are updated frequently, so some information may become outdated.
  • We welcome feedback and corrections to improve accuracy.
  1. A company wants to train a large language model with hundreds of billions of parameters but is concerned about hardware failures interrupting multi-week training jobs. They need the fastest possible recovery time when failures occur. Which SageMaker AI capability should they use?
    1. SageMaker Managed Spot Training with checkpoints
    2. SageMaker HyperPod with checkpointless training
    3. SageMaker Distributed Training with data parallelism
    4. SageMaker Warm Pools
    Show Answer

    Answer: B – SageMaker HyperPod with checkpointless training enables peer-to-peer state recovery with 80–93% reduction in recovery time (under 2 minutes vs. 15–30+ minutes for traditional checkpoint-based recovery), achieving up to 95% training goodput on large clusters.

  2. A data science team needs to fine-tune a foundation model but wants to avoid managing infrastructure. They want automatic compute provisioning and pay-per-token pricing. Which SageMaker AI feature should they use?
    1. SageMaker HyperPod with Training Recipes
    2. SageMaker JumpStart fine-tuning
    3. SageMaker Serverless Model Customization
    4. SageMaker Canvas LLM fine-tuning

    Answer: C — SageMaker Serverless Model Customization automatically provisions compute resources based on model and data size, supports advanced techniques (SFT, DPO, RLVR, RLAIF), and uses pay-per-token pricing without any infrastructure management.

  3. An organization is deploying multiple foundation models and wants to optimize costs by efficiently sharing GPU resources while maintaining independent scaling policies for each model. Which approach should they use?
    1. Deploy each model on a separate real-time endpoint with auto-scaling
    2. Use SageMaker Multi-Model Endpoints
    3. Use SageMaker Inference Components with per-model scaling policies
    4. Use SageMaker Serverless Inference

    Answer: C — Inference Components enable assigning dedicated resources per model while optimizing utilization through intelligent model packing on shared infrastructure. Each component scales independently based on its own traffic patterns, unlike multi-model endpoints which share all resources.

  4. A company wants their ML training jobs to automatically expand when cluster resources are idle and shrink when higher-priority workloads need capacity, without manual intervention. Which SageMaker HyperPod feature enables this?
    1. Flexible Training Plans
    2. Checkpointless training
    3. Elastic training
    4. Managed Spot Training

    Answer: C — Elastic training on SageMaker HyperPod automatically scales training jobs by adjusting the number of data-parallel replicas based on resource availability. Jobs scale down for higher-priority workloads and scale back up when resources free up, using automatic checkpointing and resumption across different world sizes.

  5. A solutions architect needs to provide a unified data architecture where data scientists can access data from S3 data lakes and Redshift data warehouses using a single query interface, without copying data between systems. Which service provides this? (Select TWO)
    1. Amazon SageMaker Lakehouse
    2. Amazon SageMaker Feature Store
    3. AWS Glue Iceberg REST Catalog
    4. Amazon SageMaker Data Wrangler
    5. Amazon SageMaker Pipelines

    Answer: A, C — SageMaker Lakehouse provides the unified open lakehouse architecture built on Apache Iceberg, and the AWS Glue Iceberg REST Catalog serves as the unified metadata catalog that enables querying data across S3 data lakes (including S3 Tables) and Redshift Managed Storage without data movement.

Frequently Asked Questions

What is Amazon SageMaker AI?

Amazon SageMaker AI (rebranded in 2024) is a fully managed platform for building, training, and deploying machine learning models at scale. It provides Studio IDE, no-code Canvas, HyperPod training clusters, managed MLflow, inference endpoints, and MLOps capabilities.

What is SageMaker HyperPod?

HyperPod provides managed training clusters with resilient infrastructure. Key features include checkpointless training (80-93% faster failure recovery without checkpoints), elastic training (auto-scale compute mid-job), and training recipes for popular model architectures.

When should I use SageMaker vs Bedrock?

Use SageMaker when you need custom model training, full control over algorithms, or specialized ML workflows. Use Bedrock when you want to build gen AI applications using pre-trained foundation models with features like RAG, agents, and guardrails without ML expertise.

References

Amazon SageMaker AI Documentation

Amazon SageMaker FAQs

Amazon SageMaker AI Pricing

AWS Decision Guide: Bedrock or SageMaker AI?

Amazon SageMaker Lakehouse

Amazon SageMaker AI with MLflow

Amazon SageMaker Ground Truth

Amazon SageMaker Canvas

AWS Trainium

AWS Inferentia

SageMaker HyperPod: Checkpointless and Elastic Training

Machine Learning Concepts – Cheat Sheet

Machine Learning Concepts

📋 Certification Relevance (Updated June 2026)

This post covers Machine Learning concepts relevant for:

  • AWS Certified AI Practitioner (AIF-C01) — Domain 1: AI and ML Fundamentals (20%)
  • AWS Certified Machine Learning Engineer – Associate (MLA-C01) — Domain 2: ML Model Development (26%)
  • AWS Certified Generative AI Developer – Professional (New in 2026)

Note: The AWS Certified Machine Learning – Specialty exam was retired on March 31, 2026. It has been replaced by the ML Engineer Associate and the new Generative AI Developer Professional certifications.

This post covers some of the basic Machine Learning concepts mostly relevant for the AWS AI and Machine Learning certification exams.

Machine Learning Lifecycle

Data Processing and Exploratory Analysis

  • To train a model, you need data.
  • Type of data that depends on the business problem that you want the model to solve (the inferences that you want the model to generate).
  • Process data includes data collection, data cleaning, data split, data exploring, preprocessing, transformation, formatting etc.

Feature Selection and Engineering

  • helps improve model accuracy and speed up training
  • remove irrelevant data inputs using domain knowledge for e.g. name
  • remove features which has same values, very low correlation, very little variance or lot of missing values
  • handle missing data using mean values or imputation
  • combine features which are related for e.g. height and age to height/age
  • convert or transform features to useful representation for e.g. date to day or hour
  • standardize data ranges across features

Missing Data

  • do nothing
  • remove the feature with lot of missing data points
  • remove samples with missing data, if the feature needs to be used
  • Impute using mean/median value
    • no impact and the dataset is not skewed
    • works with numerical values only. Do not use for categorical features.
    • doesn’t factor correlations between features
  • Impute using (Most Frequent) or (Zero/Constant) Values
    • works with categorical features
    • doesn’t factor correlations between features
    • can introduce bias
  • Impute using k-NN, Multivariate Imputation by Chained Equation (MICE), Deep Learning
    • more accurate than the mean, median or most frequent
    • Computationally expensive

Unbalanced Data

  • Source more real data
  • Oversampling instances of the minority class or undersampling instances of the majority class
  • Create or synthesize data using techniques like SMOTE (Synthetic Minority Oversampling TEchnique)

Label Encoding and One-hot Encoding

  • Models cannot multiply strings by the learned weights, encoding helps convert strings to numeric values.
  • Label encoding
    • Use Label encoding to provide lookup or map string data values to a numerical values
    • However, the values are random and would impact the model
  • One-hot encoding
    • Use One-hot encoding for Categorical features that have a discrete set of possible values.
    • One-hot encoding provide binary representation by converting data values into features without impacting the relationships
    • a binary vector is created for each categorical feature in the model that represents values as follows:
      • For values that apply to the example, set corresponding vector elements to 1.
      • Set all other elements to 0.
    • Multi-hot encoding is when multiple values are 1

Cleaning Data

  • Scaling or Normalization means converting floating-point feature values from their natural range (for example, 100 to 900) into a standard range (for example, 0 to 1 or -1 to +1)

Train a model

  • Model training includes both training and evaluating the model,
  • To train a model, algorithm is needed.
  • Data can be split into training data, validation data and test data
    • Algorithm sees and is directly influenced by the training data
    • Algorithm uses but is indirectly influenced by the validation data
    • Algorithm does not see the testing data during training
  • Training can be performed using normal parameters or features and hyperparameters

Supervised, Unsupervised, Semi-Supervised, and Reinforcement Learning

Supervised Learning

  • Uses labeled data — both input features and correct output (target) are provided
  • Model learns mapping between inputs and outputs
  • Types: Classification (categorical output) and Regression (continuous output)
  • Examples: spam detection, image classification, price prediction

Unsupervised Learning

  • Uses unlabeled data — no target variable provided
  • Model discovers hidden patterns or structures in data
  • Types: Clustering, Dimensionality Reduction, Anomaly Detection, Association
  • Examples: customer segmentation, PCA, anomaly detection

Semi-Supervised Learning

  • Combines a small amount of labeled data with a large amount of unlabeled data
  • Useful when labeling data is expensive or time-consuming
  • The model learns from labeled data and generalizes using unlabeled data patterns
  • Examples: medical image classification (few expert-labeled images + many unlabeled)

Self-Supervised Learning

  • A form of unsupervised learning where the model generates its own labels from the input data
  • The foundation of modern Large Language Models (LLMs) and Foundation Models
  • Techniques include masked language modeling (predict missing words) and next-token prediction
  • Enables pre-training on massive unlabeled datasets before fine-tuning on specific tasks
  • Examples: BERT (masked word prediction), GPT (next-token prediction)

Reinforcement Learning

  • Agent learns by interacting with an environment and receiving rewards or penalties
  • Goal is to maximize cumulative reward through trial and error
  • Key concepts: Agent, Environment, State, Action, Reward, Policy
  • Used in robotics, game playing, autonomous vehicles, recommendation systems
  • Reinforcement Learning from Human Feedback (RLHF) — used to fine-tune LLMs based on human preference rankings (key technique behind ChatGPT and similar models)

Splitting and Randomization

  • Always randomize the data before splitting

Hyperparameters

  • influence how the training occurs
  • Common hyperparameters are learning rate, epoch, batch size
  • Learning rate
    • size of the step taken during gradient descent optimization
    • Large learning rates can overshoot the correct solution
    • Small learning rates increase training time
  • Batch size
    • number of samples used to train at any one time
    • can be all (batch), one (stochastic), or some (mini-batch)
    • calculable from infrastructure
    • Small batch sizes tend to not get stuck in local minima
    • Large batch sizes can converge on the wrong solution at random.
  • Epochs
    • number of times the algorithm processes the entire training data
    • each epoch or run can see the model get closer to the desired state
  • depends on algorithm used

Evaluating the model

After training the model, evaluate it to determine whether the accuracy of the inferences is acceptable.

ML Model Insights

  • For binary classification models use accuracy metric called Area Under the (Receiver Operating Characteristic) Curve (AUC). AUC measures the ability of the model to predict a higher score for positive examples as compared to negative examples.
  • For regression tasks, use the industry standard root mean square error (RMSE) metric. It is a distance measure between the predicted numeric target and the actual numeric answer (ground truth). The smaller the value of the RMSE, the better is the predictive accuracy of the model.

Cross-Validation

  • is a technique for evaluating ML models by training several ML models on subsets of the available input data and evaluating them on the complementary subset of the data.
  • Use cross-validation to detect overfitting, ie, failing to generalize a pattern.
  • there is no separate validation data, involves splitting the training data into chunks of validation data and use it for validation

Optimization

  • Gradient Descent is used to optimize many different types of machine learning algorithms
  • Step size sets Learning rate
    • If the learning rate is too large, the minimum slope might be missed and the graph would oscillate
    • If the learning rate is too small, it requires too many steps which would take the process longer and is less efficient

Underfitting

  • Model is underfitting the training data when the model performs poorly on the training data because the model is unable to capture the relationship between the input examples (often called X) and the target values (often called Y).
  • To increase model flexibility
    • Add new domain-specific features and more feature Cartesian products, and change the types of feature processing used (e.g., increasing n-grams size)
    • Regularization – Decrease the amount of regularization used
    • Increase the amount of training data examples.
    • Increase the number of passes on the existing training data.

Overfitting

  • Model is overfitting the training data when the model performs well on the training data but does not perform well on the evaluation data because the model is memorizing the data it has seen and is unable to generalize to unseen examples.
  • To increase model flexibility
    • Feature selection: consider using fewer feature combinations, decrease n-grams size, and decrease the number of numeric attribute bins.
    • Simplify the model, by reducing the number of layers.
    • Regularization – technique to reduce the complexity of the model. Increase the amount of regularization used.
    • Early Stopping – a form of regularization while training a model with an iterative method, such as gradient descent.
    • Data Augmentation – process of artificially generating new data from existing data, primarily to train new ML models.
    • Dropout is a regularization technique that prevents overfitting.

Deep Learning and Neural Networks

  • Deep Learning is a subset of machine learning that uses neural networks with multiple layers (deep neural networks) to learn complex patterns
  • Excels at tasks involving unstructured data (images, text, audio)
  • Requires large amounts of data and significant compute resources

Neural Network Fundamentals

  • Composed of layers: Input Layer, Hidden Layers, and Output Layer
  • Each neuron applies weights, bias, and an activation function to its inputs
  • Common activation functions: ReLU, Sigmoid, Tanh, Softmax
  • Backpropagation — algorithm used to calculate gradients and update weights during training
  • A network with 2+ hidden layers is considered a “deep” neural network

Types of Neural Networks

Convolutional Neural Networks (CNNs)

  • Specialized for processing grid-like data (images, spatial data)
  • Uses convolutional layers with filters/kernels to detect features (edges, shapes, objects)
  • Key layers: Convolutional, Pooling (Max/Average), Fully Connected
  • Use cases: image classification, object detection, computer vision

Recurrent Neural Networks (RNNs)

  • Designed for sequential data (time series, text, speech)
  • Maintains internal state (memory) that captures information from previous time steps
  • LSTM (Long Short-Term Memory) — addresses vanishing gradient problem with gates (forget, input, output)
  • GRU (Gated Recurrent Unit) — simplified version of LSTM with fewer parameters
  • Largely superseded by Transformers for NLP tasks due to inability to parallelize

Transformers

  • Architecture introduced in “Attention Is All You Need” (2017) — foundation of modern LLMs
  • Processes entire input sequences in parallel using self-attention mechanism
  • Key innovation: Attention mechanism allows each token to attend to every other token regardless of distance
  • Components: Multi-Head Attention, Positional Encoding, Feed-Forward Layers, Layer Normalization
  • Encoder — processes input and creates representations (BERT-style models)
  • Decoder — generates output tokens auto-regressively (GPT-style models)
  • Encoder-Decoder — used for sequence-to-sequence tasks (T5, translation)
  • Use cases: NLP, text generation, translation, code generation, image generation

Generative Adversarial Networks (GANs)

  • Two networks compete: Generator (creates synthetic data) vs Discriminator (detects fake data)
  • Training improves both networks iteratively
  • Use cases: image generation, style transfer, data augmentation

Generative AI and Foundation Models

  • Generative AI is a subset of deep learning that creates new content (text, images, code, audio, video) based on patterns learned from training data
  • Foundation Models (FMs) are large pre-trained models trained on broad datasets that can be adapted for many downstream tasks
  • Examples: GPT-4, Claude, Amazon Titan, Amazon Nova, Llama, Gemini

Large Language Models (LLMs)

  • Foundation models trained on massive text corpora using self-supervised learning
  • Based on the Transformer architecture
  • Capabilities: text generation, summarization, translation, code generation, reasoning
  • Key characteristics:
    • Parameters — learned weights (billions to trillions); more parameters generally = more capability
    • Context window — maximum number of tokens the model can process at once
    • Tokens — basic units of text (words or sub-words) the model processes
    • Temperature — controls randomness of output (0 = deterministic, higher = more creative)

Customizing Foundation Models

Prompt Engineering

  • Crafting input prompts to guide model output without changing model weights
  • Zero-shot — no examples provided in prompt
  • Few-shot — providing examples in the prompt to guide the response
  • Chain-of-thought — guiding model to show reasoning steps
  • No training required; fastest and cheapest customization method

Retrieval-Augmented Generation (RAG)

  • Combines retrieval of external knowledge with generation of responses
  • Retrieves relevant documents from a knowledge base and includes them in the prompt context
  • Reduces hallucinations by grounding responses in factual data
  • No model retraining required; knowledge base can be updated independently
  • Components: Document store, Embedding model, Vector database, Retriever, Generator
  • AWS service: Amazon Bedrock Knowledge Bases

Fine-Tuning

  • Further training a pre-trained model on a task-specific labeled dataset
  • Updates model weights to specialize for specific domain or task
  • Requires labeled training data and compute resources
  • Types:
    • Full fine-tuning — updates all model parameters (expensive)
    • Parameter-Efficient Fine-Tuning (PEFT) — updates only a small subset of parameters
    • LoRA (Low-Rank Adaptation) — adds small trainable matrices to frozen model layers
  • AWS service: Amazon Bedrock and Amazon SageMaker AI

Continued Pre-Training

  • Training a foundation model on additional domain-specific unlabeled data
  • Teaches the model new domain knowledge (medical, legal, financial terminology)
  • More expensive than fine-tuning but creates deeper domain understanding

Transfer Learning

  • Technique of using a model trained on one task as the starting point for a related task
  • Reduces training time and data requirements significantly
  • Foundation models are the ultimate form of transfer learning — pre-trained on broad data, then adapted
  • Approaches: Feature extraction (freeze base layers) or Fine-tuning (update some/all layers)

Agentic AI

  • AI systems that can autonomously plan, reason, and take actions to accomplish goals
  • Uses tools, APIs, and knowledge bases to complete multi-step tasks
  • Key components: Planning, Memory, Tool use, Reasoning
  • AWS service: Amazon Bedrock Agents, Amazon Bedrock AgentCore

Classification Model Evaluation

Confusion Matrix

  • Confusion matrix represents the percentage of times each label was predicted in the training set during evaluation
  • An NxN table that summarizes how successful a classification model’s predictions were; that is, the correlation between the label and the model’s classification.
  • One axis of a confusion matrix is the label that the model predicted, and the other axis is the actual label.
  • N represents the number of classes. In a binary classification problem, N=2
    • For example, here is a sample confusion matrix for a binary classification problem:
Tumor (predicted) Non-Tumor (predicted)
Tumor (actual) 18 (True Positives) 1 (False Negatives)
Non-Tumor (actual) 6 (False Positives) 452 (True Negatives)
    • Confusion matrix shows that of the 19 samples that actually had tumors, the model correctly classified 18 as having tumors (18 true positives), and incorrectly classified 1 as not having a tumor (1 false negative).
    • Similarly, of 458 samples that actually did not have tumors, 452 were correctly classified (452 true negatives) and 6 were incorrectly classified (6 false positives).
  • Confusion matrix for a multi-class classification problem can help you determine mistake patterns. For example, a confusion matrix could reveal that a model trained to recognize handwritten digits tends to mistakenly predict 9 instead of 4, or 1 instead of 7.

Accuracy, Precision, Recall (Sensitivity) and Specificity

Accuracy

  • A metric for classification models, that identifies fraction of predictions that a classification model got right.
  • In Binary classification, calculated as (True Positives+True Negatives)/Total Number Of Examples
  • In Multi-class classification, calculated as Correct Predictions/Total Number Of Examples

Precision

  • A metric for classification models. that identifies the frequency with which a model was correct when predicting the positive class.
  • Calculated as True Positives/(True Positives + False Positives)

Recall – Sensitivity – True Positive Rate (TPR)

  • A metric for classification models that answers the following question: Out of all the possible positive labels, how many did the model correctly identify i.e. Number of correct positives out of actual positive results
  • Calculated as True Positives/(True Positives + False Negatives)
  • Important when – False Positives are acceptable as long as ALL positives are found for e.g. it is fine to predict Non-Tumor as Tumor as long as All the Tumors are correctly predicted

Specificity – True Negative Rate (TNR)

  • Number of correct negatives out of actual negative results
  • Calculated as True Negatives/(True Negatives + False Positives)
  • Important when – False Positives are unacceptable; it’s better to have false negatives for e.g. it is not fine to predict Non-Tumor as Tumor;

ROC and AUC

ROC (Receiver Operating Characteristic) Curve

  • An ROC curve (receiver operating characteristic curve) is curve of true positive rate vs. false positive rate at different classification thresholds.
  • An ROC curve is a graph showing the performance of a classification model at all classification thresholds.
  • An ROC curve plots True Positive Rate (TPR) vs. False Positive Rate (FPR) at different classification thresholds. Lowering the classification threshold classifies more items as positive, thus increasing both False Positives and True Positives.

    ROC Curve showing TP Rate vs. FP Rate at different classification thresholds.

AUC (Area under the ROC curve)

  • AUC stands for “Area under the ROC Curve.”
  • AUC measures the entire two-dimensional area underneath the entire ROC curve (think integral calculus) from (0,0) to (1,1).
  • AUC provides an aggregate measure of performance across all possible classification thresholds.
  • One way of interpreting AUC is as the probability that the model ranks a random positive example more highly than a random negative example.

AUC (Area under the ROC Curve).

F1 Score

  • F1 score (also F-score or F-measure) is a measure of a test’s accuracy.
  • It considers both the precision p and the recall r of the test to compute the score: p is the number of correct positive results divided by the number of all positive results returned by the classifier, and r is the number of correct positive results divided by the number of all relevant samples (all samples that should have been identified as positive).
  • Calculated as: F1 = 2 × (Precision × Recall) / (Precision + Recall)
  • Ranges from 0 to 1, with 1 being perfect precision and recall
  • Useful when you need a balance between precision and recall, especially with imbalanced datasets

Generative AI Evaluation Metrics

  • Traditional ML metrics (accuracy, F1) are insufficient for evaluating generative AI outputs
  • Generative AI requires metrics that measure quality, safety, relevance, and factual accuracy

Text Generation Metrics

BLEU (Bilingual Evaluation Understudy)

  • Measures n-gram overlap between generated text and reference text
  • Ranges from 0 to 1 (higher is better)
  • Originally designed for machine translation evaluation
  • Limitation: only measures lexical similarity, not semantic meaning

ROUGE (Recall-Oriented Understudy for Gisting Evaluation)

  • Measures overlap between generated summary and reference summary
  • ROUGE-N — n-gram overlap (ROUGE-1 = unigrams, ROUGE-2 = bigrams)
  • ROUGE-L — longest common subsequence
  • Commonly used for summarization tasks

Perplexity

  • Measures how well a model predicts a sequence of words
  • Lower perplexity = better model (model is less “surprised” by the text)
  • Useful for comparing language models but doesn’t directly measure output quality

BERTScore

  • Uses contextual embeddings to measure semantic similarity between generated and reference text
  • Better than BLEU/ROUGE at capturing meaning rather than just word overlap

Generative AI Safety Metrics

Hallucination Rate

  • Measures how often a model generates factually incorrect or fabricated information
  • Critical metric for production deployments
  • Mitigated by RAG, grounding, and guardrails

Groundedness

  • Measures whether model responses are supported by provided context/source documents
  • Key metric for RAG systems

Toxicity and Content Safety

  • Measures presence of harmful, biased, or inappropriate content in outputs
  • AWS service: Amazon Bedrock Guardrails for content filtering

Human Evaluation and LLM-as-a-Judge

  • Human evaluation remains the gold standard for assessing quality, helpfulness, and safety
  • LLM-as-a-Judge — using a capable LLM to evaluate outputs of another model (scalable alternative to human evaluation)
  • AWS service: Amazon Bedrock Evaluations for automated model evaluation

Responsible AI and ML Fairness

  • Ensuring AI systems are fair, transparent, accountable, and safe
  • Regulatory frameworks: EU AI Act, ISO 42001, NIST AI RMF

Bias in Machine Learning

  • Data Bias — bias present in training data (sampling bias, historical bias, measurement bias)
  • Algorithmic Bias — bias introduced by the model or training process
  • Selection Bias — non-representative training data
  • Detection: AWS Amazon SageMaker Clarify provides pre-training and post-training bias detection metrics

Explainability and Interpretability

  • Explainability — ability to understand why a model made a specific prediction
  • Techniques: SHAP (SHapley Additive exPlanations), feature importance, attention visualization
  • AWS service: Amazon SageMaker Clarify for model explainability
  • Critical for regulated industries (healthcare, finance) where decisions must be justified

Model Governance

  • Tracking model lineage, versioning, and approval workflows
  • Model cards documenting intended use, limitations, and evaluation results
  • AWS service: Amazon SageMaker Model Registry and SageMaker Data & AI Governance

Deploy the model

  • Re-engineer a model before integrating it with the application and deploy it.
  • Can be deployed as a Batch or as a Service (real-time endpoint)
  • Model Monitoring — continuously track model performance in production to detect drift
    • Data Drift — input data distribution changes over time compared to training data
    • Model Drift (Concept Drift) — relationship between input and output changes over time
    • Requires retraining or updating the model when drift is detected
  • A/B Testing — deploying multiple model variants to compare performance with real traffic
  • Shadow Deployment — running new model alongside production model without serving its predictions to users

AWS Machine Learning Services Summary

  • Amazon SageMaker AI — fully managed service to build, train, and deploy ML models at scale
  • Amazon Bedrock — managed service to build generative AI applications using foundation models (Amazon Titan, Amazon Nova, Claude, Llama, etc.)
  • Amazon Bedrock Knowledge Bases — managed RAG service
  • Amazon Bedrock Agents — build autonomous AI agents
  • Amazon Bedrock Guardrails — content filtering and safety controls
  • Amazon Q Developer — AI-powered coding assistant
  • Amazon SageMaker Clarify — bias detection and model explainability
  • Amazon Comprehend — NLP service for text analysis
  • Amazon Rekognition — computer vision service
  • Amazon Transcribe — speech-to-text
  • Amazon Polly — text-to-speech
  • Amazon Translate — language translation

References

RDS Blue/Green Deployments – Zero-Downtime Updates

RDS Blue/Green Deployment

Amazon RDS Blue/Green Deployments

  • Amazon RDS Blue/Green Deployments help make and test database changes before implementing them in a production environment.
  • RDS Blue/Green Deployment has the blue environment as the current production environment and the green environment as the staging environment.
  • RDS Blue/Green Deployment creates a staging or green environment that exactly copies the production environment.
  • Green environment is a copy of the topology of the production environment and includes the features used by the DB instance including the Multi-AZ deployment, read replicas, the storage configuration, DB snapshots, automated backups, Performance Insights, and Enhanced Monitoring.
  • Green environment or the staging environment always stays in sync with the current production environment using logical replication (for major version upgrades) or physical replication (for minor version upgrades in PostgreSQL).
  • RDS DB instances in the green environment can be changed without affecting production workloads. Changes can include the upgrade of major or minor DB engine versions, upgrade of underlying file system configuration, or change of database parameters in the staging environment.
  • Changes can be thoroughly tested in the green environment and when ready, the environments can be switched over to promote the green environment to be the new production environment.
  • Switchover typically takes under five seconds for single-Region configurations with no data loss and no need for application changes. Applications using the AWS Advanced JDBC Driver typically see two seconds or lower downtime.
  • Blue/Green Deployments are supported for RDS for MariaDB, RDS for MySQL, and RDS for PostgreSQL.
  • For Amazon Aurora, Blue/Green Deployments are supported for Aurora MySQL, Aurora PostgreSQL, and Aurora Global Database.

RDS Blue/Green Deployment

RDS Blue/Green Deployments Benefits

  • Easily create a production-ready staging environment.
  • Automatically replicate database changes from the production environment to the staging environment.
  • Test database changes in a safe staging environment without affecting the production environment.
  • Stay current with database patches and system updates.
  • Implement and test newer database features.
  • Switch over your staging environment to be the new production environment without changes to your application.
  • Safely switch over through the use of built-in switchover guardrails.
  • Eliminate data loss during switchover.
  • Switch over quickly, typically under five seconds for single-Region configurations.

RDS Blue/Green Deployment Switchover

  • A switchover transitions the green environment to be the new production environment.
  • Before switchover, production traffic is routed to the blue environment. After switchover, production traffic is routed to the green environment.
  • RDS renames the DB instances in the green environment to match the corresponding blue environment names, and renames the blue environment instances by appending -oldN to the current name.
  • Endpoints in the green environment are renamed to match the blue environment so no application changes are required.
  • A switchover timeout period can be specified between 30 seconds and 3,600 seconds (one hour). Default is 300 seconds (five minutes). If switchover takes longer, changes are rolled back.

Switchover Actions

  • Runs guardrail checks to verify both environments are ready for switchover.
  • Stops new write operations on the primary DB instance in both environments.
  • Drops connections to the DB instances in both environments and disallows new connections.
  • Waits for replication to catch up in the green environment so it is in sync with the blue environment.
  • Renames DB instances in both environments (green gets production names, blue gets -oldN suffix).
  • Allows connections to databases in both environments.
  • Allows write operations on the primary DB instance in the new production environment.

Switchover Guardrails

  • Amazon RDS runs guardrail checks to test the readiness of both environments before switchover.
  • Green environment checks:
    • Replication health – Checks if green primary DB instance replication status is healthy.
    • Replication lag – Checks if the replica lag is within allowable limits based on the specified timeout period.
    • Active writes – Makes sure there are no active writes on the green primary DB instance.
  • Blue environment checks:
    • External replication – Makes sure the blue environment isn’t a self-managed logical source or replica.
    • Long-running active writes – Makes sure there are no long-running active writes on the blue primary DB instance.
    • Long-running DDL statements – Makes sure there are no long-running DDL statements on the blue primary DB instance.
    • Unsupported PostgreSQL changes (logical replication) – Makes sure no DDL changes or large object modifications have been performed.
  • If guardrails fail, the switchover is blocked and environments remain unchanged.

After Switchover

  • DB instances in the previous blue environment are retained (standard costs apply).
  • Replication between blue and green environments stops.
  • The old blue environment DB instances are read-only until the read_only parameter (MySQL) or default_transaction_read_only parameter (PostgreSQL) is set to 0.
  • Resource IDs don’t change during switchover, but names do. Update resource IDs used in IAM policies, Performance Insights, CloudTrail, and AWS Backup.

RDS Proxy with Blue/Green Deployments

  • (New – April 2026) Amazon RDS Blue/Green Deployments now supports Amazon RDS Proxy, enabling faster application recovery during switchover by eliminating DNS propagation delays.
  • During switchover, RDS Proxy actively monitors database instances and detects when the Green environment becomes the new production environment.
  • RDS Proxy quickly redirects connections to the Green environment, enabling faster application recovery without driver modifications or application changes.
  • During the transitional period, the Blue database enters read-only mode before Green environment is promoted. RDS Proxy continues routing connections to the blue database during this period.
  • Once switchover is detected, the proxy automatically routes traffic to the newly promoted green environment.
  • When the Green environment is promoted, existing connections to the proxy are dropped and applications must re-establish connections.
  • Available for Aurora MySQL, Aurora PostgreSQL, RDS for MySQL, RDS for PostgreSQL, and RDS for MariaDB in all commercial AWS Regions where RDS Proxy is available.
  • Limitation: RDS Proxy with Blue/Green Deployments is not supported for Aurora Global Databases.
  • Note: The blue cluster must be registered with the proxy before creating a blue/green deployment. If a deployment already exists for a given blue cluster, registering it to RDS Proxy will be blocked.

AWS Advanced JDBC Driver with Blue/Green Deployments

  • (New – January/February 2026) Blue/Green Deployments support the AWS Advanced JDBC Driver (for PostgreSQL) as a smart driver alternative for faster switchover.
  • The AWS Advanced JDBC Driver detects topology changes and redirects connections to the new production environment without waiting for DNS propagation.
  • Applications using the AWS Advanced JDBC Driver typically see two seconds or lower downtime during switchover.
  • The blue/green deployment plugin in the driver provides automatic connection management during database switchovers.
  • Note: The AWS JDBC Driver for MySQL is NOT supported for blue/green deployments.

PostgreSQL Replication Methods

  • (Updated – November 2024) RDS for PostgreSQL Blue/Green Deployments now use physical replication by default for minor version upgrades.
  • Physical replication is used when no major version upgrade is specified at creation time.
  • Logical replication is used when a major version upgrade is specified during blue/green deployment creation.
  • Physical replication benefits:
    • Overcomes most limitations of logical replication.
    • Well-suited for minor version upgrades, schema changes (DDL) in the blue environment, and storage adjustments.
    • Does not support table modifications on the green instance (green is strictly read-only).
  • Logical replication limitations:
    • DDL statements (CREATE TABLE, CREATE SCHEMA) are not replicated from blue to green.
    • DCL statements (GRANT, REVOKE) are not replicated.
    • Large objects in the blue environment are not replicated to the green environment.
    • Unlogged tables are not replicated.
    • Materialized views are not automatically refreshed in the green environment.
    • UPDATE and DELETE operations require tables to have a primary key.
    • The apply process is single-threaded, which may cause lag with high write throughput.

Aurora Global Database Support

  • (New – November 2025) RDS Blue/Green Deployments now supports Aurora Global Database for safer, simpler, and faster updates.
  • Blue/Green Deployments for Aurora Global Database creates a staging (green) environment that mirrors the production (blue) Aurora Global Database, including primary and all secondary regions.
  • Eliminates complex cross-Region orchestration and manual endpoint coordination that was previously required for self-managed multi-Region blue/green deployments.
  • Switchover safely using built-in switchover guardrails with downtime typically under one minute for global configurations.
  • Available for Aurora MySQL and Aurora PostgreSQL Global Database configurations.

RDS Blue/Green Deployments Limitations

  • Blue/Green Deployments are supported only for RDS for MariaDB, RDS for MySQL, and RDS for PostgreSQL (not supported for RDS for Oracle or RDS for SQL Server).
  • Blue/Green Deployments don’t support managing master user passwords with AWS Secrets Manager.
  • If dedicated log volume (DLV) is enabled on the blue database, it must be enabled on all DB instances, including read replicas.
  • During switchover, zero-ETL integrations with Amazon Redshift must be deleted first, then recreated after switchover.
  • The Event Scheduler (event_scheduler parameter) must be disabled on the green environment when creating a deployment.
  • Cannot change an unencrypted DB instance into an encrypted one (or vice versa).
  • Cannot change a blue DB instance to a higher engine version than its corresponding green DB instance.
  • Not supported for:
    • Cascading read replicas
    • Cross-Region read replicas
    • CloudFormation
    • Multi-AZ DB cluster deployments (supported for Multi-AZ DB instance deployments)
  • After switchover, AWS DMS replication tasks can’t resume because the checkpoint from the blue environment is invalid in the green environment. You must recreate the DMS task.

RDS Blue/Green Deployments Best Practices

  • Thoroughly test resources in the green environment before switchover.
  • Monitor relevant CloudWatch metrics (DatabaseConnections, ReplicaLag) before switchover.
  • Schedule switchover during lowest traffic periods.
  • Ensure replica lag is close to zero before initiating switchover.
  • Ensure network and client DNS cache TTL is not set beyond five seconds.
  • Ensure data loading is complete before switchover (lazy loading/storage initialization).
  • For PostgreSQL with logical replication, run ANALYZE operation to refresh pg_statistics before switchover.
  • Reduce active connections to minimum necessary before switchover for faster completion.
  • Verify that the application does not override the default_transaction_read_only parameter at the session level (for PostgreSQL).

AWS Certification Exam Practice Questions

  • Questions are collected from Internet and the answers are marked as per my knowledge and understanding (which might differ with yours).
  • AWS services are updated everyday and both the answers and questions might be outdated soon, so research accordingly.
  • AWS exam questions are not updated to keep up the pace with AWS updates, so even if the underlying feature has changed the question might not be updated
  • Open to further feedback, discussion and correction.
  1. A company runs a critical production database on Amazon RDS for PostgreSQL with Multi-AZ deployment. They need to perform a major version upgrade with minimal downtime and no data loss. The application connects directly to the database endpoint. Which approach provides the LOWEST downtime for this upgrade?
    1. Create a read replica, promote it, and point the application to the new instance
    2. Use RDS Blue/Green Deployments to create a staging environment, test the upgrade, and switchover
    3. Take a snapshot, restore it with the new engine version, and update the application endpoint
    4. Perform an in-place major version upgrade during a maintenance window

    Answer: b. RDS Blue/Green Deployments create a staging environment with the upgraded version, keep it in sync via replication, and perform switchover with typically under 5 seconds downtime for single-Region configurations.

  2. A database administrator is planning to use Amazon RDS Blue/Green Deployments for a minor version upgrade on an RDS for PostgreSQL instance. Which type of replication does RDS use to keep the green environment in sync with the blue environment for this scenario?
    1. Logical replication
    2. Physical replication
    3. AWS Database Migration Service
    4. Snapshot-based synchronization

    Answer: b. Since November 2024, RDS Blue/Green Deployments for PostgreSQL minor version upgrades use physical replication by default. Logical replication is used when a major version upgrade is specified.

  3. A company wants to minimize application downtime during an RDS Blue/Green Deployment switchover. Their application uses connection pooling. Which TWO approaches reduce switchover downtime? (Select TWO)
    1. Use Amazon RDS Proxy with the blue/green deployment
    2. Increase the switchover timeout to maximum
    3. Use the AWS Advanced JDBC Driver with the blue/green deployment plugin
    4. Enable Multi-AZ on the green environment
    5. Increase the DNS TTL to 300 seconds

    Answer: a, c. RDS Proxy and the AWS Advanced JDBC Driver both detect topology changes during switchover and redirect connections without waiting for DNS propagation, reducing downtime. RDS Proxy provides sub-5-second recovery, while the JDBC Driver provides ~2-second recovery.

  4. A company uses Amazon RDS Blue/Green Deployments with RDS for MySQL. During the switchover, which actions does Amazon RDS perform? (Select THREE)
    1. Runs guardrail checks to verify both environments are ready
    2. Stops new write operations on the primary DB instance in both environments
    3. Creates a new snapshot of the blue environment
    4. Deletes the blue environment instances
    5. Waits for replication to catch up in the green environment
    6. Upgrades the engine version automatically

    Answer: a, b, e. During switchover, RDS runs guardrail checks, stops writes on both environments, drops connections, waits for replication to catch up, renames instances, and then allows connections and writes on the new production environment. The blue environment is NOT deleted – it is retained with -oldN suffix.

  5. Which of the following are limitations of Amazon RDS Blue/Green Deployments? (Select THREE)
    1. Not supported for RDS for Oracle
    2. Not supported for Multi-AZ DB instance deployments
    3. Not supported for cross-Region read replicas
    4. Cannot change an unencrypted DB instance to an encrypted one
    5. Not supported for RDS for PostgreSQL
    6. Not supported for Multi-AZ DB cluster deployments

    Answer: a, c, d. Blue/Green Deployments don’t support RDS for Oracle (or SQL Server), cross-Region read replicas, or changing encryption status. They DO support Multi-AZ DB instance deployments (not cluster deployments) and RDS for PostgreSQL.

  6. An organization uses Amazon Aurora Global Database for their multi-Region application. They need to perform an engine version upgrade. How can they use Blue/Green Deployments for this scenario?
    1. Blue/Green Deployments don’t support Aurora Global Database
    2. Create separate Blue/Green Deployments in each Region and coordinate switchover manually
    3. Use fully managed Blue/Green Deployments for Aurora Global Database which mirrors primary and all secondary regions
    4. Convert to single-Region Aurora, perform Blue/Green Deployment, then recreate Global Database

    Answer: c. Since November 2025, RDS Blue/Green Deployments supports Aurora Global Database. It creates a staging (green) environment that mirrors the production (blue) Aurora Global Database, including primary and all secondary regions, with built-in switchover guardrails.

References

AWS RDS Security

AWS RDS Security

  • AWS RDS Security provides multiple features
    • DB instance can be hosted in a VPC for the greatest possible network access control.
    • IAM policies can be used to assign permissions that determine who is allowed to manage RDS resources.
    • Security groups allow control of what IP addresses or EC2 instances can connect to the databases on a DB instance.
    • RDS supports encryption in transit using SSL/TLS connections
    • RDS supports encryption at rest to secure instances and snapshots at rest.
    • Network encryption and transparent data encryption (TDE) with Oracle DB instances
    • Authentication can be implemented using Password, Kerberos, and IAM database authentication.
    • Database Activity Streams provide near real-time monitoring and auditing of database activity.
    • RDS Proxy provides connection pooling with IAM authentication and Secrets Manager integration.

RDS IAM and Access Control

  • IAM can be used to control which RDS operations each individual user has permission to call.
  • IAM policies can grant or deny access to specific RDS resources based on conditions such as tags, IP addresses, or VPC.
  • Service-linked roles allow RDS to make calls to other AWS services on your behalf.

RDS Authentication Methods

  • RDS supports multiple authentication methods:
    • Password authentication – Traditional database username/password.
    • IAM database authentication – Token-based authentication using IAM credentials (MySQL, PostgreSQL, MariaDB).
    • Kerberos authentication – Single sign-on using Microsoft Active Directory. Supported for Db2, PostgreSQL, MySQL, Oracle, and SQL Server.
  • Kerberos authentication integrates with AWS Managed Microsoft AD or on-premises AD via forest trust for centralized authentication.

RDS Encryption at Rest

  • RDS encrypted instances use the industry-standard AES-256 encryption algorithm to encrypt data on the server that hosts the RDS instance.
  • RDS handles authentication of access and decryption of the data with a minimal impact on performance, and with no need to modify the database client applications
  • Data at Rest Encryption
    • can be enabled on RDS instances to encrypt the underlying storage
    • encryption keys are managed by KMS
    • can be enabled only during instance creation
    • once enabled, the encryption keys cannot be changed
    • if the key is lost, the DB can only be restored from the backup
    • supports both AWS managed keys and customer managed keys (CMKs)
    • supports multi-Region KMS keys for cross-region snapshot copy and disaster recovery scenarios
  • Once encryption is enabled for an RDS instance,
    • logs are encrypted
    • snapshots are encrypted
    • automated backups are encrypted
    • read replicas are encrypted
  • Encrypted snapshots can be copied to another region by specifying a KMS key valid in the destination AWS Region. It can be a Region-specific KMS key, or a multi-Region key.
  • Cross-Region and Cross-Account Snapshot Copy (Sep 2025) – RDS now supports copying snapshots across Regions and accounts directly in a single step, without performing it sequentially as two separate copies.
  • RDS DB Snapshot considerations
    • DB snapshot encrypted using a KMS encryption key can be copied
    • Copying an encrypted DB snapshot results in an encrypted copy of the DB snapshot
    • When copying, the DB snapshot can either be encrypted with the same KMS encryption key as the original DB snapshot, or a different KMS encryption key to encrypt the copy of the DB snapshot.
    • An unencrypted DB snapshot can be copied to an encrypted snapshot, to add encryption to a previously unencrypted DB instance.
    • Encrypted snapshot can be restored only to an encrypted DB instance
    • If a KMS encryption key is specified when restoring from an unencrypted DB cluster snapshot, the restored DB cluster is encrypted using the specified KMS encryption key
    • Copying an encrypted snapshot shared from another AWS account requires access to the KMS encryption key used to encrypt the DB snapshot.
  • Transparent Data Encryption (TDE)
    • Automatically encrypts the data before it is written to the underlying storage device and decrypts when it is read from the storage device
    • is supported by Oracle and SQL Server
      • Oracle requires key storage outside of the KMS and integrates with CloudHSM for this
      • SQL Server requires a key but is managed by RDS

RDS Encryption in Transit – SSL/TLS

  • Encrypt connections using SSL/TLS for data in transit between the applications and the DB instance
  • RDS creates an SSL certificate and installs the certificate on the DB instance when RDS provisions the instance.
  • SSL certificates are signed by a certificate authority. SSL certificate includes the DB instance endpoint as the Common Name (CN) for the SSL certificate to guard against spoofing attacks
  • While SSL offers security benefits, be aware that SSL/TLS encryption is a compute-intensive operation and will increase the latency of the database connection.
  • For encrypted and unencrypted DB instances, data that is in transit between the source and the read replicas is encrypted, even when replicating across AWS Regions.
  • Certificate Authority (CA) Updates
    • The older rds-ca-2019 certificates expired in August 2024.
    • AWS introduced new CA certificates in December 2022:
      • rds-ca-rsa2048-g1 – RSA 2048-bit key, valid for 40 years (default for new instances since January 2024)
      • rds-ca-rsa4096-g1 – RSA 4096-bit key, valid for 100 years
      • rds-ca-ecc384-g1 – ECC 384-bit key, valid for 100 years
    • Using the new CA certificates, Amazon RDS manages automatic rotation of the DB server certificate before it expires.
    • New DB instances created after January 26, 2024 use rds-ca-rsa2048-g1 by default.
  • RDS supports enforcing SSL/TLS connections using parameter groups (e.g., rds.force_ssl = 1 for PostgreSQL, require_secure_transport = ON for MySQL).

IAM Database Authentication

  • IAM database authentication works with MySQL, PostgreSQL, and MariaDB.
  • IAM database authentication prevents the need to store static user credentials in the database because authentication is managed externally using IAM.
  • Authorization still happens within RDS (not IAM).
  • IAM database authentication does not require a password but needs an authentication token
  • An authentication token is a unique string of characters that RDS generates on request.
  • Authentication tokens are generated using AWS Signature Version 4.
  • Each Authentication token has a lifetime of 15 minutes
  • IAM database authentication provides the following benefits:
    • Network traffic to and from the database is encrypted using SSL/TLS.
    • Helps centrally manage access to the database resources, instead of managing access individually on each DB instance.
    • Enables using IAM Roles to access the database instead of a password, for greater security.
  • Enhanced Observability (Feb 2025) – RDS IAM DB Authentication now provides metrics and logs for improved troubleshooting:
    • CloudWatch metrics for IAM DB Auth connection attempts, successes, and failures.
    • IAM DB Auth error logs can be exported to CloudWatch Logs for investigation and resolution of authentication issues.

RDS Proxy Security

  • RDS Proxy is a fully managed, highly available database proxy that makes applications more scalable, resilient, and secure.
  • RDS Proxy sits between the application and the database, pooling and sharing established database connections.
  • Security features of RDS Proxy:
    • IAM Authentication – Enforces IAM authentication for client-to-proxy connections, eliminating the need for database credentials in application code.
    • Secrets Manager Integration – Proxy retrieves database credentials from AWS Secrets Manager, and you never need to expose credentials to your application.
    • TLS/SSL Enforcement – Supports encrypted connections between client and proxy, and between proxy and database.
    • VPC Security – RDS Proxy runs within your VPC and can be restricted using security groups.
  • End-to-End IAM Authentication (Sep 2025) – RDS Proxy now supports end-to-end IAM authentication where both client-to-proxy and proxy-to-database connections use IAM authentication, providing a fully passwordless database access solution.
  • RDS Proxy automatically handles failover, routing requests to the new primary instance without disrupting application connections.

Database Activity Streams

  • Database Activity Streams provide a near real-time stream of database activity for monitoring and auditing.
  • Supported for RDS for Oracle and RDS for SQL Server (also Aurora PostgreSQL and Aurora MySQL).
  • How it works:
    • RDS pushes database activity events to an Amazon Kinesis Data Stream in near real time.
    • The Kinesis stream is created automatically when enabling the feature.
    • From Kinesis, configure services like Amazon Data Firehose and Lambda to consume, store, and analyze the data.
  • Key benefits:
    • Separation of Duties – DBAs cannot access or modify the activity stream; encryption is managed via KMS keys controlled by security teams.
    • Compliance – Helps meet regulatory and compliance requirements for database auditing (SOX, PCI, HIPAA).
    • Integration – Works with partner security tools like IBM Guardium, Imperva, and McAfee for automated alerting.
  • Operates in asynchronous mode – database activity is recorded without impacting database performance (with a small delay).
  • Use of Database Activity Streams is free; you pay only for the underlying Kinesis data stream.

RDS Security Groups

  • Security groups control the access that traffic has in and out of a DB instance
  • VPC security groups act like a firewall controlling network access to your DB instance.
  • VPC security groups can be configured and associated with the DB instance to allow access from an IP address range, port, or EC2 security group
  • Database security groups default to a “deny all” access mode and customers must specifically authorize network ingress.
  • RDS supports dual-stack mode (IPv4 and IPv6) for DB instances in VPCs, including publicly accessible databases (Oct 2025 expansion).

RDS Secrets Manager Integration

  • RDS supports AWS Secrets Manager to manage and automatically rotate database credentials.
  • Native RDS Integration with Secrets Manager (2023+)
    • RDS offers built-in integration where Amazon RDS manages the master database credentials in Secrets Manager automatically.
    • When enabled, RDS generates the password, stores it as an encrypted managed secret, and rotates it automatically on a configurable schedule.
    • You never see or manage the master password directly.
    • Can be enabled during instance creation or later by modifying the instance.
    • The managed secret is encrypted with a KMS key you own and control.
  • Custom Secrets Manager rotation (for non-master credentials):
    • Uses a Lambda function to rotate credentials.
    • Built-in rotation templates for MySQL, PostgreSQL, MariaDB, Oracle, SQL Server, and Db2.
    • Supports single-user and multi-user rotation strategies.
  • Secrets Manager benefits:
    • Rotate secrets safely without disrupting applications.
    • Manage secrets centrally with fine-grained IAM policies.
    • Encrypt secrets with KMS keys you own and control.
    • Audit access via CloudTrail integration.
    • Pay as you go – per secret stored and API calls made.

Master User Account Privileges

  • When you create a new DB instance, the default master user that is used gets certain privileges for that DB instance
  • Subsequently, other users with permissions can be created.
  • Master user credentials can now be managed by AWS Secrets Manager for improved security (no direct password management).

Event Notification

  • Event notifications can be configured for important events that occur on the DB instance
  • Notifications of a variety of important events that can occur on the RDS instance, such as whether the instance was shut down, a backup was started, a failover occurred, the security group was changed, or your storage space is low can be received
  • RDS sends event notifications via Amazon SNS, and can trigger Lambda functions or other automated responses.

RDS Encrypted DB Instances Limitations

  • RDS Encryption can be enabled only during the creation of an RDS DB instance, not after the DB instance is created.
  • DB instances that are encrypted can’t be modified to disable encryption.
  • Encrypted snapshot of an unencrypted DB instance cannot be created.
  • An unencrypted backup or snapshot can’t be restored to an encrypted DB instance.
  • An unencrypted DB instance or an unencrypted read replica of an encrypted DB instance can’t have an encrypted read replica.
  • DB snapshot of an encrypted DB instance must be encrypted using the same KMS key as the DB instance.
  • Encrypted read replicas must be encrypted with the same KMS key as the source DB instance when both are in the same AWS Region.
  • For encrypting an unencrypted RDS database, the following approaches can be used:
    • Using Snapshots (requires downtime):
      • Create a DB snapshot of the DB instance, which would be unencrypted.
      • Copy the unencrypted DB snapshot to an encrypted snapshot.
      • Restore a DB instance from the encrypted snapshot, which would be an encrypted DB instance.
    • Using AWS DMS (minimal to no downtime): Use AWS Database Migration Service (AWS DMS) to migrate and continuously replicate the data so that the cutover to the new, encrypted database is seamless.

RDS API with Interface Endpoints (AWS PrivateLink)

  • AWS PrivateLink enables you to privately access RDS API operations without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection.
  • DB instances in the VPC don’t need public IP addresses to communicate with RDS API endpoints to launch, modify, or terminate DB instances.
  • DB instances also don’t need public IP addresses to use any of the available RDS API operations.
  • Traffic between the VPC and RDS doesn’t leave the Amazon network.

AWS Certification Exam Practice Questions

  • Questions are collected from Internet and the answers are marked as per my knowledge and understanding (which might differ with yours).
  • AWS services are updated everyday and both the answers and questions might be outdated soon, so research accordingly.
  • AWS exam questions are not updated to keep up the pace with AWS updates, so even if the underlying feature has changed the question might not be updated
  • Open to further feedback, discussion and correction.
  1. Can I encrypt connections between my application and my DB Instance using SSL?
    1. No
    2. Yes
    3. Only in VPC
    4. Only in certain regions
  2. Which of these configuration or deployment practices is a security risk for RDS?
    1. Storing SQL function code in plaintext
    2. Non-Multi-AZ RDS instance
    3. Having RDS and EC2 instances exist in the same subnet
    4. RDS in a public subnet (Making RDS accessible to the public internet in a public subnet poses a security risk, by making your database directly addressable and spammable. DB instances deployed within a VPC can be configured to be accessible from the Internet or from EC2 instances outside the VPC. If a VPC security group specifies a port access such as TCP port 22, you would not be able to access the DB instance because the firewall for the DB instance provides access only via the IP addresses specified by the DB security groups the instance is a member of and the port defined when the DB instance was created. Refer link)
  3. A company needs to encrypt an existing unencrypted RDS database with minimal downtime. Which approach should they use?
    1. Enable encryption on the existing instance via the console
    2. Create an unencrypted snapshot, copy it as encrypted, and restore
    3. Use AWS DMS to migrate data to a new encrypted RDS instance (AWS DMS enables continuous replication to the encrypted target, minimizing downtime during cutover. The snapshot approach requires downtime during restore.)
    4. Modify the DB instance to add a KMS key
  4. A security team requires near real-time auditing of all database activity on an RDS Oracle instance, with separation of duties ensuring DBAs cannot tamper with audit records. Which feature should they use?
    1. CloudTrail data events for RDS
    2. RDS Enhanced Monitoring
    3. Database Activity Streams (Database Activity Streams push activity to a Kinesis stream encrypted with a KMS key controlled by security teams, ensuring DBAs cannot access or modify audit records.)
    4. RDS Performance Insights
  5. Which authentication methods does Amazon RDS support? (Choose THREE)
    1. Password authentication
    2. IAM database authentication
    3. Kerberos authentication with Active Directory
    4. SAML-based authentication
    5. OAuth 2.0 authentication
  6. A company wants to eliminate database passwords entirely for their serverless application connecting to RDS PostgreSQL through RDS Proxy. Which approach achieves this?
    1. Store credentials in environment variables
    2. Use Secrets Manager integration only
    3. Configure RDS Proxy with end-to-end IAM authentication (Since September 2025, RDS Proxy supports end-to-end IAM authentication where both client-to-proxy and proxy-to-database connections use IAM, providing a fully passwordless solution.)
    4. Use Lambda authorizers with RDS
  7. An organization needs to automatically manage and rotate their RDS master user password without using Lambda functions. Which solution requires the least operational effort?
    1. Create a Secrets Manager secret and configure Lambda rotation
    2. Enable the native RDS integration with Secrets Manager to manage the master user password (RDS natively manages the master password in Secrets Manager including automatic rotation, without requiring custom Lambda functions.)
    3. Use IAM database authentication instead of passwords
    4. Store the password in Systems Manager Parameter Store with rotation
  8. After the rds-ca-2019 certificate expired in August 2024, which certificate authority should new RDS instances use by default?
    1. rds-ca-2019
    2. rds-ca-rsa2048-g1 (New instances created after January 26, 2024 use rds-ca-rsa2048-g1 by default, which is valid for 40 years.)
    3. rds-ca-rsa4096-g1
    4. rds-ca-ecc384-g1

📖 Related: AWS RDS Backup, Snapshots & Restore – Complete Guide

References