如何在CloudFormation模板中为不同AWS Lambda别名配置不同环境变量

Great question! The key thing to know here is that Lambda aliases don't directly support defining environment variables—they act as pointers to specific function versions. To get environment-specific values for your QA and Prod aliases, you'll need to create separate versions of your Lambda function (each with their own environment variables) and link each alias to the matching version.

Below are two straightforward ways to implement this, based on your existing template:

Option 1: Using Native CloudFormation Resources #

This approach explicitly defines AWS::Lambda::Version resources for each environment, configures their unique env vars, then ties the aliases to those versions:

AWSTemplateFormatVersion: "2010-09-09"
Transform: "AWS::Serverless-2016-10-31"
Description: Lambda function configuration with environment-specific aliases

Resources:
  # Base Lambda function (keep common config here; env vars will be overridden in versions)
  EndpointLambda:
    Type: "AWS::Lambda::Function"
    Properties:
      FunctionName: "endpoint-lambda"
      Handler: "com.test.aws.RequestHandler::handleRequest"
      Runtime: java8
      Code:
        S3Bucket: "lambda-functions"
        S3Key: "test-endpoint-lambda-0.0.1.jar"
      Description: Test Lambda function
      MemorySize: 256
      Timeout: 60
      # Optional: Set universal default env vars here (versions will override duplicates)
      Environment:
        Variables:
          ES_PROTOCOL: https
          ES_PORT: 443

  # QA-specific function version with QA env vars
  QaLambdaVersion:
    Type: "AWS::Lambda::Version"
    Properties:
      FunctionName: !Ref EndpointLambda
      Description: QA environment version
      Environment:
        Variables:
          ES_HOST: qa-es-host-url
          ES_ON: true
          REDIS_URL: qa-redis-host-url

  # Prod-specific function version with Prod env vars
  ProdLambdaVersion:
    Type: "AWS::Lambda::Version"
    Properties:
      FunctionName: !Ref EndpointLambda
      Description: Production environment version
      Environment:
        Variables:
          ES_HOST: prod-es-host-url
          ES_ON: true
          REDIS_URL: prod-redis-host-url

  # QA alias pointing to the QA version
  QaLambdaAlias:
    Type: "AWS::Lambda::Alias"
    Properties:
      FunctionName: !Ref EndpointLambda
      FunctionVersion: !Ref QaLambdaVersion
      Name: "QA"
      Description: "QA alias"

  # Prod alias pointing to the Prod version
  ProdLambdaAlias:
    Type: "AWS::Lambda::Alias"
    Properties:
      FunctionName: !Ref EndpointLambda
      FunctionVersion: !Ref ProdLambdaVersion
      Name: "Prod"
      Description: "Production alias"

Option 2: Simplified Configuration with SAM #

Since your template already uses the SAM transform, you can streamline this by defining versions and aliases directly within the AWS::Serverless::Function resource:

AWSTemplateFormatVersion: "2010-09-09"
Transform: "AWS::Serverless-2016-10-31"
Description: Lambda function configuration with environment-specific aliases (SAM)

Resources:
  EndpointLambda:
    Type: "AWS::Serverless::Function"
    Properties:
      FunctionName: "endpoint-lambda"
      Handler: "com.test.aws.RequestHandler::handleRequest"
      Runtime: java8
      CodeUri: s3://lambda-functions/test-endpoint-lambda-0.0.1.jar
      Description: Test Lambda function
      MemorySize: 256
      Timeout: 60
      # Universal environment variables
      Environment:
        Variables:
          ES_PROTOCOL: https
          ES_PORT: 443
      # Define environment-specific versions
      Versions:
        - VersionName: "QA-Version"
          Description: QA environment version
          Environment:
            Variables:
              ES_HOST: qa-es-host-url
              ES_ON: true
              REDIS_URL: qa-redis-host-url
        - VersionName: "Prod-Version"
          Description: Production environment version
          Environment:
            Variables:
              ES_HOST: prod-es-host-url
              ES_ON: true
              REDIS_URL: prod-redis-host-url
      # Link aliases to their respective versions
      Aliases:
        - AliasName: "QA"
          Version: "QA-Version"
          Description: "QA alias"
        - AliasName: "Prod"
          Version: "Prod-Version"
          Description: "Production alias"

Key Notes #

• Environment variables defined in a function version will override any matching variables from the base function.
• When you invoke an alias, it uses the environment variables from the version it points to.
• For variables that change frequently, consider using AWS Systems Manager Parameter Store or Secrets Manager instead of hardcoding them in versions. This lets you update values without deploying new function versions—you'd just have your Lambda fetch the latest values at runtime.

内容的提问来源于stack exchange，提问作者Hleb