Overview
What AWS SES is
Amazon SES (Simple Email Service) is a cloud email service that sends email at scale through verified sender identities, with the deliverability and low cost of AWS infrastructure.
Courier sits in front of it as one API, a visual editor, journeys, and every other channel, so you keep AWS SES for delivery and build multi-channel notifications on top.
You need a Courier account and your own AWS account with SES set up and a verified sending identity.
Why Courier
What you get with AWS SES + Courier
Design beautiful emails, no code
Build and edit email in Courier's visual editor. Product and marketing change content and layout without shipping code.
Automate multi-step journeys
Onboarding, drip, and lifecycle sequences with delays and branching, all delivered through AWS SES.
Add SMS, push, and chat
The same notification can reach every channel. Add one when you need it, no new integration in your code.
Add an in-app inbox
A new, easy add-on: drop Courier Inbox into your web or mobile app so users get an in-product notification center alongside email.
Localize a template in seconds
Pick a language and let Courier translate the whole template with AI, then tweak any string. One template, every market.
Send to lists and audiences
Broadcast a one-off or recurring message to an entire list through AWS SES, alongside your transactional email.
Use cases
What teams build with it
Setup
Connect it in minutes
An admin adds AWS SES once on the Integrations page in Courier. Once connected, anyone on your team can design and send email through AWS SES, and add channels whenever they need them.
FAQ
Frequently asked questions
Can I use AWS SES with Courier?
Yes. Courier uses Amazon SES as an email delivery provider: SES sends the email while Courier handles templates, routing, and other channels through the Send API.
Do I still need my own AWS SES account?
Yes. Courier routes through your own SES account, so you keep its region, sending reputation, and production access. You supply AWS credentials or an IAM role plus verified identities; Courier does not resell SES capacity.
What do I need to connect AWS SES to Courier?
Either an IAM user's Access Key ID and Secret Access Key, or an IAM role's Role ARN with your Courier workspace ID as the ExternalId. You also choose an AWS region and set a verified From Address.
What IAM permissions does Courier need for SES?
At minimum ses:SendEmail and ses:SendRawEmail, granted via AmazonSESFullAccess or a custom policy. Scope the resources to your verified identity ARNs, and include your Configuration Set ARN if you set one as the default.
How do I set the sender (From) address for SES?
Set a verified From Address, like support@example.com, that exists as a verified identity in the SES region you selected. Templates can override it per channel. New SES accounts stay in sandbox mode until you request production access.
Can Courier track SES delivery status?
Yes. Add the Message Events Webhook URL from Courier's SES provider settings to an SES Configuration Set with an Amazon SNS destination. Subscribe over HTTPS for Bounce, Delivery, and Reject events, and Courier records the status.
Is Courier a replacement for AWS SES?
No. Courier sits in front of SES, which still delivers the actual email. Courier adds the Send API, Journeys, and Design Studio, plus SMS, push, and Courier Inbox, so you orchestrate SES alongside other channels.
More
