Home/Integrations/ Storage/Google Cloud Storage
Send every recording to your Google Cloud Storage bucket.
Google Cloud Storage speaks the S3 API, so AddPipe treats it as an S3-compatible endpoint. Generate an HMAC key pair, paste it into AddPipe, and processed recordings land in your bucket automatically.
storage.googleapis.comNext to the rest of your data
If your analysis, transcription or ML pipeline already runs on Google Cloud, the recording arrives where the work happens instead of needing a copy step.
Your buckets, your rules
Lifecycle policies, customer-managed encryption keys, retention locks and regional placement all stay yours. Turn on Do not store and AddPipe keeps nothing after processing.
Diagnosable
Every push attempt is written to the S3 storage logs with Google's response, so a mismatched key or an ACL conflict reads as an error rather than a missing file.
What lands in the bucket.
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, which is a convenient trigger for a Cloud Function.
Details.
Why does a Google bucket use the S3 form?
Google Cloud Storage exposes an S3-compatible interoperability API. AddPipe talks to it as an S3 endpoint, with storage.googleapis.com as the custom endpoint and an HMAC key pair in place of AWS keys.
What is an HMAC key and where do I create one?
It is an access key and secret pair for the interoperability API, created under Cloud Storage → Settings → Interoperability. Create it against a service account rather than your own user so it survives staff changes.
Uniform or fine-grained access control?
Either works. Uniform bucket-level access disables ACLs, so set the canned ACL in AddPipe to none. With fine-grained access you can use public-read to make recordings directly playable.
Can AddPipe stop keeping its own copy?
Yes. Enable Do not store on the environment and recordings go only to your bucket. Playback then reads from Google, so make the object public or sign the URL yourself.
The push failed. Where do I look?
The S3 storage logs show each attempt and the response Google returned. The usual causes are an HMAC key created on the wrong project, or a canned ACL set while the bucket uses uniform access.
Other places AddPipe can push to.
Record once, find it in GCS.
Pushing to your own storage is included in the 14-day trial. No card required.