Amazon SES Integration: Turnkey Transactional Email Setup

Amazon SES Integration for Email Sending

With over 5 years of experience and 100+ successful projects, we provide seamless Amazon SES integration. When your daily transactional email volume exceeds 50,000, the cost of sending via SendGrid or Postmark becomes a significant expense. Amazon SES offers low per-email pricing (e.g., $0.10 per 1000 emails), but its setup demands understanding reputation mechanisms: DKIM, SPF, DMARC, bounce handling. Misconfiguration can lead to domain blocking by providers. We specialize in seamless SES integration with modern stacks—from Next.js to Laravel—with deliverability guarantee of 98%+ and typical monthly savings of $500–$10,000. We have dozens of projects with millions of emails sent. Get an engineer's consultation: we'll assess your project within a day.

Exiting SES Sandbox

By default, SES runs in Sandbox mode—you can only send to verified addresses. For production, submit a request via AWS Console → SES → Account Dashboard → Request production access. Describe your use case: email volume, type (transactional or marketing), reputation management measures. Approval typically takes 24 hours. If you need it faster, we help with the application. Once out of sandbox, you can send to any address without restrictions.

Why SES is More Cost-Effective

SES is several times cheaper than competitors: at high volumes (e.g., 1 million emails/month), SES costs $100 while SendGrid charges $1,950, saving $1,850 monthly. Unlike other providers, SES gives full control: dedicated IP pools, custom configurations, integration with CloudWatch for monitoring. With SNS, you can flexibly react to events and automatically block problematic addresses, maintaining a high sender reputation (Sender Score 95+).

Case Study: Migration from SendGrid to SES

From our practice—a migration project from SendGrid to SES for a large e-commerce client with a volume of 2 million emails per month. Cost savings exceeded 80%—a substantial monthly amount (previously $3,900, now $200). Additionally, we configured SNS/SQS for automatic bounce management, reducing the complaint rate from 0.5% to 0.02%. The entire process took 5 days. The key was maximizing sender reputation: we performed IP address warming over 2 weeks and configured DMARC policies.

What's Included in Our Work

• SES domain verification, DKIM, SPF, DMARC setup
• Creation of an IAM user with minimal permissions
• SES Configuration Set + SNS for event tracking (Bounce, Complaint, Delivery, Open, Click)
• Bounce and complaint processing via SQS + Lambda
• Integration of @aws-sdk/client-ses into your application
• Testing 10+ deliverability scenarios and spam score checks
• Documentation (architecture, setup guide, troubleshooting)
• 6 months of support after launch (monitoring alerts, performance tuning)

Work Process

1. Audit—analyze current email sending, volume, requirements (1 day)
2. Design—choose architecture (Lambda/EC2/Serverless) (1 day)
3. Implementation—configure SES, write code (2–3 days)
4. Testing—check deliverability, spam rating, bounce handling (1 day)
5. Deployment—deploy to production, set up CloudWatch monitoring (1 day)

Common Mistakes in SES Setup

Mistake #1: ignoring IP address warming. If you start sending 1 million emails from a new IP immediately, providers will block it. Mistake #2: incorrect reverse DNS (PTR) records. AWS lets you set a custom MAIL FROM, but it needs verification. Mistake #3: lack of bounce handling. If you don't remove complaints and non-existent addresses, reputation drops and emails land in spam. We automate this via SQS and Lambda, reducing bounce rates below 0.1%.

SES Limits

Technical Implementation

Install SDK and Basic Sending

npm install @aws-sdk/client-ses

import { SESClient, SendEmailCommand } from '@aws-sdk/client-ses';

const ses = new SESClient({
  region: process.env.AWS_REGION ?? 'eu-west-1',
  credentials: {
    accessKeyId: process.env.AWS_ACCESS_KEY_ID!,
    secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY!,
  },
});

async function sendEmail(params: {
  to: string | string[];
  subject: string;
  html: string;
  text?: string;
}) {
  const command = new SendEmailCommand({
    Source: 'Acme <[email protected]>',
    Destination: {
      ToAddresses: Array.isArray(params.to) ? params.to : [params.to],
    },
    Message: {
      Subject: { Data: params.subject, Charset: 'UTF-8' },
      Body: {
        Html: { Data: params.html, Charset: 'UTF-8' },
        ...(params.text ? { Text: { Data: params.text, Charset: 'UTF-8' } } : {}),
      },
    },
    ConfigurationSetName: 'production-config-set',
  });

  return ses.send(command);
}

Bulk Sending via Templates

import { SendBulkTemplatedEmailCommand } from '@aws-sdk/client-ses';

// Up to 50 recipients per request, template stored in SES
await ses.send(new SendBulkTemplatedEmailCommand({
  Source: '[email protected]',
  Template: 'weekly-digest-ru',
  DefaultTemplateData: JSON.stringify({ name: 'User', articles: [] }),
  Destinations: users.map(user => ({
    Destination: { ToAddresses: [user.email] },
    ReplacementTemplateData: JSON.stringify({
      name: user.name,
      articles: user.personalizedArticles,
    }),
  })),
}));

Configuration Set Setup

import {
  CreateConfigurationSetCommand,
  CreateConfigurationSetEventDestinationCommand,
  EventType,
} from '@aws-sdk/client-ses';

// Create SES Configuration Set
await ses.send(new CreateConfigurationSetCommand({
  ConfigurationSet: { Name: 'production-config-set' }
}));

// Add SNS destination for events
await ses.send(new CreateConfigurationSetEventDestinationCommand({
  ConfigurationSetName: 'production-config-set',
  EventDestination: {
    Name: 'sns-events',
    Enabled: true,
    MatchingEventTypes: [
      EventType.BOUNCE,
      EventType.COMPLAINT,
      EventType.DELIVERY,
      EventType.OPEN,
      EventType.CLICK,
    ],
    SNSDestination: {
      TopicARN: process.env.AWS_SNS_TOPIC_ARN,
    },
  },
}));

Bounce and Complaint Handling via SNS

// SQS worker processes SES events
for (const record of event.Records) {
  const snsMessage = JSON.parse(record.body);
  const sesEvent = JSON.parse(snsMessage.Message);

  if (sesEvent.notificationType === 'Bounce') {
    for (const recipient of sesEvent.bounce.bouncedRecipients) {
      await suppressEmail(recipient.emailAddress, 'bounce');
    }
  }

  if (sesEvent.notificationType === 'Complaint') {
    for (const recipient of sesEvent.complaint.complainedRecipients) {
      await suppressEmail(recipient.emailAddress, 'complaint');
    }
  }
}

Timeline

SES setup + domain verification + application integration—2–3 days. With SNS/SQS bounce handling—an additional 1–2 days. Contact us for a cost estimate tailored to your email volume—receive a consultation within a day. Order Amazon SES integration and reduce your email cost savings.

Amazon Simple Email Service (SES) — Wikipedia

Email Campaign Integration: Why Does It Often Break?

We’ve observed that a trigger email sent 10 minutes after registration converts 4–5 times better than the same email sent after 24 hours. This isn’t a marketing myth—it’s mechanics: while the user is still warm, while they remember the context. But most integrations with email services are built like this: form submits → synchronous HTTP request to API → if the API is slow, the user waits 3 seconds → the email either goes out or doesn’t, nobody knows. In one project, we saw a 30% drop in conversion simply because the email service responded with 504 and Laravel’s queue driver wasn’t configured. Lost emails often hit customers silently – no log, no alert, just a missing order confirmation.

If you’re facing lost emails or spam folder issues, order an audit of your current integration – we’ll find bottlenecks within 2 days.

Providers and Their APIs

Unisender — a Russian provider popular in the SMB segment. REST API, simple. Adding a contact: importContacts, sending a transactional email: sendEmail. Important: for transactional emails (order confirmations, password resets), Unisender Go is a separate service with a different API and separate pricing. Mixing bulk and transactional mailings in one stream is bad for domain reputation. Unisender Go handles up to 1000 requests per second.

SendPulse — provides email, SMS, web push, Viber, and Telegram bots through a unified API. Convenient for projects requiring an omnichannel approach. Automation 360 is a visual chain builder; you can trigger automation via API events. The PHP SDK (sendpulse/rest-api-php-sdk) is maintained but updated irregularly – better to use Guzzle directly.

Mailchimp — a choice for international audiences and marketing teams accustomed to the Mailchimp ecosystem. Transactional email via Mandrill (a subsidiary service). Marketing API v3 for list, tag, and campaign management. Webhooks for opens, clicks, unsubscribes, bounces.

SMS. For Russia: SMSCenter, MTS Exolve, Devino Telecom, SMS Aero. Their APIs are similar: a send method with phone, message, sender parameters (sender name must be registered separately with the operator). One nuance: the sender name must be registered through the aggregator with a contract – otherwise SMS won’t be sent on MTS/MegaFon/Beeline networks.

How to Build an Integration That Doesn’t Lose Emails?

Separate Transactional and Marketing Streams

Transactional emails (order confirmations, password resets, delivery status) go through a dedicated sender domain or subdomain tx.example.com. Marketing campaigns go through mail.example.com or news.example.com. If a marketing campaign receives many spam complaints, it should not affect the reputation of the transactional stream. According to SendGrid documentation, transactional messages should be sent through a dedicated IP pool to prevent cross-contamination.

Queue and Retry

Any call to the email API goes through a queue (Laravel Queue, Bull, Celery). If Unisender returns a 503, the job retries after 5 minutes, then 15, then 60. After 5 failed attempts, it goes to a dead letter queue with an alert. The user already received their 200 OK and knows nothing about the issue. This approach reduces bounce rate on projects to 0.5%.

Example Laravel job:

public function handle(): void
{
    try {
        $response = Http::post(config('services.unisender.email_url'), $this->params);
        if ($response->failed()) {
            $this->release(300); // retry after 5 min
        }
    } catch (\Throwable $e) {
        $this->release(300);
    }
}

Templates

We store templates in code (Blade, Twig, React Email), not in the provider’s interface. Reasons: versioning via Git, browser preview without sending, testability. For complex templates with dynamic content — react-email with export to HTML via @react-email/render.

Validation and Consent

Before adding a contact to a list — double opt-in (confirmation email). Store the confirmation timestamp in your own database. Upon unsubscription — synchronously unsubscribe both at the provider and in your database. Ignoring webhook unsubscriptions is a direct path to account suspension at the provider. All processes comply with Федеральный закон № 152-ФЗ «О персональных данных».

Deliverability Monitoring and DKIM Setup

Connect provider webhooks for events: bounce (hard and soft), spam_complaint, unsubscribe. Hard bounce — immediately mark the email as invalid in your database, stop sending. Soft bounce 3 times in a row — same. Metrics: open rate, click rate, bounce rate, unsubscribe rate — review at least once a week. Our certified engineers configure alerts in Grafana/Prometheus.

DKIM configuration steps:

1. Generate a key pair (e.g., openssl genrsa -out private.key 2048).
2. Publish the public key in DNS as a TXT record for the selector (e.g., mail._domainkey.tx.example.com).
3. Provide the selector to the provider (SendGrid, Mailgun, Unisender).
4. Verify with dig TXT mail._domainkey.tx.example.com.

SPF, DKIM, DMARC must be configured separately for each stream. We use subdomains with different DNS records.

Why Is It Important to Separate Streams?

If you send a marketing campaign from the same domain as transactional emails and receive spam complaints, you risk getting the domain blocked — and users will stop receiving even order confirmations. SPF, DKIM, DMARC (Sender Policy Framework, DomainKeys Identified Mail, Domain‑based Message Authentication, Reporting and Conformance) must be configured separately for each stream. In one project, a marketing blast with 12% spam complaints blocked the transactional domain for 48 hours — we had to re‑authenticate with Google and Yandex.

What Does the Integration Scope Include?

• Audit of current communication streams and domain reputation (SPF, DKIM, DMARC)
• Provider and schema selection: transactional vs marketing traffic
• Configuration of SPF, DKIM, DMARC DNS records
• Development of email templates (HTML + dynamic content)
• Backend integration via queues and API
• Webhook setup for deliverability and complaints
• Operations documentation and team training
• Deliverability guarantee and post‑launch support

We deliver production‑ready documentation, access to monitoring dashboards, and a handover session with your engineers. Our certified engineers provide a 30‑day post‑launch health check guarantee.

Timelines and Cost

Cost is calculated individually after audit. We provide turnkey service: from analysis to production monitoring. Contact us for a free engineer consultation — we’ll evaluate your project and give accurate timelines. Over 7 years of experience in email service integration, 50+ projects implemented. Order a free audit of your current integration and receive a report with recommendations and estimated savings.