Once upon a time I was the serverless guy at a startup company building lambda functions. My function went into production at 128mb of memory and a timeout of 3 seconds. Because of game had "live races" we would see big spikes in traffic at certain times of the day, and unfortunately I would also see big spikes in the number of errors in the CloudWatch metrics charts... My boss even opened the website during the high volume event and noticed requests to the lambda returning 400 error. In the cloudwatch logs I could norrow down the logs to just the high volume time and see many timeout errors happening during this period. Needless to say, this is not a good look, and you don't want it to happen to you (especially you, future Jim)!
Changing Memory And Timeout Settings Like a Bitchass
Once you have created and deployed your lambda function it will be visible in the web AWS console. You can always go in and drag the slider / increment the timeout to edit the settings for you lambda function.
Change MemorySize And
The posts on this site are written and maintained by Jim Lynch. About Jim...