ตัวแปรสภาพแวดล้อมและเลเยอร์

When building serverless applications, you often need to configure your Lambda functions. This includes settings that change between development, testing, and production environments.

Think about database connection strings, API endpoints, or feature flags. Hardcoding these values is a bad practice!

Environment variables are key-value pairs that you define for your Lambda function. Your function's code can then access these variables at runtime.

• They provide a simple way to change your function's behavior without modifying its code.
• Each function has its own set of environment variables.

You can set environment variables directly in the AWS Management Console when configuring your Lambda function. They can also be defined using Infrastructure as Code tools like AWS SAM or CloudFormation.

Important: While convenient, avoid storing sensitive information like database passwords directly in environment variables. Use AWS Secrets Manager for that!

In Python, you can access environment variables using the os module, specifically os.environ.get(). This method allows you to provide a default value if the variable isn't set.

Try running this example:

Using environment variables wisely can greatly improve your function's maintainability:

• Non-sensitive config: Use for API keys (for non-critical services), log levels, feature flags.
• Integration with Secrets Manager: For truly sensitive data (e.g., database credentials), store them in AWS Secrets Manager and retrieve them at runtime using your function's IAM role.
• Separate environments: Easily switch configs for dev, staging, and production.

As your serverless applications grow, you might find multiple Lambda functions needing the same libraries, dependencies, or utility code.

Lambda Layers solve this by allowing you to package and share common components across multiple functions.

Layers offer several advantages for managing your Lambda functions:

• Smaller deployment packages: Your function code only contains your business logic, not large libraries.
• Code reusability: Share common functions, helper modules, or SDKs across many Lambdas.
• Faster deployments: Only upload your small function code, not entire dependency sets.
• Consistent dependencies: Ensure all functions use the same version of a library.

When you attach a layer to a Lambda function, AWS extracts its contents into the /opt directory in the function's execution environment.

Your function code can then import modules or use binaries from this /opt directory as if they were part of its own deployment package.

Once a layer is attached, your Python function can simply import modules from it. For example, if your layer contains my_utilities.py at python/my_utilities.py, you can import it like any other module:

This code isn't runnable on its own as the layer isn't defined here, but it shows how you'd import from it.

In this lesson, we learned how to manage Lambda function configurations and dependencies effectively:

• Environment Variables: Key-value pairs for non-sensitive configuration, accessed via os.environ in Python.
• Lambda Layers: Mechanisms for packaging and sharing common code, libraries, and dependencies across multiple functions.
• Layers lead to smaller deployment packages, improved reusability, and faster deployments.

Next up: Dive into logging and monitoring your Lambda functions with CloudWatch!