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.

Why does Shared SES require manual account approval?

All customers on Growth and Pro plans share the same AWS SES sending reputation. Manual review protects every sender on the platform from bad actors who might drive up bounce or complaint rates.

How long does Shared SES approval take?

SendFleet reviews Shared SES applications within 1–2 business days. Submit your request from Dashboard → Request Verification with your use case, company details, and expected email volume.

Shared SES - Managed Email Infrastructure on SendFleet

Shared SES

SendFleet's managed sending infrastructure. Zero AWS setup required - verify your domain with a few DNS records and you're ready to send. Full email logs, webhook events, and bounce/complaint handling included.

Manual approval required.Growth and Pro plans send via SendFleet's SES account. To protect our shared sender reputation, every account is manually reviewed before Shared SES access is granted. Submit a request from Dashboard → Verification Request. Reviews typically take 1–2 business days.

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	Growth	Pro
Monthly emails	25,000	100,000
Email log history	90 days	90 days
Bounce & complaint handling	✓ Automatic	✓ Automatic
Webhook delivery events	✓	✓
Suppression list	✓ Managed	✓ Managed
Abuse monitoring	✓	✓
Priority support	✓	✓ + SLA

Setup steps

1
Subscribe to Growth or Pro
Go to Dashboard → Billingand select Growth ($15/mo) or Pro ($59/mo). You'll need manual account verification first - see Step 2.

Request manual verification

Go to Dashboard → Verification Request. Describe your sending use-case, company name, website, and expected volume. We review within 1–2 business days and email you the outcome. You cannot subscribe to Growth/Pro until this is approved.

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
SPF record not verified	Add `v=spf1 include:amazonses.com ~all` as a TXT record on your root domain.
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)
Manual approval	Required	Not required
Email logs in dashboard	Yes	No
Webhooks	Yes	No
Bounce/complaint auto-handling	Yes	Your SES account

PreviousBYOC Setup NextDNS Records