> ## Documentation Index
> Fetch the complete documentation index at: https://docs.migma.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Amazon SES Integration

> Use Amazon SES as a delivery provider for Migma sends.

Use Amazon SES when your team already manages delivery through AWS or wants Migma-created emails delivered through SES.

## What SES does in Migma

<CardGroup cols={2}>
  <Card title="Delivery provider" icon="paper-plane">
    Migma prepares and sends the email, while SES handles delivery.
  </Card>

  <Card title="Verified sender required" icon="shield-check">
    The from address must use a domain or sender setup approved for SES sending.
  </Card>

  <Card title="Campaign and API sends" icon="code-bracket">
    Use SES from Migma sends when that provider is selected.
  </Card>

  <Card title="Migma records stay connected" icon="chart-bar">
    Campaign, logs, and suppression behavior stay in Migma workflows where supported.
  </Card>
</CardGroup>

## Setup checklist

<Steps>
  <Step title="Prepare SES">
    Verify your sending identity in AWS and make sure the account is approved for the type of sending you plan to do.
  </Step>

  <Step title="Connect SES in Migma">
    Open **Settings** and connect Amazon SES under email providers.
  </Step>

  <Step title="Choose the provider">
    When sending from Migma or the API, choose SES as the delivery provider.
  </Step>

  <Step title="Send a test">
    Send to internal test recipients before approving a campaign.
  </Step>
</Steps>

<Info>
  If you do not already use AWS for email delivery, Migma sending is usually the fastest setup path.
</Info>

## Related docs

<CardGroup cols={2}>
  <Card title="Email Service Providers" icon="envelope" href="/integrations/email-service-providers">
    Compare direct sending providers.
  </Card>

  <Card title="Sending Domains" icon="globe" href="/sending-domains/overview">
    Prepare sender identity and domain health.
  </Card>
</CardGroup>