Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Analyzer should pull bucket from event, not environment variables
See original GitHub issueBackground
Right now, the analyzer uses os.environ['S3_BUCKET_NAME'] to determine which bucket to download binaries from. The problem with this approach is that the analyzer can never be invoked for any other bucket. If the bucket name were pulled from the event notification instead of an environment variable, the analyzer could be invoked directly for any S3 object.
In particular, this would make it easy for users to manually add event notifications for their existing S3 buckets.
Desired Change
Use the bucket name from the event notification instead of an environment variable.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The documentation should be updated with instructions on how to use BinaryAlert to analyze existing S3 buckets
Each lambda function needs its own policies to interact with the various AWS resources, and those policies are all defined in
terraform/lambda_iam.tf, which are attached to the Lambda execution role