Add S3 Bucket to SNS mapping

[AlexeyRaga]

It would be very helpful if Terraform could add event notifications from an S3 Bucket to an SNS topic.
ASW has this ability through the UI and it is also supported by CloudFormation, but not by Terraform as far as I can tell.

[stack72]

@AlexeyRaga I cannot see, within the UI, a way to hook an S3 bucket up to an SNS Topic

Got any more info on how to do this?

[wstaples]

From the S3 console click properties and expend the Events section:

You can also use the cli:
aws s3api get-bucket-notification-configuration --bucket <some_bucket>

The best way to handle this would probably be to add an event property to the aws_s3_bucket resource and users can provide there own JSON.

[dwradcliffe]

Yeah bucket event config would be a big help!

[dwradcliffe]

See also: #3108

[mdevs5531]

+1 for s3 events -> SQS

[comozo]

+1 for s3 events -> SNS

[harrisnb]

+1 for s3 events -> SNS allowing users to provide their own JSON

[dabdine-r7]

I was able to work around this by combining an idea from @wstaples and the null_resource, a trigger and the local_exec provisioner:

resource "null_resource" "test_bucket_sns_event_notification" {
   triggers {
      bucket = "${aws_s3_bucket.test_bucket.arn}"
   }

   provisioner "local-exec" {
      command = <<EOF
aws s3api put-bucket-notification-configuration --region ${var.region} --bucket ${aws_s3_bucket.test_bucket.bucket} --notification-configuration \
'{
    "TopicConfigurations": [
        {
            "TopicArn": "${aws_sns_topic.some_sns_topic.arn}",
            "Events": [
                "s3:ObjectCreated:*"
            ]
        }
    ]
}'
EOF
   }
}

Obvious pros and cons here, so YMMV.

CONS:

1. Terraform can't enforce policy configuration in this model so be aware of users hand-modifying the policy via the aws cli OR the aws console.
2. Requires the aws cli to be installed locally to make use of s3api.

PROS:
It works :P

[dabdine-r7]

Oh, and +1 for s3 events -> SNS

[sp-ludovic-ivain]

+1 for s3 events -> SQS :)

[joseph-wortmann]

+1 for s3 events -> SQS

[gilessteinberg]

+1 for s3 events -> Lambda

[wincus]

+1 for s3 events -> SQS

[falaa]

+1 for s3 events -> SQS

[egoldschmidt]

+1

[iceycake]

S3 Event Notification will look something like this?

resource "aws_s3_bucket" "b" {
  notification {
    lambda {
        event = ""
        function = ""
        filter {
            name = ""
            value = ""
        }
        filter {
            name = ""
            value = ""
        }
    }
    sns {
        event = ""
        topic = ""
        filter {
          name = ""
          value = ""
        }
    }
    sqs {
        event = ""
        queue = ""
        filter {
          name = ""
          value = ""
        }
    }
  }
}

[conorgil]

+1 for s3 events -> SQS

[rantav]

Joining the herd:
+1 for s3 events -> Lambda

[rbachman]

+1 for s3 events

[curena]

It looks like bucket event notifications are being implemented via #5473

[stack72]

This has been implemented via #5473 with thanks to @kjmkznr

[ghost]

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.