Upload to S3 is a Step (action) in Cloud › AWS. Uploads an object to Amazon S3 (PutObject).
Upload to S3 is a Step (action) in Cloud › AWS. Uploads an object to Amazon S3 (PutObject).
When the flow reaches this step, JOrchestrator executes Upload to S3 against your linked site or an external integration, using the field values you set on General and Design. Downstream steps can read the output payload fields defined for this node.
Upload to S3 is a action step in the Cloud › AWS group. Action steps run in the middle or end of a flow. They perform work on your CMS, call external services, or transform data for the next step.
Typical reasons teams add Upload to S3 to a flow:
Common patterns on the canvas:
AWS access key, secret, and region from your CMS plugin settings → AWS. Body as plain text or base64.
IAM user or role needs s3:PutObject on the target bucket and key prefix.
The designer shows these tabs for this node:
| Tab | Purpose |
|---|---|
| Info | Plain-language description and output payload fields for downstream steps |
| General | Canvas label and read-only node ID |
| AI | Optional assistant to help draft settings from plain language |
| Design | Node-specific configuration fields |
These fields are managed by the designer or runtime — you do not type into them directly:
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
_nodeId | Node ID | node-id | No | — | — |
_payloadFields | Available Fields | payload-panel | No | — | — |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
label | Label | text | No | — | Node label |
| Property key | Label | Type | Required | Visible when | Notes |
|---|---|---|---|---|---|
bucket | S3 bucket | payload-text | Yes | — | my-bucket |
objectKey | Object key | payload-text | Yes | — | path/to/file.json |
body | Body | textarea | Yes | — | File content or {{node_id.field}} |
contentEncoding | Body encoding | select (text | base64; default: text) | No | — | — |
contentType | Content-Type | select (application/octet-stream | application/json | text/plain | text/html | text/csv | text/xml | application/xml | application/pdf | application/zip | application/gzip | image/jpeg | image/png | image/gif | image/webp | image/svg+xml | video/mp4 | audio/mpeg | audio/wav; default: application/octet-stream) | No | — | — |
Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under Node Configuration, not per step on this node. Link the flow to a domain before testing CMS-backed fields.
After this step runs, later nodes can reference these fields using placeholders such as {{upload_to_s3.success}}.
| Field key | Type | Description |
|---|---|---|
success | boolean | Whether the operation completed successfully. |
bucket | string | Cloud storage bucket name. |
objectKey | string | Object key/path within the bucket. |
url | string | Public HTTP URL to a resource on the site. |
etag | string | Entity tag (checksum) from cloud storage. |
bytesWritten | number | Number of bytes written to storage. |
message | string | Human-readable status, error, or result summary. |
bucket) must be filled before the flow can be saved.objectKey) must be filled before the flow can be saved.body) must be filled before the flow can be saved.Other steps in the same area of the palette:
aws-list-s3) — Cloud › AWSaws-log-cloudwatch) — Cloud › AWSaws-media-convert) — Cloud › AWSaws-retrieve-s3) — Cloud › AWS