Skip to content

Latest commit

 

History

History
48 lines (39 loc) · 1.43 KB

README.md

File metadata and controls

48 lines (39 loc) · 1.43 KB

CDK Construct for adding config.json file to a Lambda Function

When using Lambda@Edge, a function cannot use environment variables. This CDK Construct uses a Custom Resource to inject a config.json file with user provided values into an existing function, and publishes a new version that is ready to be used as part of a CloudFront Distribution.

Inspired by similar mechanism in https://github.com/aws-samples/cloudfront-authorization-at-edge/

Usage

npm install @studyportals/cdk-lambda-config

Using the construct:

const originalFunction = lambda.Function.fromFunctionArn(...)
const updatedFunction = new LambdaConfig(this, "UpdatedFunction", {
  function: originalFunction,
  config: {
    Key1: "Some value",
    Nested: {
      Key2: "Other value",
    },
  },
  nonce: "1", // See TSDoc.
}
// Can now retrieve the new version:
updatedFunction.version

Read from within the handler:

const fs = require("fs")
const path = require("path")
const config = JSON.parse(
  fs.readFileSync(path.join(__dirname, "config.json"), "utf-8"),
)

If function update is meant to run concurrently targeting the same function, you can pass locksTable property in the config object, pointing to a table that's been created using LockableTable.create(this,"UpdateCodeLocks") in the project that uses @studyportals/cdk-lambda-config This will ensure that multiple stacks won't get stuck while trying to update the same function