Different environments for Lambda Functions

Question

I currently have a few lambda functions that interact with an application inside Elastic Beanstalk. These functions use environment variables that are specific to Staging env. Since I am now going to start moving some things to production, I wanted to know good and practical ways of handling these functions, that is:

Should I copy this function into another function and set different env variables?
Is there a way to have different environments in one unique function?
Should I use runtime variables?

Thanks in advance,

Mark B · Accepted Answer · 2020-08-20 12:45:15Z

1

Should I copy this function into another function and set different env variables?

Yes, but you should really be doing this via something like CloudFormation or Terraform instead of copying it manually.

Is there a way to have different environments in one unique function?

No

answered Aug 20, 2020 at 12:45

Mark B

203k27 gold badges339 silver badges332 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Vitor Carvalho Over a year ago

Thank you! I am using terraform :)

Mark B Over a year ago

@VitorCarvalho if using Terraform I suggest using workspaces, so you deploy the function once to your dev workspace, and then a second time to your prod workspace, without having to duplicate any code or configuration.

Collectives™ on Stack Overflow

Different environments for Lambda Functions

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related