Search for a command to run...
Here is my approach to configuring lambda's Provisioned Concurrency in multi environments (QA, test, etc.) with AWS SAM
Hi there 👋
I'm an Indonesian who loves coffee and dogs!! Also, code sometimes.
Currently studying at Kyoto College of Graduate Studies for Informatics. 🏫
Work as Full-Stack Engineer
No comments yet. Be the first to comment.
Or: Why we stopped trying to build software for everyone, and built Lensiro just for optical shops. If you've ever walked into an optical shop in Indonesia to buy a pair of glasses, you probably didn'
How event-sourced ledger architecture eliminated stock discrepancies in our optical retail app
ホコリをかぶった12台のMacBookから、今では本番LLMトラフィックの4分の1を担う200ノードのAppleシリコンファームへ
From twelve dusty MacBooks to a 200‑node Apple‑silicon farm that now powers our live LLM traffic
Discover how integrating GitHub with Snowflake empowers seamless version control and collaborative workflows for managing your UDFs and procedures.
Last week, I worked on a project that used Lambda as an API to run an algorithm triggered by multiple services in my company. I implemented it with AWS Serverless Application Model (AWS SAM), wrote the template, and set up CI/CD with no problem, except for one, the first request was slow.
A Lambda function instance created at startup will disappear after a certain period. Therefore, if Lambda is executed after a certain period, there is a good chance that the function instance has disappeared and is re-executed from its creation. This is what we call Cold Start.
Source: https://www.slideshare.net/AmazonWebServices/become-a-serverless-black-belt-optimizing-your-serverless-applications-aws-online-tech-talks/14
If Lambda is re-executed before the function instance is lost, the container is reused, as shown in the following slide, and execution without startup time (warm start) becomes possible. If Lambda functions are executed frequently, the container is more likely to be reused, and the probability of a cold start will decrease.
My goal is to prevent cold start so that customers using our services will have a good user experience. I could implement an event that fires lambda every minute, but In addition to the time-consuming setup process, There is no fixed amount of time before a function instance goes into an unconscious state. Therefore, periodic execution is only a method to reduce the probability of a cold start and cannot guarantee a warm start.
Another way, which guarantees a warm start and can be done with a bit of setup, is Provisioned Concurrency.
In my case, I use AWS SAM Template to Implement it. If you prefer to configure it on the console, I recommend reading AWS Official's blog post about how to do it.
It is as simple as adding these three lines to the template.yaml. I will pretend we all know about SAM Template and some basic Code as Infrastructure in AWS.
....
Resources:
MyFunction:
Type: AWS::Serverless::Function
Properties:
.....
AutoPublishAlias: live
ProvisionedConcurrencyConfig:
ProvisionedConcurrentExecutions: 1
.....
And if you have multiple environments (QA, test, etc.) and want to apply it only on production to save cost. Here is my approach to doing that.
...
Parameters:
Environment:
Type: String
Description: 'Enter Env Name'
Conditions:
ConfigureConcurrency: !Equals
- !Ref Environment
- prd
Resources:
MyFunction:
Type: AWS::Serverless::Function
Properties:
.....
AutoPublishAlias: live
ProvisionedConcurrencyConfig:
!If
- ConfigureConcurrency
- ProvisionedConcurrentExecutions: 1
- !Ref "AWS::NoValue"
.....
It will create an alias but will not set provisioned concurrency in other environments except prd, which is an alias for production.
DeploymentPreference (AllAtOnce, Canary10Percent5Minutes, Linear10PercentEvery1Minute etc). as of my research, I couldn't find if it causes downtime or not.arn:aws:lambda:REGION:function:FUNTION_NAME:ALIAS_NAME)
As of my finding, here is a way to lower the price:
Here, I have summarized my understanding. I hope it will be helpful to those who may have difficulty setting it up in AWS SAM template or making it work in multiple environments.
Cheers!