Skip to content

Changing the S3 bucket that triggers the lambda #85

Description

@BFASRachelS

I am playing with the newrelic/aws_s3_log_ingestion_lambda: AWS Lambda that sends log data from S3 to New Relic Logging and I can see the logs in New Relic when I upload files to the default bucket that is created. In this it creates a bucket prefix that matches the name of stack in the samconfig.toml file.

The docs indicate that I should be able to set;
resolve_s3 = false
s3_prefix = ""
I have an existing bucket that I write error logs to, and I want that bucket to trigger the lambda function instead of the default one created during the deployment of aws_s3_log_ingestion_lambda
When I replace the s3_prefix with the name of that bucket, it just gets overwritten with the default that is created during the deployment and matches the name of the stack name I specify.

If you could assist me, that would be great.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions