Guide to connect your AWS SES account with SuprSend to send email notifications.
Before you begin, ensure you have:
If you don’t have an AWS account, you can create one here.
SuprSend supports two authentication methods for Amazon SES integration:
IAM Role-based authentication is the recommended approach as it:
Creating IAM Role
Create Policy
If you’re using IAM-role authentication at multiple places inside SuprSend, you can consolidate all permission statements within a single policy.
Navigate to IAM console.
Select Policies
tab.
Click Create Policy
.
Either use a ‘Visual-editor’ or a ‘JSON editor’ to allow actions ["ses:SendEmail", "ses:SendRawEmail"]
.
For simplicity, choose “JSON editor” and replace the existing content with below JSON.
Name your policy (e.g. suprsend_trust_role_policy
).
Add an optional description.
Click Create Policy
. This will create a policy with the above permissions.
Create IAM Role
Roles
tabCreate Role
Another AWS Account
as trusted entity924219879248
suprsend_trust_role
)Verify Role Configuration
Important:
Creating IAM User
Follow these steps to create an IAM user with programmatic access:
AmazonSESFullAccess
policyAccess-key-ID
and Secret-Access-Key
securelyMake note of your AWS region (e.g. ap-south-1
) as it will be needed for configuration.
Create SES Verified Identity
Verified Identities
tabCreate Configuration Set
Configuration-set is a rule set applied to send-email. In configuration-set you can specify to track events (e.g. send, delivery, open, click, bounce, complaint etc.) and send these to an event destination. Refer to the documentation on how to create configuration sets.
Configuration sets
Create set
ses_suprsend_configset
default
Create Set
Manage Event Destinations
Event destinations are used to send email delivery events to SuprSend for tracking notification status (send, delivery, open, click, bounce, complaint etc.) for logs and analytics. To setup event destination,
Event Destinations
tabAdd destination
ses_suprsend_configset_destination
Event publishing
is markedEnabled
.Configure SNS Topic Permissions
After setting up the configuration set and SNS topic for email events, you’ll need to grant SuprSend permission to subscribe to your SNS topic. This is done through AWS’s cross-account SNS subscription feature, which allows external AWS accounts (like SuprSend’s) to receive notifications from your SNS topics. For detailed information about cross-account SNS subscriptions, see the AWS documentation.
Access Policy
section. The policy looks something like below. You’ll notice that the current policy givessns:Publish
permission to your SES account.Add policy to give`sns:Subscribe`permission
Next you need to add a policy to givesns:Subscribe
permission to SuprSend (Account: 924219879248). Add below json inside theStatement
list: (replace the “Resource
” value with your “Resource” value)
So in effect, the whole policy would look like this. Verify the policy and click on Save
.
Fill Vendor settings page on Suprsend
On the SuprSend dashboard, go to vendor page from side panel and click Email -> Amazon SES from the list of Vendors. This will open vendor details page as shown below:
Here’s a description on what each of these form fields describe:
Form Field | Description |
---|---|
Nickname | You can give any name which may help you to identify this account easily. E.g. - AWS SES [Production] |
From Email | Default ‘From Email ID’ that email will go from. You can override this in the individual template.*e.g. support@suprsend.com |
From Name | Default ‘From Name’ that email will go from. You can override this in the individual template.e.g. SuprSend |
Reply Address | Default ‘Reply To Email id’ on which replies are received. You can override this in the individual template.*e.g. support@suprsend.com |
AWS region | aws-region you are going to use for sending emails. |
Access Key ID | Access key ID of the IAM user with full access. Refer step to create a new IAM user and generate access key. |
Secret Access Key | Secret-Access-Key of the IAM user with full access. Refer step to create a new IAM user and generate access key. |
Configuration Set | Configuration-set is used to track email events (e.g. send, delivery, open, click, bounce, complaint etc.). Refer Step to define configuration set. |
SNS Topic ARN | This is the destination where the tracked events will be sent. Configuration set defines what events to be tracked and setting the topic allows SuprSend to receive these events. Follow step 4 & 5 to setup SNS topic and give SuprSend permission to subscribe to it. |
Price per notification | This is the amount you pay per email notification to AWS. It helps us to calculate, estimate and optimise your cost spent on notifications. |
One of the platform advantage of using SuprSend as a central communication system is that it shows notification analytics for all channels in your SuprSend account together. For enabling event tracking at SuprSend (such as delivery, opened, blocked, spam etc.), you’ll have to sns:Subscribe
action to SuprSend.
Once you’ve filled in the required fields and saved your changes on the vendor configuration page in the SuprSend platform, you’ll need to manually click the Subscribe
button to initiate the subscription to your specified SNS Topic ARN. This step is necessary to enable Email Tracking and ensure that notification delivery and failure logs are properly tracked.
If any changes are made to the SNS configuration after a successful subscription, you can click the Resubscribe
button to re-establish the subscription using the latest configuration. This ensures your email tracking setup stays consistent and up to date.
Successfully Subscription as:
It’s recommended to allow recipients to unsubscribe from emails. You can use SuprSend’s hosted preference page for giving granular control to your users, allowing them to manage preferences per category while also reducing unnecessary vendor API calls for opt-outs.
Why it’s important to give unsubscribe option in email?
First, it is required by the CAN-Spam Act. Second, if you don’t give them this option, they are more likely to click on the spam complaint button, which will cause more harm than allowing them to unsubscribe. Finally, many ESPs look for unsubscribe links and are more likely to filter your email if they don’t have them.