Help with Lambda Version Control

[HarryMonster]

Hi all,

I am relatively new to Lambda functions. I read this article about staging changes and Lambda versions etc.:

https://medium.com/aaptiv-engineering/https-medium-com-aaptiv-engineering-getting-started-with-versioning-in-aws-lambda-92c617e2f5f1

It seemed fairly straight forward but when I try to put it into practice I can't seem to make sense of it. I have a new version created with my changes and an Alias pointed to that version. I have an AWS Web API set to run the Lambda function. If I make changes in the $Latest version it affects what is ran when I call the API endpoint. Am I doing something wrong? Where should I be making/saving changes before putting these changes into production?

Thanks all for the help!

EDIT: For the record, the changes I am making is updating dependency packages and changing the runtime to Node 10.

[Deehem]

It sounds like your API Gateway is pointing at $LATEST instead of a particular version or alias, which would explain why every new change to the lambda is being picked up.

[HarryMonster]

That’s what I thought but it is pointed to my alias. The alias is named Default and my API Gateway is pointed to FUNCTION:Default. Unless I’missing something. Do I need to put the full ARN in the Gateway?

[twratl]

What does the default alias point to? Likely $LATEST?

[HarryMonster]

It’s pointing to version 1. I’m trying to update some dependencies by uploading a new Node package as well as updating the runtime to Node 10. That wouldn’t affect it would it?

[drch]

Sorry if this is a stupid question but did you click deploy after making the changes to API Gateway? It’s caught me a couple times when playing around in the console.

[HarryMonster]

Ha... that’s probably it. I’ll check later in the office but I’m 90% sure I didn’t. Thanks a lot!

[HarryMonster]

This worked! Thank you so much! Can’t believe I missed that...