Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Object storage

S3 presigned URLs explained: temporary access without sharing keys

Published August 2026 · 7 min read · Updated 2026-09-07

An S3 presigned URL is a time-limited signed request that lets another client perform a specific storage operation without receiving the application’s permanent access key. Treat the URL itself as temporary sensitive data: possession can be enough to use the delegated request while it remains valid.

The application signs, the recipient executes

A trusted application uses its S3 credential to calculate a signature for a particular HTTP method, bucket, object key and expiry. The recipient then sends that signed request directly to the object endpoint.

The recipient does not learn the permanent secret key. The storage service validates the signature and time window when the URL is used.

Presigned access inherits the signer scope

The signing identity must already be allowed to perform the requested action. A presigned URL cannot legitimately grant more authority than the credential that produced it.

Keep the signing user scoped to the application’s bucket. Otherwise a bug in key selection can create signed access to data the application should never have reached.

Expiry is a security control, not a one-time-use switch

Do not assume a presigned URL becomes invalid after its first successful request. Amazon S3 documents that the same presigned URL can be used multiple times until it expires; other S3-compatible services should be tested rather than assumed to have identical reuse behavior. Choose an expiry that matches the transfer window and treat a leaked URL as usable for that window.

The advertised expiry is also not always the only validity limit. On Amazon S3, temporary signing credentials can expire before the URL’s requested expiry, and policy controls can impose a shorter allowed signature age. Immediate revocation can require changing the underlying permission or credential. Test the exact provider and credential type before promising cancellation behavior.

AWS: presigned URL behavior and expiration

Uploads need validation around the URL

A presigned PUT can allow a browser or client to upload without proxying the entire file through the application server. The application should still control object naming, size expectations, content handling and later processing. If the signed request includes headers such as Content-Type or a checksum, the uploader must send the matching signed values.

Do not trust a client-supplied filename as a safe storage key or executable content type. Object storage authorization and application input validation solve different problems. When integrity matters, test the checksum mechanism supported by the exact S3-compatible service and SDK instead of assuming every AWS checksum option exists.

AWS: uploading with a presigned URL

Test clock, method and endpoint behavior

Presigned requests depend on time and on the exact endpoint/signing inputs. Test expiry, wrong method, altered key and an intentionally expired URL as negative cases.

Compatibility testing should use the SDK that will generate production URLs because subtle differences in endpoint or addressing style can invalidate otherwise correct signatures.

Next step

Learn how S3 presigned URLs authorize a specific operation for a limited time, where they help, what they expose and how to use them safely.

Explore DotMoose Object Storage

Keep reading

Related guides.

boto3 S3-compatible storage: custom endpoint, put_object and connection tests

Connect boto3 to S3-compatible storage with endpoint_url. Start with a read-only list, then optionally verify put_object with one isolated write/read/delete round trip.

Read the guide

S3 multipart upload explained: part size, retries, checksums and cleanup

Learn how S3 multipart upload works: numbered parts, AWS part-size limits, parallel retries, completion, checksums and cleanup of abandoned uploads.

Read the guide

Veeam S3-compatible repository: setup and compatibility checklist

Use this checklist before adding an S3-compatible repository to Veeam Backup & Replication: protocol requirements, bucket ownership, immutability, credentials, capacity and restore testing.

Read the guide

More object storage guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move