Deploying Pytorch models for free with Docker, AWS ECR and AWS Lambda

Original Source Here

You can find all the code in the Github repo.

Step 0: requirements

For this tutorial you will need:

How Docker works (from:

Step 1: initialise the project with SAM CLI

Once you have everything set up, you can start a new project from a template:

sam init


  1. AWS quick-start templates
  2. Image (artifact is an image uploaded to an ECR image repository)
  3. amazon/python3.8-base
  4. PyTorch Machine Learning Inference API

Then cd into the project you just created.

Step 2: build the model

For illustration purposes, I have created and trained a model for machine translation (French to English). You can find the code in the Github repo under /app/ I won’t go into the details as it is not the purpose of this post.

Next, we need to create the handler, this is the function that will process requests. It needs to have the following:

  1. pre-processing the data (e.g. one-hot encoding, converting to tensor, etc)
  2. loading the trained model
  3. making the prediction (model.forward())
  4. processing the output (e.g. one-hot tensor to text)
  5. returning the output as a JSON object

Step 3: uploading the Docker image and deploying the lambda function

The Docker image will be hosted in a repository in AWS ECR. When the lambda function gets triggered (i.e when a user sends a request) it will run the Docker image which will execute the handler with the data sent in the request.

To create an ECR repository run:

aws ecr create-repository --repository-name <REPOSITORY_NAME> --image-scanning-configuration scanOnPush=true --region <REGION>

Don’t forget to set:

  • <REPOSITORY_NAME> to any name you’d like (for me it’s lambda-pytorch)
  • <REGION> to an AWS region (e.g. us-east-2)

⚠️ all of your resources need to be in the same region

When prompted, copy the repositoryUri. This is the address of the repository you just created. You will need it in the next step to tell SAM where to upload the Docker image.

Now that the repository is created, you can build the docker image:

sam build

This will create a build.toml file in the .aws-sam folder.

⚠️ make sure to re-run the build command whenever you change your Dockerfile or the application code. Otherwise, you will deploy the older version.

Once it’s done you can run the deploy command to launch the whole deploy stack:

  1. upload the Docker image to your ECR image repository,
  2. create the lambda function,
  3. create the API Gateway that will receive the requests from the web and trigger the lambda function to process them.
sam deploy --guided --stack-name <STACK_NAME>

The cool thing with stacks is that once deployed, you can run the deploy command again ( sam deploy --guided) and it will check if the resources already exist. If it is the case, it will update them with the new ones. So everything is managed and optimized for you!

Step 4: test your Lambda function

To test your Lambda function, you first need to find the API URL (where to send the request).

Go to AWS management console and to Lambda function and click on your Lambda function. Scroll down to API endpoint. It should look something like this:

To send a request to the API, run the following command in your terminal:

curl --header "Content-Type: application/json" --request POST --data '{"sentence": "Les deux chiens marchent dans le parc."}' <API_URL>

Step 5: avoid the bill with lifecycle policy rules

ECR free tier only allows 500 MB-month, i.e if you host a Docker image bigger than 500 MB for a whole month, you will exceed the free tier threshold.

There is a chance that your image exceeds this 500 MB threshold. It is not a problem as long as you don’t leave your image for a whole month.

In order to avoid deleting your image manually (and messing up the whole stack automation) or even worse, forgetting to delete it 😱, I will show you how you can set up a lifecycle policy rule.

Lifecycle policy rules allow you to manage images in ECR by defining actions that should be applied automatically (e.g. cleaning up images based on an expiration period).

To set up a lifecycle policy rule:

  1. Go to AWS management console
  2. Go to Elastic Container Registry
  3. Click on your repository (the one that you created in step 2)
  4. On the left side menu, click Lifecycle Policy
  5. Click create rule
  6. Under Match criteria, set Since Image pushed and enter the expiration period you want (e.g 1 will automatically delete every image 24 hours after they’ve been uploaded)
  7. And then Save

Voila! your images will be automatically deleted once the expiration period is over. This way you won’t receive bad surprises.

🔑 If you are still afraid, you can check your consumption in Billing in the AWS Management Console.


I hope you liked this tutorial. If you have any questions please leave them in the comments.

Let me know if you would be interested in going further (unit testing, using Github actions to automatically test/build/deploy on push, building a fully-fledged web app running deep learning models).


Trending AI/ML Article Identified & Digested via Granola by Ramsey Elbasheer; a Machine-Driven RSS Bot

%d bloggers like this: