If you want, your Lambda function can have different configurations or settings when it moves from different life cycle states like from development to test to production. For example, development, test, and production environments, which contain databases and functions needed to connect to the database. All of these have different environments and so they have different connection information. In this case, you can create the environment variables, reference it for the database name, DB connection information, and in which stage like development, test, and production that function is executing in without any code change. Using AWS console, you can modify and configure environment variables.
- Here, you are configuring the variable ...
