Amazon S3 general-purpose bucket and optional path connection for bounded object listing, transfer, marker, delete, and exact-object move operations.

7 listed actions1 capability groups

Connection facts

What the Amazon S3 connector actually exposes.

These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.

Connection method
aws-access-key
Setup
Prefer temporary least-privilege credentials. Store the access key id, secret access key, optional session token, bucket, optional path, and region only in StackOS.
Capability groups
File Transfer
Action boundaries
1 read action6 write actions

Action catalog

Actions listed for Amazon S3.

Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.

7 matching actions

File TransferCan make changes

Create Amazon S3 Directory Marker

Create one zero-byte trailing-slash marker object.

File TransferCan make changes

Delete Amazon S3 Object

Delete one exact current object and retain version/delete-marker facts.

File TransferCan make changes

Delete Amazon S3 Prefix

Delete an empty marker or a bounded current-object prefix set.

File TransferCan make changes

Download Objects Or Prefixes From Amazon S3

Download explicit object or prefix mappings to local destinations.

File TransferReads data

List Amazon S3 Prefix

List one bounded page of objects and common prefixes.

File TransferCan make changes

Move Amazon S3 Object

Copy then conditionally delete one exact current object.

File TransferCan make changes

Upload Files Or Directories To Amazon S3

Upload explicit local mappings with conditional conflict handling.

Direct answer

How does the Amazon S3 integration work?

People continue using Amazon S3 as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.

  1. 01Your requestStart in your AI
  2. 02StackOS planExpands the steps
  3. 03Amazon S3Does its bounded part
  4. 04Checked resultKeeps the proof

Common questions

Amazon S3 and StackOS.

What can the Amazon S3 integration do in StackOS?

The current catalog includes 7 Amazon S3 actions across File Transfer. The exact actions used depend on the workflow and approval rules.

Does StackOS replace Amazon S3?

No. Amazon S3 remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.