Environment Variables

Environment Variables Overview

Environment Variables is a building block you will reach for often in AWS Lambda. It keeps related logic together and makes your intent obvious to reviewers and future maintainers.

When you learn environment variables properly, you avoid the guesswork that leads to bugs and rework. The example below shows the shape you will use in most real AWS Lambda projects.

import { SSMClient, GetParameterCommand } from '@aws-sdk/client-ssm';

const ssm = new SSMClient({});
let cachedApiKey;

export const handler = async () => {
  if (!cachedApiKey) {
    const { Parameter } = await ssm.send(new GetParameterCommand({
      Name: '/app/api-key',
      WithDecryption: true,
    }));
    cachedApiKey = Parameter.Value;
  }

  return { hasKey: Boolean(cachedApiKey) };
};

Configuration is fetched once and cached in module scope so warm invocations skip the extra call.

Environment Variables Example

// handler.mjs
export const handler = async (event, context) => {
  // 1. read input from the event
  // 2. do the work
  // 3. return a response (or throw on error)
};

• Start from a minimal Environment Variables example and grow it only as needed.
• Keep configuration explicit so Environment Variables behaves the same in every environment.
• Name things clearly so teammates understand your Environment Variables at a glance.
• Add tests around Environment Variables early to lock in expected behaviour.

AWS Lambda Cheatsheet

Handy reference for working with environment variables in AWS Lambda and Node.js.

How Environment Variables Works in AWS Lambda

Environment Variables runs inside the managed Lambda execution environment. AWS provisions a micro-VM, loads your Node.js code, runs any module-scope initialisation once, and then invokes your handler for each event.

Configuration is fetched once and cached in module scope so warm invocations skip the extra call.

• Handlers should be small and do one job well.
• Initialise SDK clients and config outside the handler to reuse them on warm starts.
• Return quickly and let event sources handle retries where possible.
• Emit structured logs so CloudWatch and X-Ray can correlate activity.

Practical Guidance for Environment Variables

On real projects, environment variables works best when it is observable, secure, and cheap to run. Grant least-privilege IAM, validate every input, and keep the deployment package small.

Common Mistakes

• Skipping error handling and edge cases when wiring up environment variables.
• Leaving environment variables untested, so regressions slip into production.
• Over-engineering environment variables before you actually need the extra flexibility.
• Ignoring documentation, which makes environment variables hard for the next developer to change.

Key Takeaways

• Environment Variables is a core part of working effectively with AWS Lambda.
• Start small and keep environment variables focused on a single responsibility.
• Apply consistent patterns so environment variables scales across your project.
• Test and document environment variables to keep it maintainable over time.