Connect to Amazon S3

Keep your S3 data in the same AWS region as your StarTree cluster. For BYOC deployments, StarTree creates an S3 gateway endpoint in your cluster’s region, so reads from buckets in that region stay on the AWS private network. A gateway endpoint does not cover buckets in other regions. Reads from those buckets go through your VPC’s NAT Gateway (node → NAT Gateway → Internet Gateway → public S3 endpoint). For large datasets, the NAT Gateway processing charges show up on your AWS bill and can be significant. A one-time read may not justify moving the data, but the charges from repeatedly reading a large dataset add up quickly.If the bucket has to stay in a different region, set up a cross-region S3 interface endpoint (AWS PrivateLink) before you onboard the data. See Networking and data transfer costs for details.

In the Data Portal, click Tables and then click Create Table.

Select S3 as the Data Source.

Create a New Connection.

Click New Connection. If you want to use an existing connection, select the connection from the list and proceed to Step 5.Enter a Source Name for the new connection.Select the Authentication Type from the drop-down list.

Configure Connection Parameters.

Connecting to S3 Using Basic Authentication

Use the following JSON configuration when S3 is set up with basic authentication using an access key and secret key.

{
  "inputDirURI": "s3://<BUCKET_NAME>/<PATH>/",
  "input.fs.prop.region": "<REGION>",
  "input.fs.prop.accessKey": "<ACCESS_KEY>",
  "input.fs.prop.secretKey": "<SECRET_KEY>"
}

Property Descriptions

Property	Required	Description
`inputDirURI`	Yes	URI of the input directory/files for ingestion. It tells Pinot where the data resides.
`input.fs.prop.region`	Yes	Region of the file system (e.g., `us-east-1`).
`input.fs.prop.accessKey`	Yes	Access key for authentication to the file system.
`input.fs.prop.secretKey`	Yes	Secret key for authentication (paired with access key).

Connecting to S3 Using IAM-Based Authentication

Please follow these steps to create IAM role for S3 setup.Use the following JSON configuration when S3 is set up with IAM-based authentication by assuming an IAM Role for secure access.

{
  "inputDirURI": "s3://<BUCKET_NAME>/<PATH>/",
  "input.fs.prop.roleArn": "arn:aws:iam::<AWS_ACCOUNT_ID>:role/<ROLE_NAME>",
  "input.fs.prop.region": "<REGION>",
  "input.fs.prop.externalId": "<EXTERNAL_ID>",
  "input.fs.className": "org.apache.pinot.plugin.filesystem.S3PinotFS"
}

Property Descriptions

Property	Required	Description
`inputDirURI`	Yes	URI of the input directory/files for ingestion. It tells Pinot where the data resides.
`input.fs.prop.region`	Yes	Region of the file system (e.g., `us-east-1`).
`input.fs.prop.externalId`	Yes	External ID of the AWS Account of your StarTree Cloud.
`input.fs.prop.roleArn`	Yes	The Amazon Resource Name (ARN) of an AWS IAM role to assume for accessing AWS S3. Allows Pinot to securely access resources in different AWS accounts. Example Use Case: If Pinot is running in Account A but the S3 bucket is in Account B, you can assume a role in Account B that grants access to the bucket. The role must have permissions like “s3:List*” and “s3:GetObject” for proper access.
`input.fs.className`	Yes	The file system implementation class to access the input directory. Examples: - `org.apache.pinot.plugin.filesystem.S3PinotFS` (for Amazon S3) - `org.apache.pinot.plugin.filesystem.LocalPinotFS` (for local file systems) - `org.apache.pinot.plugin.filesystem.HadoopPinotFS` (for HDFS)

Test the Connection and Configure Data Ingestion.

After you have configured the connection properties, test the connection to ensure it is working.

Configure Data Ingestion

When the connection is successful, use the following JSON to configure additional data settings:

{
  "inputFormat": "",
  "includeFileNamePattern": "",
  "excludeFileNamePattern": ""
}

Property Descriptions

Property	Required	Description
`inputFormat`	Yes	The format of the input files. Supported values include csv, json, avro, parquet, etc.
`includeFileNamePattern`	Yes	The glob pattern to filter which files to include for ingestion. Used when the input directory contains mixed files and only specific files should be ingested.
`excludeFileNamePattern`	No	The glob pattern to filter which files to exclude from ingestion. Used when the input directory contains mixed files and only specific files should not be ingested.

Configure Record Reader

Configure the record reader to customize how the file format is read during ingestion.

CSV

The CSVRecordReaderConfig is used for handling CSV files with the following customizable options:

header: Provide a header when the input file has no headers.
skipHeader: Provide an alternate header when the input file has a corrupt header.
delimiter: Use an alternate delimiter when fields are not separated by the default delimiter comma.
skipUnParseableLines: Skip records that are not parseable instead of failing ingestion.

Example: Provide a header when the input file has no headers.

{
  "header": "colA,colB,colC"
}

Example: Provide an alternate header when the input file has a corrupt header.

{
 "header": "colA,colB,colC",
 "skipHeader": "true"
}

Example: Use an alternate delimiter when fields are not separated by the default delimiter comma.

{
 "delimiter": ";"
}

{
  "delimiter": "\\t"
}

Example: Skipping records that are not parseable instead of failing ingestion. This option to be used with caution as it can lead to data loss.

{
  skipUnParseableLines: "true"
}

Example: Handling CSV files with no header, tab-separated fields, empty lines, and unparsable records.

{
  "header": "colA,colB,colC",
  "delimiter": "\\t",
  "ignoreEmptyLines": "true",
  "skipUnParseableLines": "true"
}

For a comprehensive list of available CSV record reader configurations, see the Pinot CSV documentation.

AVRO

One configuration option AvroRecordReaderConfig is supported.

enableLogicalTypes: Enable logical type conversions for specific Avro logical types, such as DECIMAL, UUID, DATE, TIME_MILLIS, TIME_MICROS, TIMESTAMP_MILLIS, and TIMESTAMP_MICROS.

{
  "enableLogicalTypes": "true"
}

For example, if the schema type is INT, logical type is DATE, the conversion applied is a TimeConversion, and the value is V; then a date is generated V days from epoch start.

Parquet

For Parquet files, Data Manager provides the ParquetRecordReaderConfig with customizable configurations in Data Manager.Use Parquet Avro Record Reader:

{
    "useParquetAvroRecordReader" : "true"
}

When this config is used the parquet record reader used is: org.apache.pinot.plugin.inputformat.parquet.ParquetAvroRecordReaderUse Parquet Native Record Reader:

{
    "useParquetNativeRecordReader" : "true"
}

When this config is used the parquet record reader used is: org.apache.pinot.plugin.inputformat.parquet.ParquetNativeRecordReader

Preview the Data

Click Show Sample Data to preview the source data before finalizing the configuration.

Next Step

Proceed with Data Modeling.

Get Started

Ingestion

External Tables

Query Data

Manage Data

Observability

Visualize Data

Cluster Operations

Manage Security

Release Notes

Reference

Connecting to S3 Using Basic Authentication

Property Descriptions

Connecting to S3 Using IAM-Based Authentication

Property Descriptions

Configure Data Ingestion

Property Descriptions

Configure Record Reader

Next Step

​Connecting to S3 Using Basic Authentication

​Property Descriptions

​Connecting to S3 Using IAM-Based Authentication

​Property Descriptions

​Configure Data Ingestion

​Property Descriptions

​Configure Record Reader

Next Step

Connecting to S3 Using Basic Authentication

Property Descriptions

Connecting to S3 Using IAM-Based Authentication

Property Descriptions

Configure Data Ingestion

Property Descriptions

Configure Record Reader