Guide to export notification data & templates from SuprSend to Amazon S3 bucket.
data points
you want to sync to your S3 bucket.
Create S3 Bucket
suprsend-notification
2. Set Bucket Permission Policy
PutObject
for data ingestion in your bucket. To set permission policy,suprsend-notification
with your bucket name). Set a relevant name to the policy, something like- SingleBucketWriteAccess
.Select the Authentication Scheme
IAM Role (Recommended)
Create Policy
["s3:PutObject"]
.
For simplity, choose “JSON editor” and replace the existing content with below JSON.
Resource
with your own bucketNext
, and enter a Policy Name (e.g. suprsend_trust_role_policy), & other optional Description.
Create Policy
button, it will create a new policy with the above permissions.
Create IAM Role
Create Role
button, and select Another AWS Account
as the trusted entity.924219879248
suprsend_trust_role
) and create the role.Verify Role Permissions
IAM User
s3-bucket-suprsend
Get Access Credentials
Form Field | Description |
---|---|
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 e.g.: 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 Seconds | The amount of time (in seconds) SuprSend can assume the IAM Role for each session (e.g. 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 |
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.