S3 bucket notification to Lambda

[bfedorov-clgx]

Description

Hello!
When Itry to create S33 bucket with notification to Lambda Igabe a issue.

Code

`module "s3_bucket" {
source = "terraform-aws-modules/s3-bucket/aws"

for_each = var.buckets

bucket = lookup(each.value, "bucket")
acl = lookup(each.value, "acl")
control_object_ownership = lookup(each.value, "control_object_ownership")
object_ownership = lookup(each.value, "object_ownership")
versioning = lookup(each.value, "versioning")
force_destroy = true
}

module "all_notifications" {
source = "../../modules/notification"

bucket = module.s3_bucket["source_bucket"].bucket

eventbridge = true

Common error - Error putting S3 notification configuration: InvalidArgument: Configuration is ambiguously defined. Cannot have overlapping suffixes in two rules if the prefixes are overlapping for the same event type.

lambda_notifications = {
lambda1 = {
function_name = module.lambda["function1"].function_name
events = ["s3:ObjectCreated:*"]
}
}
} `

issue

18:24:23 Initializing modules... 18:24:23 - all_notifications in 18:24:23 Downloading terraform-aws-modules/lambda/aws 5.3.0 for lambda... 18:24:23 - lambda in .terraform/modules/lambda 18:24:23 Downloading terraform-aws-modules/s3-bucket/aws 3.14.0 for s3_bucket... 18:24:24 - s3_bucket in .terraform/modules/s3_bucket 18:24:24 ╷ 18:24:24 │ Error: Unreadable module directory 18:24:24 │ 18:24:24 │ Unable to evaluate directory symlink: lstat ../../modules: no such file or 18:24:24 │ directory 18:24:24 ╵ 18:24:24 18:24:24 ╷ 18:24:24 │ Error: Failed to read module directory 18:24:24 │ 18:24:24 │ Module directory does not exist or cannot be read. 18:24:24 ╵ 18:24:24

[Anton Babenko]

Change module source from:

source = "../../modules/notification"

to

source = "terraform-aws-modules/s3-bucket/aws//modules/notification"

[bfedorov-clgx]

Thanks a lot!

[bfedorov-clgx]

hello @antonbabenko

which version of Lambda module should I use in order to avoid this failure?
Everything is deployed and working but Jenkins job didn't succed

16:22:23 │ Error: adding Lambda Permission (lambda-function/AllowExecutionFromS3Bucket): InvalidParameterValueException: We currently do not support adding policies for $LATEST.
16:22:23 │ {
16:22:23 │ RespMetadata: {
16:22:23 │ StatusCode: 400,
16:22:23 │ RequestID: "08293542-9973-4d17-b494-cfa3f47ae01b"
16:22:23 │ },
16:22:23 │ Message_: "We currently do not support adding policies for $LATEST.",
16:22:23 │ Type: "User"
16:22:23 │ }
16:22:23 │
16:22:23 │ with module.lambda["function1"].aws_lambda_permission.current_version_triggers["AllowExecutionFromS3Bucket"],
16:22:23 │ on .terraform/modules/lambda/main.tf line 206, in resource "aws_lambda_permission" "current_version_triggers":
16:22:23 │ 206: resource "aws_lambda_permission" "current_version_triggers" {
16:22:23 │
16:22:23 ╵

[Anton Babenko]

@bofedorov-clgx You should set create_current_version_allowed_triggers = false in the Lambda module

https://github.com/terraform-aws-modules/terraform-aws-lambda/blob/master/variables.tf#L367-L371

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.