--- title: "Amazon S3 channel" slug: "amazon-s3-channel" updated: 2026-04-27T19:20:50Z published: 2026-04-27T19:20:50Z --- > ## Documentation Index > Fetch the complete documentation index at: https://help.quickbase.com/llms.txt > Use this file to discover all available pages before exploring further. # Amazon S3 channel > *Go to the*[*Channels*](https://team.quickbase.com/nav/main/action/pipelines/channels)*page to learn more about what plans have access to this channel. Sign into Quickbase, and then go to Pipelines > Channels.* Amazon S3 (Amazon Simple Storage Service) allows you to store and retrieve any amount of data, at any time, from anywhere on the web. It gives any developer access to the same highly scalable, reliable, fast, and inexpensive data storage infrastructure that Amazon uses to run its own global network of websites. Visit [https://aws.amazon.com/](https://aws.amazon.com/) to learn more. > [!NOTE] > Note: The AWS channel is only available if you are on the Enterprise Plan. ## How to connect 1. On the My pipelines page, select **Create Pipeline**. 2. Search for or select a step, and then select it to add it to the pipeline. When you add a step to a pipeline, it is added to the canvas of the pipeline designer. 3. Expand the Connection section of the step, and add the required information. ### Connect to Amazon S3 1. Expand **Amazon S3** in the list of channels on the right side of the page and select **Connect to Amazon S3**. 2. In the pop-up window, select **Connect to Amazon S3**. ![Connect to Amazon S3 dialog with Connect to Amazon S3 button](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471431929236.png) 3. You will be asked to enter your AWS Access Key ID, AWS Server Secret Key, and AWS Region as required fields, and then select **Sign in**. To get your AWS Access Key ID and AWS Server Secret Key: 1. Go to your Amazon profile. On the upper right side of the page, select your username dropdown, and then select **My Security Credentials**. ![AWS console with username dropdown showing My Security Credentials option](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471424904084.png) 2. Select **Access keys (access key ID and secret access key)**. 3. To get your Server Public Key, copy the Access Key ID. ![AWS IAM security credentials page showing Access Key ID field](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471306997524.png) 4. To get your Server Secret Key, select **Create New Access Key** and follow the instructions. ### Regions Region isn't directly specified on a key, instead you specify it through the connection.​ To find the region codes, select **Global** in the top left, type in your chosen code in the Pipelines credentials​: ![Pipelines credentials page showing Global region selector and code entry field](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471414397460.png) For more information about regions, see [Regions and Zones](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html). ## How to reconnect You may need to reconnect your account to a channel. Reasons may be (but not limited to): - If you need to connect a different account. - Authorization updates, such as a changed password. - Editing the access rights that Pipelines has to the channel. To reconnect: 1. Select a pipeline that already has this channel in it. 2. Open a step that contains this channel. 3. Under account, select **Connect (or reconnect)** and follow the [connection steps](/v1/docs/amazon-s3-channel#how-to-connect) above. ![Pipeline step editor showing Connect (or reconnect) option under account settings](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/17571087364628.png) ## Steps The steps you can use with Amazon S3 fall into one category: Objects | Type | Name | Description | | --- | --- | --- | | Objects | | | | Action | Upload an Object | Uploads an Object into S3 Bucket. The limit for the object is 100MB. | | Action | Delete an Object | Delete the selected object. An object look-up should be done in the previous step. | | Action | Look Up an Object | Returns a single Object for the selected account. It is used when you wish to download or transfer a file. Look Up an Object searches for a single object given the bucket's name containing it and the object's name as a key. This action will return `content_url` / `file_transfer_handle`. | | Query | Search Objects | Searches the selected account for files and returns a list. Search Object searches for objects given many parameters: id, key, type, bucket, updated at, size, content type, browser url, file transfer handle or (advanced) expression handle. The query will return a list that satisfies the search conditions. | ## Limits - Currently we do not support working with buckets from different regions. - Individual Amazon S3 objects can range in size from a minimum of 0 bytes to a maximum of 100MB. The largest object that can be uploaded is 100MB. ## Use cases ### Quickbase file transfer to Amazon S3 Bucket It would be convenient every time we create a record containing a file, to transfer that file to our Amazon S3 Bucket. Let's create a pipe that checks if the created record contains an existent file. If the file exists, then it is transferred to our Amazon S3 Bucket. Otherwise, the pipe does nothing. In the following example, we will show you step-by-step how to create this pipeline. 1. Drag and drop the Record Created Trigger from the Quickbase channel and attach it to the pipe. ![Pipeline designer canvas with Quickbase Record Created Trigger connected to the pipeline](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471424976148.png) **Account**—from your existing Quickbase profile select the auth token which is connected to the Quickbase tables you want to operate with **Table**—select an existing table from your Quickbase profile, which records contain files **Fields for Subsequent Steps**—select the table fields 2. Select **Insert a condition** ![Pipeline designer showing Insert a condition option](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471424998548.png) After this step you should have these fields: ![Pipeline designer showing condition fields after inserting a condition step](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471414422164.png) 3. Select **Add conditions** → **Record** and select **File**->**File transfer handle** ![Pipeline condition builder with Record and File transfer handle selected](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471307021844.png) Set the condition to **is set** ![Pipeline condition set to is set for File transfer handle field](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471414433300.png) 4. Connect to your Amazon S3 account. Type your account ID under the **Account** heading and then type the bucket's name that you would want to use under the **Bucket** heading. After that drag the **File transfer handle** and **File name** bubbles respectively under the **URL** and **File name** headings. ![Amazon S3 pipeline step showing Account, Bucket, URL, and File name configuration fields](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471439576596.png) 5. Leave the Else clause empty 6. After triggering the pipeline in your Activity log you should have: ![Pipeline activity log showing successful file transfer results](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471439617556.png) When you create a record containing a file, the expected result is to transfer that file to the Amazon S3 Bucket. ![Quickbase record showing file successfully transferred to Amazon S3 Bucket](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471412791572.png) ### Transfer CSV file from AWS S3 to Quickbase table Let's create a pipeline that gets a CSV file from AWS S3 and uploads it into a Quickbase table. In the following example, we will show you step-by-step how to create this pipeline. The test.csv file contains three columns—firstname, lastname, and email. This could be any kind of file, Excel, etc., but in this case, it is a CSV file. 1. Connect to your Amazon S3 account. Drag and drop the Look Up an Object Action from the Amazon S3 channel and attach it to the pipeline. Choose your account ID under the **Account** heading and then select the bucket that you would want to use under the **Bucket** heading. Under the **Query** heading select **Key**, **equals** and then fill in the name of the CSV file you would like to transfer to a Quickbase table. Do not forget to include your file extension as well when specifying the name. ![Amazon S3 Look Up an Object step with Key query for CSV file lookup](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471425175700.png) 2. Connect to your Quickbase account. Drag and drop the Import with CSV Action from the Quickbase channel and attach it to the pipeline. Under the **Account** and **Table** headings select your Quickbase account, and respectively the target table in Quickbase where the data will be imported. Under **Merge Field** select **Record ID#**. After that drag the **File transfer handle** bubble under the **CSV URL** heading. ![Quickbase Import with CSV step showing account, table, and field mapping configuration](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471425199124.png) Select the appropriate fields in the Quickbase table to match the columns in the test.csv file in the **Field to map to column** sections. 3. After triggering the pipeline in your Activity log you should have: ![Pipeline activity log showing successful CSV import results](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471439733780.png) When you run the pipeline, the expected result is to transfer the information from that csv file to the selected Quickbase table. ![Quickbase table showing data imported from CSV file](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471412857876.png) ### Dynamically select the file using Jinja Let's say you are building an AWS S3 pipeline and want to dynamically select the file that has the file name suffix that corresponds to today's date (YYYYMMDD), using Jinja. In this example, we have three CSV files in there and want our scheduled pipeline find the file that matches today's date. - logdata_20211109.csv - logdata_20211108.csv - logdata_20211107.csv We use this jinja in our query field: ```plaintext logdata_{{time.today|date_ymd('')}}.csv ``` Like this: ![Amazon S3 pipeline step query field showing Jinja expression for dynamic date-based file selection](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/4471425298836.png) ### Log data from S3 to a Quickbase app The following video walks through moving S3 log data to an existing Quickbase app: