bucket event notifications creates placeholder lambda function

Describe the bug When you use function.addEventSource(new S3EventSource(...)) or bucket.addObjectCreatedNotification(...) it creates a BucketNotificationsHandler lambda function with some placeholder code.

To Reproduce

    const bucket = new Bucket(this, 'TestBucket');
    const lambda = new Function(this, 'TestFunction', {
      code: Code.asset('./test-src'),
      runtime: Runtime.NodeJS10x,
      handler: 'index.handler',
      description: 'Example function',
    });
    lambda.addEventSource(new S3EventSource(bucket, {
      events: [EventType.ObjectCreated],
    }));

Expected behavior Should only connect the TestFunction to the lambda function not create a new placeholder function.

Version:

• macOS 10.14.5
• Typescript
• 0.33

[jthornbrue]

My stack contains an object created notification that triggers an SNS topic. See below (using the Python API):

my_bucket.add_event_notification(
        aws_s3.EventType.OBJECT_CREATED,
        aws_s3_notifications.SnsDestination(my_topic),
        aws_s3.NotificationKeyFilter(
            prefix=OUTPUT_PREFIX,
            suffix='.csv'
        )
    )

This creates a dummy lambda function in the stack–even though there is not and never will be a lambda target. This is annoying. Any progress on this bug?

[LechuckThePirate]

This should be solved. I don’t understand how this went out of beta with this problem. If you run into this, it’s not just that you have a lambda function there that shouldn’t be there… the thing is you are actually PAYING for every S3 bucket event…