Next
I acknowledge that AWS CloudFormation might create IAM resources with custom names
under the Capabilities section, and click “Create.”mvn clean install.
serverless.yml
from https://github.com/thundra-io/thundra-lambda-warmup/blob/master/serverless.ymlpackage
section with the downloaded thundra-lambda-warmup.jar
path on your local environment.serverless.yml
:thundra-lambda-warmup artifact
will be deployed.thundra-lambda-warmup
artifact will be deployed.thundra-lambda-warmup
artifact as a Lambda function by sls deploy
.thundra_lambda_warmup_function
environment variable and separated by a comma. This environment variable is then put into the thundra-lambda-warmup
Lambda function. For example, the environment variable key (name) is thundra_lambda_warmup_function
and value is my-func-1,my-func-2,my-func-3
.thundra_lambda_warmup_warmupAware
environment variable (the value is true
). Note that this environment variable is put into the Lambda function that should be warmed up (NOT into the thundra-lambda-warmup
Lambda function).eight
, which is the number of warmed up container counts needing to be kept up. This factor can be configured with the thundra_lambda_warmup_invocationCount
environment variable. There are a few points you should be aware of:eight
, there is no guarantee that there are exactly eight containers up; there may be more or less. But in practice, and based on previous tests we have run, generally eight containers will be up.thundra-lambda-warmup
Lambda function can dramatically reduce your cold starts. However, keep in mind that it is not a complete fix, and there is no guarantee that there won't be any cold starts.public class HandlerClass : LambdaRequestHandler<GetAlbumRequest, Album>
then you must extend “ISelfAware
” in the GetAlbumRequest class.IsEmpty
method. The same goes for dealing with Stream handlers.thundra_agent_lambda_jvm_optimizeForFastStartup
to true. More detailed information can be found here.