Amazon SES

Use the Amazon SES connector when AWS is your preferred delivery platform or when procurement, compliance, or infrastructure ownership already points to SES.

Before you start

• Verify the sending identity in SES.
• Move the SES account out of sandbox mode for production traffic.
• Create IAM credentials with least-privilege send permissions.
• Decide which AWS region owns the sending identity.

Setup

sequenceDiagram
  participant Admin as Workspace admin
  participant AWS as Amazon SES
  participant MG as GenieOS
  participant Recipient as Recipient

  Admin->>AWS: Verify identity and create IAM credentials
  Admin->>MG: Install SES connector
  MG->>AWS: Send test via SES API
  AWS->>Recipient: Deliver email
  AWS->>MG: SNS or event destination callbacks

1. Open Settings -> Connectors and choose Amazon SES.
2. Enter the AWS region and IAM credentials.
3. Configure the verified sender identity.
4. Configure provider events through the webhook mechanism shown in the connector setup flow.
5. Send a connector test.

Capabilities

Webhooks and suppressions

SES event publishing must be configured for the identity or configuration set used by GenieOS. At minimum, route bounces and complaints back to GenieOS so future sends are suppressed correctly.

Troubleshooting

• Sandbox errors mean the SES account or region is not approved for production sending.
• Signature or credential errors usually mean the IAM user lacks SES send permissions or was created in the wrong account.
• Missing event data usually means the configuration set or event destination is not attached to the send path.