Skip to main content

Configuring S3 Event-Driven Flows

Ganymede Flows can be triggered on file save to an S3 bucket, so that files are processed as soon as they land in an S3 bucket. This page details the configuration required to enable this platform feature.

EventBridge setup in AWS​

  1. Create bucket (if necessary) and, in Properties, enable “Send notifications to Amazon EventBridge for all events in this bucket”.

  2. Set up an EventBridge rule

    1. Navigate to EventBridge -> Rules -> Create Rule
    Setup EventBridge rule
    1. In Build Event Pattern, select “AWS events or EventBridge partner events”, and configure event pattern for S3 Object Created events. The example below shows an example S3 bucket called ganymede-s3-to-eventbridge referenced.
    Set up event pattern

    1. In Select Targets, select “EventBridge API destination” and enter the API Destination details (POST request to https://<tenant subdomain>.ganymede.bio/event/aws)

    2. Enter a new connection with authorization type “API Key”.

      • API key name: api-key
      • Value: <enter an api key value that will be sent in request header>.
         
      note

      You can generate the API Key by running

      Linux:

      openssl rand -hex 32

      Windows PowerShell:

      [System.BitConverter]::ToString((1..32 | ForEach-Object {Get-Random -Minimum 0 -Maximum 256})).Replace('-','').ToLower()
      Set up EventBridge API Key in AWS

    3. Create rule.

  3. Enter the API Key configured in step 2.iv into a secret named s3_api_key the Environment Secrets panel.

  4. Test out the connection using an S3 Event node.

  5. Deliver your S3 bucket name to Ganymede support. Your Ganymede representative will need to direct events coming from your S3 bucket to your Ganymede tenant. To do so, please provide them with your S3 bucket name.

Troubleshooting​

Issue: An S3 Event rule and IAM role have been set up correctly, but there is no indication that EventBridge has accessed the role.​

Check the event bus for the event rule; the monitored event, by default, would go to a default event bus rather than a newly created event bus.