Environment Variables and Configuration
Discover how to use environment variables to configure your Lambda functions without changing code, promoting reusability and operational flexibility.
Environment Variables and Configuration is a free Serverless AWS Lambda Development lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Serverless AWS Lambda Development learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
What are Env Variables?
When building applications, you often need to change settings without altering your core code. This is where environment variables come in!
They are key-value pairs that your application can access at runtime. Think of them as sticky notes attached to your program, telling it how to behave.
Why Use Env Variables?
Environment variables are crucial for flexible and scalable serverless applications:
- No Code Changes: Update settings like API endpoints or feature flags without modifying and redeploying your function code.
- Environment-Specific Config: Easily switch configurations between development, testing, and production environments.
- Reusability: The same Lambda function code can serve different purposes based on its configured variables.
Lambda's Environment
When your Lambda function is invoked, AWS injects these environment variables into its execution environment. Your function's code can then read these variables using standard language features.
This keeps your application logic separate from its operational configuration.
Setting Env Vars in AWS
You can configure environment variables directly in the AWS Management Console when creating or updating a Lambda function:
- Go to your function's configuration tab.
- Scroll down to the 'Environment variables' section.
- Add new key-value pairs (e.g.,
LOG_LEVEL:INFO).
These settings are then available to your function's runtime.
Reading Env Variables (Java)
Let's see how a simple Java program can read an environment variable. When deployed to Lambda, your function code would access them similarly.
Try running this example after setting an APP_NAME environment variable on your system!
public class Main {
public static void main(String[] args) {
String appName = System.getenv("APP_NAME");
if (appName == null || appName.isEmpty()) {
appName = "MyDefaultApp";
}
System.out.println("Running application: " + appName);
System.out.println("To change, set APP_NAME environment variable.");
}
}Practical Use Cases
Environment variables are ideal for many configuration needs:
- API Endpoints: Specify different URLs for external services (e.g., a payment gateway's sandbox vs. production API).
- Feature Flags: Enable or disable specific features based on the environment.
- Resource Identifiers: Store names or ARNs of other AWS resources like S3 buckets, DynamoDB tables, or SQS queues.
Not for Secrets!
Important Security Note: While convenient, environment variables are generally not suitable for sensitive data like database passwords, API keys, or private certificates.
They are not encrypted at rest by default and can be viewed by anyone with console access. For secrets, always use dedicated services like AWS Secrets Manager or AWS Systems Manager Parameter Store (with secure strings).
Updating & Deployment
One of the biggest advantages is operational flexibility. When you update environment variables for a Lambda function:
- The changes take effect immediately for new invocations.
- You do not need to re-deploy your function's code.
This allows for quick configuration adjustments without downtime or complex deployment pipelines.
Quick Check on Env Vars
Consider a Lambda function that needs to connect to different databases in its 'development' and 'production' environments.
Recap: Environment Variables
You've learned that environment variables are powerful key-value pairs for configuring Lambda functions:
- They promote reusability and operational flexibility by externalizing settings.
- You can change them without redeploying code, enabling dynamic configuration.
- Always use dedicated services like AWS Secrets Manager for sensitive information.
Mastering environment variables is a fundamental step towards building adaptable and efficient serverless applications.
Frequently asked questions
Is the “Environment Variables and Configuration” lesson free?
Yes — the full text of “Environment Variables and Configuration” is free to read here on the web, and the Serverless AWS Lambda Development course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Serverless AWS Lambda Development course, upgrade to CoddyKit PRO.
What will I learn in “Environment Variables and Configuration”?
Discover how to use environment variables to configure your Lambda functions without changing code, promoting reusability and operational flexibility. You practise Serverless AWS Lambda Development with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Serverless AWS Lambda Development?
No prior experience is required. Serverless AWS Lambda Development on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Environment Variables and Configuration” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Serverless AWS Lambda Development lesson?
Yes. Every Serverless AWS Lambda Development lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Understanding Lambda Runtime & Layers
- Environment Variables and Configuration
- IAM Roles for Lambda Security
- Versioning and Aliases for Safe Releases