v0.90.0

• No changes

v0.89.0

• No changes

v0.88.0

Support `source_zip` as source for Lambda@Edge submodule @zdmytriv (#262)

what

Added support source_zip option for lambda@edge functions.

why

There are cases when we need to send the archive as a source for Lambda@Edge. For example, include node_modules for node js projects.

So at the moment, this module supports 3 types of sources for Cloudfront Lambda@Edge:

• source - just a string with source code that is going to be saved to a file and archived by this module
• source_dir - path to the directory that contains a few files and/or subdirectories that are going to be archived by this module
• source_zip - path to a single zip file. This is useful when Lambda@Edge has a lot of dependencies for example in the case of NodeJS - node_modules directory

See examples/complete for usage examples.

references

• Closes #205

v0.87.0

Ability to specify source directory for Lambda@Edge submodule @zdmytriv (#260)

what

• Ability to specify source directory for Lambda@Edge submodule

why

• Currently, we can pass the list of files that will be archived and uploaded as Lambda sources. This is not an option if more advanced logic is used and a lot of files should be used.

Example

For example, we have the following file structure for lambda@edge submodule:

lambda_edge_example/
    lib/
        node_modules/
        index.js
        package.json
        package-lock.json
    context.tf
    main.tf
    outputs.tf
    variables.tf

And we want the whole directory lib to be packaged.

With this enhancement path to lib might be specified like this

module "lambda_edge" {
  source  = "cloudposse/cloudfront-s3-cdn/aws//modules/lambda@edge"
  version = "x.xx.x"

  functions = {
    viewer_request = {
      source_dir   = "${path.module}/lib/"
      runtime      = "nodejs12.x"
      handler      = "index.handler"
      event_type   = "viewer-request"
      include_body = false
    }
  }

  // ...
}

Related

Closes #205

v0.86.0

feat: add http_version variable @syphernl (#256)

what

• Adds http_version variable.

why

• To be able to control the maximum HTTP version to be supported by the CloudFront Distribution, defaults to http2

references

• Finishing work started in #238 by @kim0

v0.85.0

Revert #253 @Benbentwo (#254)

what

• Reverts #253

why

• misunderstanding of use cases

v0.84.1

🚀 Enhancements

bugfix `website_enabled` @Benbentwo (#253)

what

• website enabled means we should use
  • Public Bucket
  • No TLS Verify on bucket assets (not used by cloudfront in website mode)
  • No Lambda Edge association

why

• Bugfix Website Mode

references

• 4. on this doc

v0.84.0

Add support for origin shield @alexjurkiewicz (#247)

For default origin only.

v0.83.0

🚀 Enhancements

Allow overwriting DNS records @LCaparelli (#246)

Signed-off-by: Lucas Caparelli [email protected]

what

• Allow overwriting DNS records

why

• See #245

references

• Resolves #245

v0.82.5

🚀 Enhancements

Allow AWS provider version >= 4.9.0 @nitrocode (#236)

what

• Allow AWS provider version >= 4.9.0

references

• Version 4.0.0 had breaking changes, so this module had pinned AWS provider < 4.0. Breaking changes were replaced with deprecation warnings in v4.9.0, so we can now allow later versions.