Can you use Amazon SES for email marketing?

Amazon SES can deliver marketing email. Newsletters, campaign broadcasts, promotional emails, onboarding sequences -- all of these can route through SES. Whether SES is the right infrastructure for your sending program depends on what you mean by "use SES for email marketing" and how your operation is set up.

The short answer: SES is excellent delivery infrastructure for email marketing, but it is not a marketing platform. You need software above it to run a real sending program.

What SES does and does not include

Amazon SES accepts email via SMTP or API and delivers it. What it does not include:

• Subscriber list management -- no import, no storage, no segmentation, no custom fields
• Campaign builder -- no visual editor, no scheduling, no template library
• Marketing automation -- no journey builder, no event triggers, no conditional logic
• Unsubscribe handling -- you must manage opt-outs yourself or build the processing
• Bounce suppression -- bounce notifications arrive via SNS; you implement the suppression logic
• Engagement analytics -- basic delivery metrics via CloudWatch, not campaign-level reporting

This is not a criticism of SES. It is designed to be an infrastructure layer, not a complete marketing platform.

The right way to think about the stack

Email marketing infrastructure has two distinct layers. Most platforms bundle them, which is convenient but comes with trade-offs.

Bundled platforms (Mailchimp, Klaviyo, ActiveCampaign) handle both layers under one subscription. Convenient -- but you do not own the delivery infrastructure. Your sender reputation lives on their platform. If you move providers, you start building reputation from scratch.

Using SES with a dedicated marketing platform separates these layers. You own the delivery infrastructure: your SES account, your sending domains, your dedicated IPs if you have them. The platform software handles the marketing layer. This model costs slightly more to set up, but the infrastructure you build is yours.

Who it works well for

The deliverability requirements

Proper authentication

Your sending domain needs SPF, DKIM, and DMARC configured. SES supports DKIM signing on custom domains -- and you should enable it. A properly configured DKIM signature means your emails carry a cryptographic proof of origin. This is now a requirement from Gmail and Yahoo for bulk senders, not an optional improvement.

DMARC is the policy layer that tells inbox providers what to do when emails fail authentication checks. Starting with p=none for monitoring and moving to p=quarantine once your authentication is confirmed is the standard path for a serious sending program.

Bounce and complaint management

SES sends bounce and complaint notifications via Amazon SNS. Hard bounces need to be suppressed immediately. Sending to bounced addresses again risks your reputation and your SES account standing.

Complaint rate is the metric inbox providers watch most closely. Keep complaint rates below 0.1% (Google's stated threshold for bulk senders). At 0.3%, you will see deliverability impact. Above that, you risk account suspension.

List hygiene

Sending to addresses that have not engaged in years, or to a list that was not acquired through explicit opt-in, generates bounces and complaints at rates that damage sending reputation quickly. The composition of your subscriber list matters more than the infrastructure underneath it.

Getting started with SES for marketing email

1. Create an AWS account if you do not have one. SES is available in multiple regions.
2. Verify your sending domain in the SES console. This involves adding DNS records for domain verification and DKIM signing.
3. Configure DMARC on your domain. Start with p=none to collect data before enforcing policy.
4. Set up SNS for bounce and complaint notifications. Create an SNS topic and configure SES to publish events to it.
5. Request production access. New accounts start in the sandbox. Submit a request to AWS explaining your use case and how you acquire subscribers. Approval typically takes 24--48 hours.
6. Connect a marketing platform. Unless you are building everything yourself, connect SES to a platform that handles campaigns, subscriber management, automation, and the compliance layer above delivery.

The permission question

SES acceptable use policy requires explicit permission. This is not just a policy requirement -- it is the foundation of a sending program that performs well and stays performing well.

Subscribers who opted in to hear from you, who recognize your sender name, and who expect your emails are your best deliverability asset. They open, they click, they do not mark as spam. That engagement pattern builds reputation with inbox providers over time.

SES is built for this model. It is not built for cold outbound to purchased lists, and using it that way risks both your account standing and your domain reputation.