S3 Presigned Document URLs: Expiry and Revocation

Treat download links as temporary credentials and plan how to stop future use

Published Updated

S3 Presigned Document URLs: Expiry, Sharing, and Revocation. Layered-paper illustrations show a linked document, a clock, and a closed access gate, labelled Issue, Limit lifetime, and Contain access.

A staff member opens a private contract, copies its download URL, and posts it in the wrong chat. Another person can download the file without signing in to the document application. The link itself carries temporary permission for that download.

Treat a presigned document URL as a temporary credential. Authorise its creation, keep it within the intended workflow, set a suitable lifetime, and decide how future requests can be stopped if it is shared accidentally. These links let an application transfer private S3 content without making the bucket public.

Understand what the link authorises

Start by separating the document's stored permissions from the access carried by its download link. The following properties explain why a private bucket can still serve a person who receives a valid signed URL.

A specific storage request

The signature covers an operation against an S3 object. The application's permission check happens before issuance; a later storage request uses the signed URL and applicable AWS controls.

Possession can be enough

A person who receives the complete working URL can make that request, subject to expiry and storage restrictions. Forwarding the link can therefore extend access beyond the original user.

Repeated use is possible

A presigned URL can be used more than once while valid. If the workflow needs single use or a named recipient check, design those controls into the delivery route.

AWS's presigned-request FAQ explains both forwarding and repeated use. Choose whether possession of the URL is sufficient for your scenario before selecting the delivery method.

Protect the complete lifecycle

  1. 1 · Issue

    Authorise the exact request

    Evaluate user, site, document, version, artifact, operation, watermark, and permitted duration.

  2. 2 · Deliver

    Protect the download link

    Use HTTPS, generate the link when needed, and keep its signature out of analytics, tickets, and diagnostic logs.

  3. 3 · Expire

    Limit and monitor exposure

    Apply signature-age and network guardrails where suitable, record issuance, and define incident revocation.

Choose lifetime limits and containment controls

Revocation and containment options.
ControlEffect and trade-off
Short expirationSets a deadline for new requests. Choosing a short lifetime initially reduces exposure; changing defaults later does not rewrite an existing signature.
Temporary signing credentialsThe URL cannot outlive its signing credentials. Revoking older role-session permissions can affect other requests using those sessions too.
Bucket policy signature ageA configured s3:signatureAge limit can deny older signed requests even when the requested expiry is later. Test retries and slow workflows against the limit.
Network restrictionLimits usable paths but can break legitimate external or mobile access.
Object and version accessContainment must address the exact object version and applicable storage permissions. Replacing the current file alone does not address a URL pinned to an older version.
Authenticated content serviceA service that checks each content request can enforce current recipient permissions. Design its capacity and costs; a redirect to a reusable S3 URL still exposes that URL.

AWS documents that the requested expiry and the lifetime of the signing credentials both limit access. S3 checks expiry when a request begins: an in-progress download can continue past the deadline, while a later restart needs a valid request. See the S3 expiration guidance.

AWS's signature-age guidance describes limits that can shorten validity. For emergency containment, its role-session revocation guidance explains the broader effect on sessions issued before a cutoff. Choose a tested scope so stopping one leaked link does not unnecessarily interrupt unrelated work.

Check versioned content explicitly. AWS's version-deletion documentation distinguishes a current delete marker from removal of a particular stored version. Keep deletion and retention policy separate from incident containment; choose an access restriction when the record must remain preserved.

Prevent browser and logging leakage

Deliver the URL only to the client that needs it, when the download is requested. Avoid embedding long-lived URLs in static pages, emails, or persistent application state. Redact signatures or complete query strings in analytics, diagnostics, and support records, following AWS logging guidance. Review referrer policy, redirects, browser integrations, and intermediary logging as part of the delivery path.

Record a URL issuance event using document, version, user, purpose, requested duration, and request ID, but omit the query string and signature. S3 data events or approved access logs can help investigate use, subject to cost, privacy, and retention decisions.

Work through an accidental share

In this fictional workflow, a staff member requests a two-hour download link for contract version 6, then posts it in the wrong chat. The incident process needs to stop new downloads while preserving the contract.

  1. Identify the issued request

    Use the issuance record to find the document, version, signer, issue time, requested expiry, and applicable policy. Record the incident reference and likely audience without pasting the signed URL into the case.

  2. Contain access through the tested route

    The operator applies the deployment's selected storage-policy or credential response for that object and version. Assess whether the change also affects other documents or users. A change to application-level business permissions alone does not alter the already-issued S3 signature.

  3. Verify new requests are denied

    Check a fresh request through the leaked route, the exact version, and any remaining configured access paths. Confirm required legitimate workflows still work. Record the action and observed result without claiming it recalls a copy already downloaded.

  4. Resume the intended workflow

    If the approved recipient still needs the contract, provide the agreed sharing route with its own audience and expiry settings. Keep the incident history and review why the raw download link reached the wrong channel.

Test URL handling

  • Issue URLs only after current document and version authorisation.
  • Test the requested duration, credential expiry, and configured signature-age limit, including delayed retries.
  • Verify full URLs never enter analytics, logs, tickets, or notifications.
  • Test watermark, content-disposition, version, and artifact behaviour.
  • Exercise suspected leakage and measure revocation propagation.
  • Use a stronger external-sharing workflow when recipient control is required.

Treat the URL like a temporary credential

Presigned URLs are useful for direct delivery of private document content. Match their scope and lifetime to the task, protect the signed request, and retain enough issuance context to respond if it is forwarded. Use a recipient-controlled route when the workflow needs to check who is retrieving the document.

      Start with FormKiQ Core

      The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.

      Get Started Free

      Deploy FormKiQ Essentials or Advanced

      Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.

      Explore Options

      Plan an Enterprise Rollout

      For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.

      Book a Call