Skip to main content

Upload an EMEA Data File via LiveRamp's AWS S3 Bucket

Follow the steps below to upload an EMEA data file via LiveRamp's AWS S3 bucket, either with an S3 client or by using AWS Command Line Interface (CLI). For information on formatting files for EMEA data, see "Creating Data Files for EMEA Countries".


  • When you're uploading the first file to an audience, you'll need to contact your LiveRamp representative so we can make sure your file is imported correctly. Depending on the type of audience and your situation, you might need to do this before uploading your first file or after (or both). See "Considerations When Uploading the First File to an Audience" for more information.

  • Uploading with WinSCP? Make sure not to send files with an extension of ."filepart", as our system will not process these files (and you will see the error "Cannot create remote file 'uploads/filename.csv.filepart.' Permission denied.", or something similar). To disable the feature in WinSCP that might be giving your files a ."filepart" extension, see these instructions.


Next Steps

Upload with an S3 Client

You can use most S3 clients to upload EMEA data files to LiveRamp’s AWS S3 bucket, including the following:

  • Cyberduck

  • S3 Browser

  • Terminal supports upload via AWS CLI commands

  • CloudBerry

  • Other S3 Clients that enable you to upload files

Follow the steps below to upload an EMEA data file via LiveRamp's AWS S3 bucket with an S3 client.

  1. Make sure that the file is formatted correctly and not password-protected.

  2. If using a firewall, enable outgoing port 443.

  3. Sign in to your S3 client.


    LiveRamp recommends Cyberduck, a free client that works on Mac and PC.

  4. In the "Host" field, enter "".

  5. Enter the username and password given to you by your LiveRamp representative.NoteContact your LiveRamp representative (or your reseller representative, if appropriate) for S3 credentials if you haven't been given them yet, or if you need to have your password reset.

  6. Upload the file to the "/uploads" directory, or to the subdirectory for the audience you’re uploading the file to (if you have more than one audience).


Need a walkthrough? See the section below for a walkthrough to guide you through the S3 file upload process via Cyberduck.

If the file does not appear in Connect within 3 days, contact your LiveRamp representative to confirm that the file uploaded correctly.

Cyberduck Upload Walkthrough

Follow these steps to upload EMEA data files via LiveRamp's AWS S3 with Cyberduck:

  1. Download the Cyberduck client.

  2. Open Cyberduck.

  3. Click Open Connection.

  4. Click into the connection type drop-down list and select “Amazon S3"

  5. Enter the following information:

    • Server:

    • Port: 443

    • Access Key ID: Your access key ID (given to you by your LiveRamp representative)

    • Secret Access Key: Your secret access key (given to you by your LiveRamp representative)

  6. If you want Cyberduck to remember your credentials next time, check the "Add to Keychain" check box.

  7. Click Connect.

  8. Once the connection has been made, select the upload location:

    1. Click Go at the top of the navigation bar and then select “Go To Folder”.

    2. Enter the path "com-liveramp-eu-customer-uploads/" followed by your customer ID (provided by your LiveRamp POM or obtained from the URL in Connect).

    3. If you’ve discussed using a subfolder with your POM, include a subfolder.

    4. Click Go.

    A successful connection will look like this:

  9. To access your folder, select "Go" at the top bar and then select "Go To Folder". Then enter the path again followed by your customer ID (provided by your POM; . Include a sub-folder if you have discussed this with your POM. See below for an example where the customer ID is 1001 (do not use 1001 as your customer ID):

  10. Upload your files using one of the methods listed below:

    • Drag and drop the files from your computer into the Cyberduck window.

    • From the File tab, select "Upload" and then select the desired file(s).

    • Click the "Action" button, select "Upload", and then select the desired file(s).

    A successful upload looks like the example below:

  11. When you're finished uploading, click Disconnect.

Automating File Upload with the AWS Command Line

Depending on your tech stack, you may wish to use commands available via the AWS Command Line Interface to generate a script that will automate file uploads to our S3. Currently, this automation must occur client-side, though it is a long-term roadmap item to enable LiveRamp to automatically pull files from client servers in the EU.

The AWS Command Line Interface is the easiest and preferred way to automate uploads.

Follow these instructions if you wish to automate your file deliveries utilizing Amazon’s Command Line Interface:

  1. Install AWS CLI by following these official instructions to install the utility on Windows, Linux, or Mac.

  2. Configure the AWS utility with the credentials provided by your POM to put the access key that was given to you in a file accessible by the AWS command line utility (for more information, see this AWS CLI article.

    The easiest way to do that is to open a command line prompt and enter "aws configure".

    Make sure to specify a profile if you don't wish to override an existing one. For example, to create a "liveramp" one, enter "aws configure --profile liveramp".

    Enter the following parameters:

    • AWS Access Key ID [None]: Your access key ID

    • AWS Secret Access Key [None]: Your secret access key

    • Default region name [None]: eu-west-1

    • Default output format [None]: json

  3. After the utility is configured, use AWS CLI to automate file uploads by entering the following command:

    aws s3 cp <file> s3://com-liveramp-eu-customer-uploads/<Your customer number>/

    If you created a specific profile (for example, the "liveramp" one from above), you need to specify it, like this:

    aws --profile liveramp s3 cp <file> s3://com-liveramp-eu-customer-uploads/<Your customer number>/

    This type of command can be used in a script that runs on a cron (or some other triggering mechanism) to generate and upload new files from your machine.