1. Socialive Support Center
  2. Articles home
  3. Admin Portal
  4. Integrations

Integrations: Connecting Your AWS S3 Bucket

This article provides instructions to connect your AWS S3 Bucket to Socialive. Integrating AWS to Socialive allows you to send Socialive recordings directly to your S3 Bucket.


To connect an AWS S3 Bucket to Socialive, you need to:

  • Have access to an AWS S3 Bucket
  • Be an Administrator in your Socialive account


  1. In Socialive, click your initials to open the Settings menu.
  2. In the Settings menu, click Integrations.
  3. On the Integrations page, click Add Integration.
  4. Click AWS S3.
  5. Give the integration a name (or use the default one) and click Save. Giving each integration a specific title may be useful when creating integrations of the same type for different departments. For example “Send to Marketing AWS S3 Bucket” versus the default “Send to AWS S3.”
  6. Click New Authentication.
  7. Enter a name for your new authentication.
  8. Enter the Access Key and Secret Key and click Create.
  9. A notification will appear to confirm the authentication was successfully created. Click Next.
  10. Select the target bucket from the drop-down list and click Finish. Now you can send Socialive recordings to your AWS S3 bucket.

Sending Recordings to AWS S3

Follow the steps in the article to send recordings to your AWS S3 bucket. When you send recordings to AWS S3:

  • You will receive email notifications when the upload is completed.
  • The transfer times may vary depending on the file size but most files will be uploaded within 15 minutes.

Still looking for an answer?

Contact Socialive Support via live chat, email at support@socialive.us, or submit a support ticket.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article