Amazon S3 / Amplitude Integration – Amplitude

The Amazon S3 data destination allows teams to export their Amplitude data to an Amazon S3 bucket. This enables users to analyze their Amplitude data alongside other organization sources of data that users might not have within Amplitude. Oftentimes, behavioral data needs to be analyzed alongside other organizational sources of data that aren’t captured within Amplitude.

What you will learn in this article

Teams are now able to set up exports of their event data to any of their own Amazon S3 buckets directly from within the Amplitude UI. This article represents a guide that will walk users thought setting up the Amazon S3 destination in Amplitude.

Prerequisites

This feature is available to all paying customers
The ability to export merged Amplitude IDs along side the raw event data is currently disabled as some infrastructure work still needs to be complete
Once setup, event data will be automatically exported on an hourly basis to the bucket
Currently Portfolio Projects cannot be used as data sources for the Amazon S3 export

How it Works
Setup
- Manual Exports
- Manage
FAQs

How it Works

The export works on a per project basis, teams having the flexibility to setup data from one project to to go multiple buckets, or use multiple projects to export event data into the same Amazon S3 bucket.

In addition to automatic hourly exports, teams can also backfill historical event data for any date range (Manual Export). The status of both hourly jobs and backfill jobs can be monitored from the Amplitude UI.

Please note that while Amplitude does allow multiple projects in the same org to access the same bucket, we do not allow multiple orgs to access the same bucket. This is for security purposes. If you have more than one org to export data into Amazon S3, you will need more than one S3 bucket.

Setup

To setup the Amazon S3 integration users will have to navigate to the Sources&Destinations menu:

Once the Sources & Destinations menu is accessed, select the Destinations options:

To add the Amazon S3 as destination, click the Add Destination button at the top right corner in the UI:

Here users have visibility over all the available destinations or can use this interface to request new destinations. Select the Amazon S3 destination to start setting it up:

Selecting the Amazon S3 destination will open a menu where users can start setting up the export:

You have a choice of exporting events ingested today and moving forward, or exporting all merged AmplitudeIDs (feature not yet available). Once the data for export is selected, the Bucket Policy has to be set up:

After setting up the Bucket Policy, users can finish setting up the Amazon S3 export, by verifying the Bucket Access:

Hourly Automatic Exports begin immediately when users finish the step-by-step wizard flow.

Manual Exports

To backfill historical data to S3, you can manually export data by selecting a range of UTC dates, and then click the 'Start Export' button:

Once setup is completed, users can check the status of their Automatic Exports and Manual Exports:

Manage

Users have the option to disable the automatic exports inside the Manage modal:

FAQs

How long does it take for the export to complete?

The export will finish within one hour after the currently exported hour. The export time is typically between 1 and 10 minutes.

What potential errors might occur, and how will I be alerted to them?

The only potential error is an accessibility error. This can happen if you have changed any configurations (on the receiving end), and we are unable to access to your bucket. In this case, the export will fail after several tries, and the Admin and the user who created the S3 export will be notified via email.

How do I troubleshoot errors?

Troubleshooting information is not available within the Amplitude UI, but information will be provided in the error email. Because the accessibility is the only error that we can potentially run into, the email will include information on which permission is missing.

Is there a limit in size or date range when backfilling historical event data (via manual exports)?

No. If for any reason you are unable to export a certain date range, please confirm that you have event data for that date range and submit a ticket to our support team.