Push to S3

Push to S3 writes files produced by your Multi FileFeed (MFF) to an Amazon S3 bucket. Use it as a delivery step at the end of an MFF to hand processed files off to another system or team.

Availability: Beta. Requires the WorkflowsS3Push feature. Contact your OneSchema support representative if you do not see this transform.

What it does

• Input: one or more files.
• Output: none for downstream transforms — this is a terminal (sink) node. It writes files directly to S3 rather than passing them onward.
• The transform uploads each input file to the configured bucket, optionally under a key prefix, using the connected S3 credential.

When to use it

• You need to hand off processed or validated files to another system that reads from S3.
• You want to archive MFF outputs in S3 for auditing or downstream batch processing.
• You're replacing a manual upload step with an automated delivery step.

How to configure it

In the MFF builder, add a Push to S3 node at the end of the branch that produces the files you want to deliver.

Settings

Configuration tips

• Use a key prefix that includes a date or run identifier if you want each run's files kept separate in the bucket.
• Confirm the connected S3 account has write permission on the target bucket before saving the node.

Example

Setup

An MFF produces a cleaned orders.csv file. The node is configured with bucket acme-processed and key prefix orders/2024-05-01/.

Result

The file is uploaded to s3://acme-processed/orders/2024-05-01/orders.csv.

Troubleshooting

Upload fails with a permissions error

• Confirm the connected S3 account has s3:PutObject permission on the target bucket and prefix.
• Check that the bucket name is spelled correctly and exists in the expected AWS account/region.

Files are overwritten unexpectedly

• Include a unique element, like a timestamp or run ID, in the key prefix so that each run's files don't collide with previous ones.

See also

• Fetch from Google Cloud Storage
• Fetch from SFTP
• Push to Salesforce