Releases: spring-media/terraform-aws-lambda
s3 deployment packages
Like the terraform aws_lambda_function this module now all supports specifying the deployment package either directly as a local file (using the filename
argument) or indirectly via Amazon S3 (using the s3_bucket
, s3_key
and s3_object_version
arguments). If filename
is specified, the s3_
-prefixed options cannot be used. (see docs).
With this release the source_code_hash
isn't computed automatically anymore. If you like to trigger updates of your lambda function, please set this variable in the module configuration (see docs for details).
CloudWatch Event Rules
Breaking changes
CloudWatch Event Rules support
In addition to schedule_expression
the module now also supports event_pattern
as a trigger. This functionality has been merged into a new event
type cloudwatch-event
.
If you have been using cloudwatch-scheduled-event
in the past, just replace it with the new event type:
event = {
type = "cloudwatch-event"
schedule_expression = "rate(1 minute)"
}
publish
The publish
argument of the module now defaults to false
as specified by terraform. If you relied on creating new Lambda versions you need to enable this now explicitly:
module "lambda" {
// ...
publish = true
}
runtime
The runtime
argument of the module is now mandatory as specified by terraform. If you relied on the old default (go1.x
), you need to set it explicitly:
module "lambda" {
// ...
runtime = "go1.x"
}
func
for all serverless gophers: https://github.com/moritzzimmer/func/releases/tag/v0.0.17 supports this release
Unified kinesis and dynamodb event sources
Since v4.4.0 this module supports kinesis aws_lambda_event_source_mapping
s. With this release both dynamodb
and kinesis
use the same variables for configuration defaulting to terraform standards.
If you have been using dynamodb
as event
before, please change stream_event_source_arn
to event_source_arn
in your module configuration.
v4.3.0
With release 4.3.0 you can configure reserved_concurrent_executions
(see https://www.terraform.io/docs/providers/aws/r/lambda_function.html#reserved_concurrent_executions) for your Lambda functions, thx to @wavemoran
S3 event
Release 4.2.0 support S3 as an event source, see new example.