S3 Sign Upload Template — Reference
Insert a provider, signed-upload URL and URL-response scaffold.
Insert a provider, signed-upload URL and URL-response scaffold.
Before you begin
Section titled “Before you begin”- An open Server Connect action. Use disposable records/files when testing generated write or upload steps.
S3 Sign Upload Template
Section titled “S3 Sign Upload Template”Insert a provider, signed-upload URL and URL-response scaffold.
Fields or generated steps
Section titled “Fields or generated steps”| Part | Meaning |
|---|---|
| Incoming name | The template defines $_GET.name and uses it as the destination key. Replace or validate this with an authorized, scoped server-chosen key before exposing the endpoint. |
| Generated provider | Creates s3 with blank endpoint and credentials. Select a properly configured provider instead of deploying the blank values. |
| Generated signer | Creates sign for the selected bucket/key, then outputs url from the signed result. Supply the bucket, expiry and access settings appropriate to the provider. |
Verification example
Section titled “Verification example”Configure an approved test provider and a disposable key prefix. Generate a short-lived upload URL, use the correct PUT request and headers from a test client, then verify the stored object before marking upload complete.
What remains your responsibility
Section titled “What remains your responsibility”The template only signs a request; it does not transfer bytes, validate the uploaded file or create a database record. Authenticate and authorize the signing endpoint, use collision-safe keys, verify bucket CORS/policy, and inspect the object after upload. See the S3 Provider and Sign Upload URL references for current constraints.
Review the resulting workflow
Section titled “Review the resulting workflow”Inspect the actual generated or included steps, their inputs and their final output before connecting the action to a user-facing page.
Check your result
Section titled “Check your result”You can identify what this editor entry adds and configure or interpret it without assuming an unfinished scaffold is a completed workflow.