S3 Bucket Event Lambda Trigger
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.
| 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. A default role with the AWS predefined
AWSLambdaBasicExecutionRole permission is created if omitted.
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 to be used to filter the S3 bucket.
For example,
|
| Object suffix filter | (Optional) The suffix to be used to filter the S3 bucket.
For example,
|
Map to Flow Inputs
Map the flow output to the trigger reply in 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. |