Create a Webhook with AWS Lambda

January 17, 2020

Create a simple webhook for your automation with AWS Lambda and Python.

The other day I was moving a friend’s static website over to Netlify. It’s a simple static Hugo site with only a handful of pages and images. What makes the site unique is the hundreds of large PDF files.

Initially, I looked into storing the PDF files in Git LFS. It’s a cool technology and both Netlify and GitHub support it. Unfortunately, I quickly hit the storage limit of my GitHub account. I didn’t feel like paying to increase it, just for this one site.

So, I rolled up a tidy Netlify/AWS hybrid solution. Netlify builds the static HTML files, while the PDFs reside in S3. CloudFront sits at the fore, using Netlify as the default origin, and an S3 origin for the content under /pdf.

This solved the large file problem. Cheap, durable storage of the PDFs in S3, with Netlify’s dead-simple CI/CD automation.

Yet, there is another problem. What if we update the site content files and Netlify does a deploy? How will CloudFront know there is new content? We need to somehow send an invalidation request to CloudFront after each Netlify deployment.

I decided to create a webhook using a few AWS tools.

AWS webhook recipe

Simply put, the webhook is a listener on my Application Load Balancer (ALB) that points to a Lambda function. For convenience, I have a lambda. subdomain pointed at the ALB. The ALB listens for that host and specific query strings. Then it forwards both of them to the Lambda function. The function then triggers a CloudFront invalidation.

IAM role for Lambda

Before creating the Lambda function, I created an IAM role with very basic permissions. The role only needs permission to create a CloudFront invalidation request.

    "Version": "2012-10-17",
    "Statement": [
            "Effect": "Allow",
            "Action": "cloudfront:CreateInvalidation",
            "Resource": "*"

Lambda function

Next, I created the Lambda function using Python. The function creates an invalidation request and returns a 200 HTTP status code to Netlify.


import boto3
import json
import time

def lambda_handler(event, context):
    client = boto3.client("cloudfront")

    distribution = event["queryStringParameters"]["dist"]
    request = client.create_invalidation(
            "Paths": {"Quantity": 1, "Items": ["/*"]},
            "CallerReference": str(time.time()),
    response = {
        "statusCode": 200,
        "statusDescription": "200 OK",
        "isBase64Encoded": False,
        "headers": {"Content-Type": "text/html"},
        "body": "<h1>Invalidation in progress.</h1>",
    return response

I wanted a function I could use with other distributions, so we tell Lambda to look for a query string parameter dist corresponding to a CloudFront distribution ID.

We invalidate all paths in the site with /*. This is fine for small sites. If your needs are more complex, you can use a Python list with multiple paths. CloudFront also needs a unique CallerReference so we just use the current time.

Finally, we send a JSON response back to the ALB with a 200 HTTP response code. Netlify requires webhooks to return an HTTP response code (other than 4xx or 5xx). Without an acceptable response code, the webhook becomes disabled.

I used the IAM role defined earlier for this function.

Application Load Balancer setup

In my ALB settings, I created a target group and pointed it at my Lambda.

ALB Target Group
ALB Target Group

Then, I created a listener. It watches for a path and a query string with a key of token, which is assigned a random value. The value is random to provide a little security.

Here’s an example of how the listener might look:

ALB Rule
ALB Rule


Now I can put together a tidy URL:

…and plop it into my Netlify deploy configuration.

When the deploy succeeds, Netlify sends a POST request to the URL. The load balancer triggers the Lambda function and CloudFront begins its invalidation.


Contact Form

Form submissions are sent to my email inbox. Besides reading your comment, I don't do anything with your information. Caveat: I log IPs to prevent spam.

Enter a valid email if you want a response.