​
Overview

SuprSend offers two types of connectors:

  • Source: Connects event and user data from third-party platforms into SuprSend
  • Destination: Syncs data (message templates, notification metrics) from SuprSend to your data warehouse

Amazon S3 is a destination used to ingest data from SuprSend into your S3 bucket. You can directly query on this data using Athena or import it to data warehouses like Redshift, Snowflake, Clickhouse etc. for analysis.

​
How it works?

This integration exports individual parquet files for notification data, and JSON files for message templates to your S3 bucket at a regular interval. You can select what all data points you want to sync to your S3 bucket.

The sync happens every 3-5 minutes, ensuring that you always have the latest data in your S3 bucket. For notifications, there will be a separate parquet file for each day.

This integration only publishes parquet files for notifications to your storage bucket. You can either use Athena to query this data or ingest this data into a data warehouse for analysis.

​
Prerequisites

Before you begin, ensure you have:

  • An AWS account with administrative access
  • Necessary permissions to create S3 buckets and IAM roles/users
  • Access to AWS Console

​
Setup Steps

1

Create S3 Bucket

Skip this step if you want to use an existing bucket. Otherwise, follow these steps:

  1. Sign in to AWS S3 Console
  2. Click “Create bucket”

  1. Configure bucket settings:
  • Bucket name: e.g., suprsend-notification
  • Region: Choose your preferred region
  • Object Ownership: ACLs disabled (recommended)
  • Block all public access: Enabled
  • Bucket versioning: Disabled
  • Default encryption: Server-side encryption with Amazon S3 managed keys (SSE-S3)
  • Bucket Key: Enabled
  1. Click “Create bucket”

2

2. Set Bucket Permission Policy

We’ll need permission to PutObject for data ingestion in your bucket. To set permission policy,

  1. Go to IAM Console
  2. Select Policies → Create Policy
  3. Use JSON editor and paste this policy (replace suprsend-notification with your bucket name). Set a relevant name to the policy, something like - SingleBucketWriteAccess.
{
  "Version":"2012-10-17",
  "Statement":[
      {
        "Sid":"AllObjectActions",
        "Effect":"Allow",
        "Action":[
            "s3:PutObject"
        ],
        "Resource":[
            "arn:aws:s3:::suprsend-notification/*"
        ]
      }
  ]
}
3

Select the Authentication Scheme

Choose between IAM Role (recommended) or IAM User authentication. IAM Role-based authentication is the recommended approach as it:

  • Provides temporary, scoped access
  • Eliminates the need for long-term credentials
  • Follows security best practices

​
Configure S3 connector in SuprSend

Go to Settings → Connectors → Amazon S3 and fill in required information.

  • In case of IAM Role:

  • In case of IAM User:

Form FieldDescription
Connector name*This name is identify the connector and is for your reference
Authentication Scheme*Select whether to use IAM Role or IAM User for authentication.
AWS Region*Choose the AWS Region where your S3 bucket is hosted (for eg: us-east-1, ap-south-1, or eu-west-2)
Role ARN*The Amazon Resource Name (ARN) of the IAM Role that grants access to the S3 bucket.
External ID*The unique External ID you configured in the IAM Role’s trust policy for SuprSend. This provides an extra layer of security when SuprSend assumes the role.
Duration SecondsThe amount of time (in seconds) SuprSend can assume the IAM Role for each session (for example, 3600 = one hour). Leave it at the default unless you have specific session duration requirements.
Access Key ID*This is the access key ID linked to the IAM user. Refer step 4 for steps to create access key
Secret Access Key*This is the secret access linked to the IAM user. Refer step 4 for steps to get secret access
Export Bucket*Name of the S3 bucket where the parquet files should be exported. Refer step 1 to create an export bucket
Data Points to export*Here you can choose what all information should be exported to your S3 bucket: Notifications Status - To sync details to the each notification - users, tenants, vendor, channel, DLR status of the notification (delivery, seen, click etc.), and failure reasons for failed notifications Template - To sync all templates created in SuprSend in your S3 bucket. Template sync will happen every time you are making change in the template

Your S3 setup is now complete. Click on Enable sync to start data export. You can pause and resume your sync anytime you want. To Pause sync for certain data points, deselect the ones not needed from “Data Points to export” and save the changes.

You can also disable your entire sync by disabling the Enable sync button, in which case we’ll stop the export. When you enable your sync again, we send all of your historical data as if you’re starting a new integration.

Was this page helpful?