Book Image

Machine Learning Engineering on AWS

By : Joshua Arvin Lat
Book Image

Machine Learning Engineering on AWS

By: Joshua Arvin Lat

Overview of this book

There is a growing need for professionals with experience in working on machine learning (ML) engineering requirements as well as those with knowledge of automating complex MLOps pipelines in the cloud. This book explores a variety of AWS services, such as Amazon Elastic Kubernetes Service, AWS Glue, AWS Lambda, Amazon Redshift, and AWS Lake Formation, which ML practitioners can leverage to meet various data engineering and ML engineering requirements in production. This machine learning book covers the essential concepts as well as step-by-step instructions that are designed to help you get a solid understanding of how to manage and secure ML workloads in the cloud. As you progress through the chapters, you’ll discover how to use several container and serverless solutions when training and deploying TensorFlow and PyTorch deep learning models on AWS. You’ll also delve into proven cost optimization techniques as well as data privacy and model privacy preservation strategies in detail as you explore best practices when using each AWS. By the end of this AWS book, you'll be able to build, scale, and secure your own ML systems and pipelines, which will give you the experience and confidence needed to architect custom solutions using a variety of AWS services for ML engineering requirements.
Table of Contents (19 chapters)
1
Part 1: Getting Started with Machine Learning Engineering on AWS
5
Part 2:Solving Data Engineering and Analysis Requirements
8
Part 3: Diving Deeper with Relevant Model Training and Deployment Solutions
11
Part 4:Securing, Monitoring, and Managing Machine Learning Systems and Environments
14
Part 5:Designing and Building End-to-end MLOps Pipelines

Deploying models from SageMaker Model Registry

There are many possible next steps available after an ML model has been registered to a model registry. In this section, we will focus on deploying the first registered ML model (pre-trained K-Nearest Neighbor model) manually to a new inference endpoint. After the first registered ML model has been deployed, we will proceed with deploying the second registered model (pre-trained Linear Learner model) in the same endpoint where the first ML model has been deployed, similar to what’s shown in the following diagram:

Figure 8.7 – Deploying models from the model registry

Here, we can see that we can directly replace the deployed ML model inside a running ML inference endpoint without creating a new separate inference endpoint. This means that we do not need to worry about changing the “target infrastructure server” in our setup since the model replacement operation is happening behind the...