-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat guard lambda s3 output #240
base: main
Are you sure you want to change the base?
Conversation
if e.s3_output_bucket.is_empty() { | ||
resp = results_vec; | ||
}else { | ||
// No extra configuration is needed as long as your Lambda has |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there are prerequisite permissions to be granted to Lambda role, let's add a documentation in README for Lambda for granting required permissions to the access policy such as bucket s3:PutObject
action.
This item is currently being reviewed. As the AWS SDK is in Developer Preview, this will not be merged to main. Will follow up soon. |
Issue #, if available: #236
Description of changes:
Added new flag to guard-lambda to send output to S3 bucket
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license