ตัวแปรสภาพแวดล้อมและการกำหนดค่า

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.

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.

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.

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.

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!

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.

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).

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.

Consider a Lambda function that needs to connect to different databases in its 'development' and 'production' environments.

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.