Create Amazon S3 Directory Marker
Create one zero-byte trailing-slash marker object.
Amazon S3 general-purpose bucket and optional path connection for bounded object listing, transfer, marker, delete, and exact-object move operations.
Connection facts
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.
Action catalog
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
Create one zero-byte trailing-slash marker object.
Delete one exact current object and retain version/delete-marker facts.
Delete an empty marker or a bounded current-object prefix set.
Download explicit object or prefix mappings to local destinations.
List one bounded page of objects and common prefixes.
Copy then conditionally delete one exact current object.
Upload explicit local mappings with conditional conflict handling.
Direct answer
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.
Common questions
The current catalog includes 7 Amazon S3 actions across File Transfer. The exact actions used depend on the workflow and approval rules.
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.