Home/Integrations/ Storage/DigitalOcean Spaces
Push every recording to your DigitalOcean Space.
Spaces is S3-compatible, so AddPipe treats it as an S3 endpoint. Generate a key pair, choose the endpoint for your region, and processed recordings land in the Space automatically.
<region>.digitaloceanspaces.comPredictable pricing
Spaces bundles storage and a generous transfer allowance into a flat monthly price, which suits recording workloads where playback traffic is hard to forecast.
A CDN in front, at no extra step
Turn on the Spaces CDN and the same object is served from the edge. AddPipe writes to the origin, so nothing about the integration changes.
Diagnosable
Every push attempt is written to the S3 storage logs with DigitalOcean's response, so a wrong region endpoint reads as an error rather than a missing file.
Endpoints by region.
Enter the hostname only. No https://, and no Space name in front of it.
What lands in the Space.
Up to five files per recording, all sharing the recording's name.
Which of the five are produced is set per environment in the Transcoding Engine. Your webhook receives a video_copied_s3 event with the object path once the push completes.
Details.
Which endpoint do I use?
The one matching your Space's region: ams3.digitaloceanspaces.com for Amsterdam 3, nyc3.digitaloceanspaces.com for New York 3, sfo2.digitaloceanspaces.com for San Francisco 2, sgp1.digitaloceanspaces.com for Singapore 1. Enter it without the Space name and without https://.
Where do I create the key pair?
In the DigitalOcean control panel under Spaces → Manage Keys → Generate New Key. You get a Key and a Secret; the Secret is shown once.
Should the files be private or public?
Choose the canned ACL in AddPipe. Use public-read if you want recordings playable straight from the Space, or private and serve them through your own signed URLs.
Does the Spaces CDN work with this?
Yes. Enable the CDN on the Space and serve the mp4 from the CDN hostname. AddPipe writes to the origin, so nothing about the push changes.
The push failed. Where do I look?
The S3 storage logs show each attempt and DigitalOcean's response. The usual cause is an endpoint for the wrong region, or the Space name repeated in both the bucket field and the endpoint.
Other places AddPipe can push to.
Record once, find it in your Space.
Pushing to your own storage is included in the 14-day trial. No card required.