S3 Notifier

The S3 Notifier output connection will send submission data and state-change notifications to the Amazon S3 URI you specify. Each file’s name will be in the format ____.json.

If you would like to use the S3 Notifier connection in a SaaS instance and your service is not public, you should create a firewall pinhole for the connection. Contact your Hyperscience representative for more information.

Sample use cases

  • Send extracted information and submission metadata to an S3 bucket for downstream processing.

  • Configure monitoring of the output bucket and alert other systems to take action on submissions, if needed.

Block settings table

In addition to the settings outlined below, you can also configure the settings described in Universal Integration Block Settings.

Name

Required?

Description

S3 URI

Yes

The URI of the location where the data should be stored (in the format of s3://///).

Use AWS EC2 Instance IAM Role Credentials 

Yes

If selected, credentials are obtained from the EC2 instance directly, and the AWS Access Key ID and Secret Key are not present.

This option applies only to on-premise instances. It must be disabled in SaaS deployments.

Enabled by default.

AWS Access Key ID

Yes, if Use AWS EC2 Instance IAM Role Credentials is not selected

The access key ID allows access to the S3 bucket.

This setting is only available if Use AWS EC2 Instance IAM Role Credentials is not selected.

AWS Access Key ID must be provided in SaaS deployments.

Secret Access Key

Yes, if Use AWS EC2 Instance IAM Role Credentials is not selected

The secret access key allows access to the S3 bucket.

To edit the key, click Edit value, modify the key, and then click Done.

This setting is only available if Use AWS EC2 Instance IAM Role Credentials is not selected.

Secret Access Key must be provided in SaaS deployments.

 

Setting up the S3 Notifier

To set up the S3 Notifier, enter the settings as described in the Block settings table above. 

Before deploying a flow with the S3 Notifier enabled, ensure that the credentials you’ve specified in the block settings have the PutObject permission for the specified prefix.