S3 Bucket Event Lambda Trigger
Note: The information in this section is applicable for an app executable only.
Use the S3 Bucket Event Lambda trigger to trigger a Lambda function when a supported event occurs on the associated S3 bucket.
Trigger Settings
Note:
- Creating a new event or updating an existing event in the S3 Bucket Event Lambda trigger and re-pushing the app deletes existing Events on AWS S3.
- You can have only one S3 trigger in an app. An app that has an S3 trigger cannot contain any other triggers including another S3 trigger. The S3 trigger supports multiple handlers (flows), so you can have multiple flows in the app that are attached to the same S3 trigger. You can also have blank flows in the app which can serve as subflows for the flows that are attached to the S3 trigger.
For overriding app properties, use the FLOGO_APP_PROPS_JSON environment variable only. You cannot override app properties using the FLOGO_APP_PROPS_ENV environment variable.
Field | Description |
---|---|
AWS Connection Name | (Mandatory) Name of the AWS connection that you want to use for deploying the flow. |
Execution Role Name | Permission of the Lambda function to execute. The role must be assumable by Lambda and must have CloudWatch logs permission execution role.
By default, Cloud watching is enabled. |
Bucket | Name of the S3 bucket with which the trigger is to be associated. This bucket must be an existing one. |
Event name | Name of the S3 bucket event notification. |
Event list | A list of operations to be performed on the S3 bucket. Supported operations are POST, PUT, COPY, and DELETE. |
Object prefix filter | (Optional) The prefix is to be used to filter the S3 bucket.
For example,
|
Object suffix filter | (Optional) The suffix is to be used to filter the S3 bucket.
For example,
|
Map to Flow Inputs
Map the flow output to the trigger reply on this tab. The tab displays the following fields.
Field | Description |
---|---|
Function | Information about the Lambda function |
Context | Envelope information about this invocation |
Identity | Identity for the invoking users |
ClientApp | Metadata about the calling app |
S3Event | Default schema of S3 bucket event trigger. It can be mapped with the flow input to pass the key values to the flow. |