Skip to content
Branch: master
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
.gitignore Initial commit Jan 21, 2020 Initial commit Jan 21, 2020
handler.js Initial commit Jan 21, 2020
package-lock.json Initial commit Jan 21, 2020
package.json Initial commit Jan 21, 2020
serverless.yml Initial commit Jan 21, 2020

Lambda in VPC -- VPC endpoint example

This Serverless service shows how to configure a Lambda function in a VPC to use AWS services by using a VPC endpoint. It will configure all necessary VPC resources and deploy a Lambda function in the VPC. This example uses Amazon SNS, but it will work with any of the services that use support VPC endpoints. The VPC will demonstrate that the VPC endpoint works by using SNS to send an SMS message.


To use this example, run the following steps. You must have the Serverless Framework installed.

  1. Create a new service from this repository and install the dependencies.

    serverless create --template-url --path vpc-endpoint
    cd vpc-endpoint
    npm i
  2. Update the SMS_NUMBER environment variable in the serverless.yml file to use the SMS number where you want to send a message.

  3. Deploy your service.

    In your terminal, run:

    serverless deploy

    This will take a few minutes to provision the VPC resources.

  4. Invoke your function to send the SMS message.

    In your terminal, run:

    serverless invoke -f sendText

    You should receive an SMS message to the number provided.


The serverless.yml file is creating the following resources:

  • A VPC;
  • Two private subnets. The Lambda functions will use the private subnets.
  • A Security Group to give to our Lambda function.
  • A Security Group for our VPC Endpoint. This security group will allow TCP ingress on port 443 (HTTPS) from our Lambda's security group.
  • A VPC endpoint in our private subnets that is routing to SNS.

The general architecture is as follows:

Lambda in VPC with VPC Endpoint

Our Lambda functions are (functionally) in the private subnets of our VPC. The SNS requests are routed through the configured VPC endpoints to the SNS service.

In our Lambda function configuration, we use the private subnet IDs and the security group ID to configure our Lambda function to be in a VPC.

Both the VPC resources and the Lambda function are combined in this example stack for ease of demonstration. For production use cases, I would recommend splitting the VPC configuration into a different CloudFormation stack altogether. You could refer to the exported values from that stack in your Serverless service.

You can’t perform that action at this time.