This post is originally published on our blog.
This guy has asked the serverless forum for a solution to implement it. That is why I wanted to write this post to describe how to toggle VPC configuration per stage. I hope it can help you and save your time :)
If you are working on the Serverless framework to build your application on AWS. You possibly wanted to run your Lambda functions under your private Vpc to protect your functions and hide it from the world. But sometimes, you might want to run your function without VPC such as for non-production environments.
Basically, we can disable Vpc configuration for Lambda function by either:
- Omit the vpc property in the provider configuration.
- Or you can set both securityGroupIds and subnetIds as an empty array.
Based on the above logic, we can define a property in the custom prop as below:
With the above configurations, deploy to the dev stage will not add your lambda functions to a Vpc, but deploy to the prod stage will add your lambda functions to your desired Vpc.
You can refer to some plugins I added in the serverless.yml file, it can be used to create your Vpc automatically or discover from the AWS account.
If you want to have a try, you can check out our repo on Github.
Should you run into issues while practicing the steps outlined in this article, I encourage you to reach out to me. You can get in touch with me through my Twitter handle @hoangleitvn
My name is Hoang, I am the Co-founder and CTO of InnomizeTech. My title is CTO but I am a full-stack developer and software architect, passionate about Cloud Computing, Serverless, DevOps, Machine Learning, and IoT.
If you are looking for developers, offshore team, or need consulting about the AWS cloud, Serverless architecture, and so on, then hire us, we can help you!
Thank you for reading!