Set up once. Ship forever.
Connecting a cloud takes a couple of clicks in your own tenant. After that, getting a file into storage is a single pasted command — on any machine, with nothing installed.
Connect your cloud — one click
In the dashboard, pick AWS or Azure and follow a one-click flow that runs entirely in your tenant. No long-lived keys ever leave your account.
- AWS: a Launch Stack link creates an IAM role scoped to your bucket, trusting BlobShip via AssumeRole with a unique external ID. You stay in control; revoke by deleting the role.
- Azure: grant access to your storage account so BlobShip can mint User Delegation SAS on demand — short-lived, write-scoped, revocable.
In the dashboard
One-click setup runs in your tenant. BlobShip never receives a standing secret.
Copy your one-liner
The dashboard generates the exact command with your API key already in it. Pick your OS, copy it, and store it in your notes. The endpoint and key stay the same — only the filename changes per upload.
$ curl -fL -H "x-api-key: blsh_live_xxxx" https://blobship.io/ship/ -T db_backup_202606101052.sql Ship a file
Paste the command on any box that has curl and internet access — a bastion, an RDP session, a customer's server. Swap in your filename and hit enter.
The same line works everywhere; on Windows just use
curl.exe so PowerShell doesn't hijack it with
its Invoke-WebRequest alias.
What happens under the hood
Your key is checked
x-api-key. The
broker validates it and the target connector — control data only.
A credential is minted
307 → direct upload
Ready to ship?
Connect a cloud and send your first files free. Setup is a couple of clicks.