Guide · Amazon S3 and Azure Blob Storage

How to revoke an S3 presigned URL or an Azure SAS token.

The short answer is that you cannot revoke the URL itself. Neither service keeps a list of the links it has signed, so there is nothing to cross off. What you can do is invalidate the thing the URL depends on. Each way of doing that has a blast radius, and this page is mostly about choosing the smallest one.

Checked against AWS and Microsoft documentation on 5 November 2026. Commands are for the AWS and Azure CLIs; the portals and SDKs expose the same operations.

Why there is no revoke button

A presigned URL or a SAS token is a signature over a set of permissions and an expiry, made with a secret only you and the service hold. When a request arrives, the service recomputes the signature from the secret and checks the expiry and the signer's permissions as they are right now. It never looks anything up. That is what makes these links cheap and fast, and it is why there is no per-link off switch: the service has no record that the link exists. To kill a link you change one of the inputs the check depends on: the secret, the permissions, or the object.

On Amazon S3

  1. Remove the signer's permission. The cleanest option when the URL was signed by a dedicated IAM user. S3 re-checks the signer's permissions on every request, so detaching s3:GetObject from that user, or adding a bucket-policy deny for that principal, fails every URL it ever signed, immediately. Nothing else is affected if the user existed only to sign links, which is a good reason to set it up that way in the first place.
    $ aws iam detach-user-policy --user-name link-signer --policy-arn arn:aws:iam::123456789012:policy/LinkSignerRead
  2. Disable or rotate the access key that signed it. Every presigned URL made with that key stops working at once, and so does every script and application using the key. Disable rather than delete, so you can reverse it if something unexpected breaks.
    $ aws iam update-access-key --user-name link-signer --access-key-id AKIA… --status Inactive
  3. Move or delete the object. The URL names a key; if nothing is at that key, the download returns 404. With versioning on, a URL without a version id serves the current version, so a delete marker works too. Crude, but it is the only option that works when you have no idea which credentials signed the link.
  4. If it was signed by a role, wait. A URL signed with temporary credentials dies when that session's token expires, often within the hour, at most twelve. Sometimes the right answer is to check the session length and let it lapse.
  5. For next time: cap the age at the bucket. A bucket policy can refuse any presigned request whose signature is older than a limit you set, in milliseconds, with the s3:signatureAge condition. It does not revoke a link that exists, but it means no link signed against that bucket can outlive the window you choose, whoever signed it.
    "Condition": { "NumericGreaterThan": { "s3:signatureAge": "600000" } }

On Azure Blob Storage

Azure has three kinds of SAS, and which kind you issued decides what you can do.

  1. A service SAS tied to a stored access policy. This is the one Microsoft designed for revocation. The policy on the container holds the permissions and expiry; the SAS only references it. Set the policy's expiry to the past, or delete it, and every SAS that references it stops working immediately. A container can hold five policies, so one per client or per job is a sensible layout.
    $ az storage container policy update --account-name clientacct --container-name masters \
        --name deliveries-oct --expiry 2026-01-01T00:00Z
  2. An ad-hoc SAS signed with the account key. This is what most tools and the portal's "Generate SAS" produce, and it has no policy to cancel. The only way to kill it is to regenerate the account key that signed it, which kills every SAS and every application using that key. Storage accounts have two keys for exactly this reason: move your applications to the other key first, then regenerate the one the SAS was signed with.
    $ az storage account keys renew --account-name clientacct --key key1
  3. A user delegation SAS, signed with an Entra ID identity rather than the account key. These live at most seven days, and all of them for an account can be revoked at once by revoking the account's user delegation keys, or for one signer by removing that identity's role on the container.
    $ az storage account revoke-delegation-keys --name clientacct
  4. Move or delete the blob, as on S3, when you do not know how the SAS was signed.
  5. For next time: a SAS expiration policy on the account. The storage account can carry a maximum SAS lifetime, with an action of Log or Block. With Block, a SAS signed for longer than the period is refused, so no one on the team can issue a year-long token by accident.

The pattern behind all of them

Every option above works by making the link depend on something you can change: a dedicated signer, a stored policy, a key you can afford to rotate. The links that are hardest to revoke are the ones made quickly from the main account key by whoever had it to hand. So the practical rule is: never share a signed URL directly. Share something that points at it and that you control.

That is what a Klarsend link is. The recipient gets a short link; behind it sits a signed URL that Klarsend's resolver hands out on each open. Revoke the short link and new opens stop at once, on the free plan as much as on Premium, and the access log shows who opened it before you did. The honest limit, printed on the front page as well: the signed URL behind the link lives until its own expiry, so anyone who captured it before the revoke keeps it for that long. Keep expiries short when the stakes are high; the link form makes one hour the smallest choice for that reason.

See also the guides for Amazon S3 and Azure Blob Storage, the companion page on why presigned URLs expire after seven days, and the FAQ.

Get started

Bring the storage a client actually gave you.

Connect it, send a link, revoke it — in under ten minutes, with no card and no email address.

The core stays free. Premium is €6 a month, VAT included — pricing · refund policy.