Home/Integrations/ Storage/Amazon S3
AddPipe Amazon S3 Integration
Push recordings to Amazon S3 storage. AddPipe automatically sends your recordings and associated files to your Amazon S3 bucket or other S3-compatible services, so you can streamline your workflow on AWS's scalable, secure and globally accessible storage infrastructure. Four simple steps, no code.
Seamlessly store and manage your recordings in the cloud.
Whether you're using AddPipe as an online video recorder to record videos with a webcam, capturing screen recordings for tutorials, or managing large media projects, this integration simplifies your workflow. Ideal for developers, businesses and content creators, AddPipe makes recording a video and storing it in the cloud effortless.
The recording is yours from the start
Files land in your account, under your lifecycle rules, your encryption settings and your retention policy. Turn on Do not store and AddPipe keeps nothing after processing.
Scoped access, not a master key
Limit the IAM user to the essential S3 actions, lock it to one bucket and, for added security, to Pipe's production server IPs.
Comprehensive logging
Track every push attempt in the S3 logs, including status, exceptions and Object URLs, available for 30 days in your AddPipe dashboard.
Key features.
private, public-read) to set permissions on your files, tailoring access to your needs.Benefits.
Getting started in 4 simple steps.
Setting up AddPipe with Amazon S3 is quick and straightforward. For detailed instructions with screenshots, check out our documentation.
s3:PutObject and s3:AbortMultipartUpload (see the policy below), then retrieve the Access Key ID and Secret Access Key.A minimal IAM policy.
PutObject and AbortMultipartUpload cover uploads, including multipart uploads for recordings over 100 MiB. Add PutObjectAcl if you set a canned ACL.
{ "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": [ "s3:PutObject", "s3:PutObjectAcl", "s3:AbortMultipartUpload" ], "Resource": "arn:aws:s3:::my-recordings/*", // optional: only accept pushes from AddPipe's servers "Condition": { "IpAddress": { "aws:SourceIp": [ "162.55.182.247", // EU2 "168.119.177.143", // EU3 "167.99.173.235", // US1 west "68.183.96.15" // US2 east ] } } }] }
Security considerations
IAM permissions
Limit your IAM user to essential actions (e.g. s3:PutObject, s3:AbortMultipartUpload) for a secure setup.
Bucket configuration
Adjust Object Ownership and Block Public Access settings to control file accessibility, and use bucket policies for cross-account pushes.
Best practices
Restrict IAM policies AddPipe's production server IPs for added security.
What lands in the bucket.
Your recordings and associated files, all sharing the recording's name.
Which files 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, so your application can reference the file the moment it exists.
Who can benefit from AddPipe's video recording software?
Whether you're recording a screen, recording video cam footage, or recording audio, AddPipe's S3 integration enhances your operations across industries.
FAQ.
How do I make my recordings publicly accessible?
Set the canned ACL to public-read in AddPipe's S3 settings to allow access to video recordings and audio recordings via Object URLs. On the bucket, set Object Ownership to ACLs enabled and uncheck Block all public access so the ACL can take effect.
Does this work with other cloud providers?
Yes, AddPipe supports S3-compatible services like DigitalOcean Spaces, Google Cloud Storage and Cloudflare R2, making it a flexible video recorder software.
What happens if a push fails?
AddPipe will automatically retry failed uploads, using exponential backoff. Check the S3 logs in your AddPipe dashboard for status and exceptions to troubleshoot issues. Logs are available for 30 days.
Which IAM permissions does AddPipe need?
Limit your IAM user to essential actions: s3:PutObject to upload and s3:AbortMultipartUpload for recordings over 100 MiB, plus s3:PutObjectAcl if you set a canned ACL. AmazonS3FullAccess works but grants far more than necessary.
Can I restrict the IAM user to AddPipe's servers?
Yes, and it is recommended. AddPipe pushes from four production addresses: 162.55.182.247 and 168.119.177.143 in the EU, 167.99.173.235 and 68.183.96.15 in the US. Add them as an aws:SourceIp condition, as in the policy above.
Can AddPipe stop keeping its own copy?
Yes. Enable Do not store on the environment and recordings go only to your bucket, never to AddPipe storage. The setting applies to future recordings, not retroactively.
What if I need help integrating?
Integrating AddPipe? Contact us directly, we are happy to help. Building something beyond AddPipe? For custom web and product development, reach out through the form on the custom development page, and we will get back to you with one of our development partners.
Other places AddPipe can push to.
Sign up for a 14 Day Trial
Add audio, video and screen recording to your website and explore the AddPipe Platform for 2 weeks with our 14 days trial. No credit card required.
