Do I need an AWS account to use Shared SES?

No. Shared SES (Growth and Pro plans) uses SendFleet's own managed AWS SES infrastructure. You only need to add DNS records for your domain - no AWS account required.

What prerequisites does Shared SES have?

Your account email must be verified and your Managed plan subscription must be active. Sending also requires a registered Shared SES domain with ownership and DKIM verification completed.

Does Shared SES still have abuse controls?

Yes. SendFleet monitors bounce and complaint rates continuously and can suspend sending automatically or manually. Removal of manual approval as an onboarding prerequisite does not bypass abuse controls.

Shared SES - Managed Email Infrastructure on SendFleet

Shared SES

SendFleet's managed sending infrastructure. Verify your account email, subscribe to a Managed plan, add a sending domain, and complete its DNS verification. Full email logs, webhook events, and bounce/complaint handling included.

No manual account approval. Shared SES onboarding is automatic once your account email is verified and your Managed plan subscription is active. You still need to add and verify a sending domain before API sending is enabled. Abuse monitoring and suspension controls remain active for every sender.

How it works

When you use Shared SES, emails are delivered via SendFleet's own AWS SES account. We handle domain identity registration, bounce/complaint SNS webhooks, suppression lists, and abuse monitoring on your behalf. Full email logs appear in your dashboard.

What's included

Feature	Managed Starter	Managed Growth	Managed Pro
Monthly emails	5,000	25,000	100,000
Email log history	90 days	90 days	90 days
Bounce & complaint handling	✓ Automatic	✓ Automatic	✓ Automatic
Webhook delivery events	✓	✓	✓
Suppression list	✓ Managed	✓ Managed	✓ Managed
Abuse monitoring	✓	✓	✓
Priority support	✓	✓	✓ + SLA

Setup steps

1
Subscribe to a Managed plan
Go to Dashboard → Billing and select Managed Starter ($5/mo), Managed Growth ($15/mo), or Managed Pro ($59/mo). Your SES tenant is provisioned automatically after email verification and subscription activation.

Wait for automatic tenant provisioning

SendFleet provisions the infrastructure that isolates your suppression list. This normally happens immediately. If provisioning fails, the operation is retried on your next entitlement lifecycle event or you can contact us if the issue persists and we will fix it.

Add a Shared SES domain

Go to Dashboard → Domains → Add Shared SES domain. Enter your root domain (e.g. acme.com). We register the identity in our SES account and display the DNS records you need to add at your DNS provider.

Add DNS records

Add the records shown in the domain detail page. At minimum you need the TXT ownership record and the 3 DKIM CNAME records before you can send. See the full DNS Records guide →

Minimum required records

TXT   _amazonses.acme.com           <verification_token>
CNAME <token1>._domainkey.acme.com  <token1>.dkim.amazonses.com
CNAME <token2>._domainkey.acme.com  <token2>.dkim.amazonses.com
CNAME <token3>._domainkey.acme.com  <token3>.dkim.amazonses.com

5
Verify and send
Once DNS propagates (up to 48 h), click Verify ownership then Verify DKIM in the domain detail page. Both must pass before sending is enabled. Then generate an API key and make your first request.

Email logs

Every email sent via Shared SES is logged in your dashboard. Logs include the sender, recipient, subject, status (pending → sent / failed), and delivery timestamp. Logs are retained for 90 days.

Unlike BYOC, email content is stored on Shared SES - this is what enables the dashboard logs, bounce/complaint attribution, and webhook events. If you need zero content storage, use the BYOC path instead.

Bounce & complaint handling

SendFleet processes SNS bounce and complaint notifications from our SES configuration set automatically.

Event	What happens
Hard bounce (permanent)	Recipient address is added to your suppression list. Future sends to this address return `422 recipient_suppressed`. Email log is marked `failed`.
Soft bounce (transient)	Logged as a bounce event. Address is not suppressed - soft bounces are temporary delivery failures.
Complaint (spam report)	Recipient address is added to your suppression list. Future sends return `422 recipient_suppressed`.
Delivery confirmation	Email log status updated from `pending` to `sent` with a delivered_at timestamp.

High bounce or complaint rates trigger automatic suspension. We monitor a rolling 7-day window. Bounce rate ≥ 4% or complaint rate ≥ 0.08% (over a minimum of 50 sends) automatically suspends your account's API sending. Clean your recipient lists proactively. See Suspension & Suppression →

Deliverability response warnings

Successful send responses on the Shared SES path may include a warningsarray. These are non-blocking issues that will hurt inbox placement but don't prevent delivery.

Warning	Fix
MAIL FROM not verified	Add the MX and SPF records for `send.yourdomain.com`. See DNS Records →
DMARC record not found	Add `v=DMARC1; p=none;` as a TXT record on `_dmarc.yourdomain.com`.

Differences from BYOC

	Shared SES	BYOC
AWS account needed	No	Yes (yours)
Email content stored	Yes, 90 days	Never
Sender reputation	Shared pool	Isolated (yours)
Account setup	Verify account email and activate a Managed plan	Verify account email
Email logs in dashboard	Yes	No
Webhooks	Yes	No
Bounce/complaint auto-handling	Yes	Your SES account

PreviousBYOC Setup NextDNS Records