Amazon S3

What is Amazon S3?

Amazon S3 (Simple Storage Service) is an Amazon Web Services storage service that enables durable storage and retrieval of any amount of data, organized into buckets and accessible from anywhere on the web.

Amazon S3 delivery is for teams that want automated dataset delivery into their AWS environment for ingestion, warehousing, or downstream processing.

Available formats and delivery schedule

Coresignal can deliver flat files to S3 in formats that vary by dataset and cadence. Supported flat-file formats across Coresignal datasets include JSONL, Parquet, and CSV.

How to connect Coresignal to Amazon S3?

Coresignal supports two common S3 setup methods.

Access key setup

For a standard S3 delivery setup, we need the following:

• Bucket name

• AWS Access Key ID

• AWS Secret Access Key

1

Create or select an S3 bucket to receive Coresignal files.

2

Create credentials with permission to upload files into that bucket.

3

Share the following with Coresignal

Provide the following information:

• Bucket name

• AWS Access Key ID

• AWS Secret Access Key

4

Coresignal will conduct a test upload to confirm access.

5

Once verified, we configure the agreed-upon delivery schedule and file path.

IAM role setup

Coresignal also supports cross-account, IAM role-based S3 delivery. In this setup, you create a role in your AWS account and authorize Coresignal’s role to assume it.

1

Create or choose an S3 bucket in your AWS account.

2

Create an IAM role for file uploads.

3

In that role’s trust policy, allow Coresignal’s role ARN to assume the role.

4

Attach a policy that allows s3:PutObject on your bucket path.

5

Share the following with Coresignal

Provide details:

• Client IAM role ARN

• Bucket name

• AWS region

6

Coresignal will perform a test upload to verify the configuration.

Verifying delivery

Once the first files land, check:

• Expected bucket/prefix – confirm that files arrived in the agreed folder path.

• File readability – confirm that files can be downloaded, decompressed, and parsed.

• Permissions and access – confirm that your team can read the uploaded objects in your AWS account.

• Delivery completeness – if this is a recurring feed, confirm that the first delivery includes the expected date folder and a non-zero file count.

FAQ

Files aren't showing up in our bucket – what should we check first?

Ensure that your credentials or IAM role haven't expired or been rotated, and verify that the bucket policy still provides the necessary permissions. Also confirm that the bucket name and region given to Coresignal match exactly.

What if we rotate our Access Key or update our IAM role?

Notify your account manager as soon as the new credentials or role ARN are ready so the pipeline can be updated without missing a scheduled delivery.

Can I have separate buckets for different datasets?

Yes, provide the bucket name for each dataset and confirm access. We will then configure individual deliveries to their respective buckets.