Presigned URLs
A presigned URL is a normal web link to one file in a private bucket, with a built-in permission slip and an expiry time. Anyone who has the link can download that file (or upload it, if the link was made for uploading) until the link expires. After that, the link stops working. Nobody needs your keys, and the bucket stays private.
Think of it as a ticket: you sign it with your S3 credential, you decide how long it is valid, and the storage checks the ticket every time someone uses it.
When to use a presigned URL
Buckets are private by default: only your S3 credentials can read or write them. There are three ways to let other people get at files:
If you are unsure, use a presigned URL: it shares one file, for a limited time, and you can cut it off by revoking the credential that signed it.
How it works
- You create the link with a tool or your code, using your S3 credential. Nothing is sent to IBEE at this point; the link is calculated on your computer.
- You give the link to the person or program that needs the file.
- They open the link. IBEE Object Storage checks the signature, the expiry time and your credential’s permissions, then sends (or accepts) the file.
The IBEE portal has no “share link” button yet. Create presigned URLs with the AWS CLI or an S3 SDK, as shown below.
Before you begin
You need:
-
A bucket and the key (full name and path) of the file, for example
reports/2026-05.pdf. Keys are case-sensitive. See Create a bucket. -
An S3 credential for the bucket’s workspace, created under Organization → API Tokens → S3 Credentials. See API Credentials. Its permission level decides what links it can sign:
If the credential is limited to specific buckets, it can only sign links for those buckets.
-
Your S3 endpoint:
https://WORKSPACE-ID.blob.ibeestorage.com. It is shown as S3 Endpoint when you create the credential. -
The AWS CLI (version 2) for the command-line steps, or Python (boto3) or Node.js for the code examples.
Every tool needs the same three settings for IBEE:
Create a download link with the AWS CLI
Save your credential as a profile
Run these once. Replace the two keys with your S3 credential’s values.
aws s3 presign only makes download links. To make an upload link, use an SDK as shown in Upload links.
Create a download link in code
Create links on your server, where the secret key is safe — never in a browser or mobile app.
Upload links (PUT)
An upload link lets someone put one file, at the key you chose, into your bucket without credentials — for example, a user uploading a profile picture straight from your web page.
IBEE Object Storage only accepts an upload link that was signed together with the file’s MD5 checksum, a short fingerprint of the file’s exact contents. This proves the file that arrives is the file you allowed. So:
- Get the file’s MD5 checksum before you create the link. In a web app, the browser calculates it and sends it to your server with the file name.
- Create the link with the checksum (
ContentMD5). - Upload with the same checksum in a
Content-MD5header.
Calculate the checksum (base64-encoded MD5):
Create the upload link:
The person with the link uploads the file in one request, sending the same content type and checksum:
Before you hand out upload links:
- The headers must match what was signed. The upload must send exactly the
Content-TypeandContent-MD5the link was created with, or it fails withSignatureDoesNotMatch. - The file must match its checksum. A different or changed file fails with
BadDigest. Create a new link for each file. - An upload replaces any file with the same key. Use a unique key per upload (for example, include a random ID) if files must not overwrite each other.
- One link, one file. Each upload link is for one key.
Uploading from a web page
A browser only allows the upload if the bucket’s CORS rules allow your website. Add a rule that allows your site’s origin, the PUT method, and the Content-Type and Content-MD5 headers. See CORS.
Browser form uploads (presigned POST with an upload policy) are not supported. Use a presigned PUT link instead.
How long a link lasts
A link stops working before its expiry time if the S3 credential that signed it is revoked or deleted. This takes effect immediately, for every link that credential signed.
A download link points to a key, not to one copy of the file: if the file is replaced, the link returns the new file; if it is deleted, the link returns NoSuchKey. The expiry is checked when a request starts, so a download that started before the expiry time finishes.
Choosing an expiry
Shorter is safer: anyone who gets hold of the link can use it until it expires.
What’s in a presigned URL
Your secret key is never part of the link.
Security tips
- Treat a link like a password. Anyone who has it can use it until it expires. Don’t post it publicly or write it to logs.
- Use the shortest expiry that works, and create a fresh link for each request instead of reusing one.
- Sign with a narrow credential: use Object Read only for download links and limit the credential to the buckets it needs.
- Create links on a server. Never put an S3 secret key in a web page, mobile app or public repository.
- To cut off every link at once, revoke the credential that signed them, then create a new credential for your app.
Troubleshooting
Errors come back as XML with a Code and a Message. Look up the message:
Related pages
- API Credentials: create and revoke S3 credentials
- Bucket Policies: public access and permission levels
- CORS: allow uploads and downloads from a web page
- Objects: upload and download with your own credentials
