Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Amazon S3

Scalable storage in the cloud

CategoryDeveloper Tools
Authenticationcustom
Version0.7.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Amazon S3 with Flows360

Scalable storage in the cloud

Use the Amazon S3 connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 8 actions and 1 trigger.

Available actions

  • Upload File
  • Read File
  • Generate signed URL
  • Generate Signed Upload URL
  • Move File
  • Delete File
  • List Files
  • Decrypt PGP File

Available triggers

  • New or Updated File

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Amazon S3
  • Package: @activepieces/piece-amazon-s3@0.7.0
  • Exact artifact digest: sha256:f10bef88832b2fae81fa3de6d768c4596c00f8351bd0bdcbeb071f5cb7ebc94d
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH, OIDC. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Upload File (upload-file), Upload an File to S3 Classification: read.
  • Read File (read-file), Read a file from S3 to use it in other steps Classification: read.
  • Generate signed URL (generate-signed-url), Generate a signed URL for a file in a s3 bucket Classification: read.
  • Generate Signed Upload URL (generate-signed-upload-url), Generate a pre-signed URL that allows anyone with the link to upload a file directly to S3 without needing AWS credentials. Classification: read.
  • Move File (moveFile), Move a File to Another Folder Classification: read.
  • Delete File (deleteFile), Deletes an existing file. Classification: read.
  • List Files (list-files), List all files from an S3 bucket folder/prefix. Classification: read.
  • Decrypt PGP File (decrypt-pgp-file), Decrypt a PGP encrypted file from S3 using a private key stored in AWS Secrets Manager Classification: read.

Trigger contracts

  • New or Updated File, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects9
Supported actionsNot published
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Access Key ID Required · protected credential
  • Secret Access Key Required · protected credential
  • Endpoint (Optional) Optional
  • Region Required
  • Bucket Name Required
connection_2 · custom
  • Role ARN Required
  • Region Required
  • Bucket Name Required

Supported objects

ObjectReadWriteNotes
Upload File Yes No Upload an File to S3
Read File Yes No Read a file from S3 to use it in other steps
Generate signed URL Yes No Generate a signed URL for a file in a s3 bucket
Generate Signed Upload URL Yes No Generate a pre-signed URL that allows anyone with the link to upload a file directly to S3 without needing AWS credentials.
Move File Yes No Move a File to Another Folder
Delete File Yes No Deletes an existing file.
List Files Yes No List all files from an S3 bucket folder/prefix.
Decrypt PGP File Yes No Decrypt a PGP encrypted file from S3 using a private key stored in AWS Secrets Manager
New or Updated File Yes No polling trigger declared by the pinned package.

Triggers

New or Updated File · Poll

Triggers when you add or update a file in your bucket. The bucket/folder you choose must not contain more than 10,000 files.

Inputs

  • markdown · string
  • folderPath · string

Setup

Setup

  1. Add the Amazon S3 connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Access Key ID (accessKeyId), required; stored as a sensitive connection value.
  • Secret Access Key (secretAccessKey), required; stored as a sensitive connection value.
  • Endpoint (Optional) (endpoint), optional.
  • Region (region), required.
  • Bucket Name (bucket), required.
  • Role ARN (roleArn), required.
  • Region (region), required.
  • Bucket Name (bucket), required.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-amazon-s3@0.7.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 8 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Amazon S3 connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-amazon-s3@0.7.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com