Prerequisites Before Adding AWS SES on WebEngage

  1. Please ensure that the From Email/Domain in your AWS SES account is verified. When adding this AWS SES account on WebEngage, please ensure that you specify the same Region as the one you used when configuring/verifying the From Email/Domain in AWS SES.
  1. Following permissions to the credentials are required:
  1. The SES account must NOT be in Sandbox mode. If the account is in Sandbox mode, the recipient address must also be verified.

  2. Request AWS to increase the send rate to a higher number (2500 emails/second) for better throughput.

  1. This step is optional. In case you use dedicated IPs to send emails through AWS SES and if you would like the email campaigns in WebEngage to be sent through these dedicated IPs, please create a Configuration Set in your AWS SES account and map these IPs to that configuration set. You can then specify this Configuration Set in WebEngage when you’re adding AWS SES as an ESP in WebEngage.

Once you've completed the steps above, please proceed with the steps below.

Steps to Add AWS SES on WebEngage

Click on the AWS SES box under the Available Email Service Providers (ESP) section. In the configuration modal, enter the following information of your AWS SES account: Access Key, Secret Key, Region, Configuration Set (Optional).

You will also have to name the configuration on WebEngage to identify the added ESP account. Please choose any user-friendly name for the Name Your Configuration field. The Configuration Name helps you identify the relevant ESP account you should use during the Email campaign creation process (especially helpful when you have multiple accounts with the same ESP that you have configured and added to WebEngage).

Updated about a year ago


AWS SES


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.