@brokeros/int-mail-ses) uses AWS Signature Version 4 (SigV4) to authenticate directly with Amazon SES REST endpoints and processes delivery telemetry via Amazon SNS.
AWS SES Email Pipeline
Required Credentials
To connect AWS SES to BrokerOS, generate an IAM User credential set with Amazon SES permissions:Configuration Steps
1
Verify Sending Domain in AWS SES Console
Open the Amazon SES Console. Under Configuration -> Verified Identities, create a Domain Identity for your sending domain. Add the 3 CNAME DKIM records provided by AWS into your DNS provider (Cloudflare, GoDaddy, Route 53).
2
Request Production Access (Exit Sandbox)
New AWS accounts operate in the SES Sandbox and can only send to verified addresses. Submit a Production Access Request in the SES Console specifying your real estate audience acquisition methods and opt-in policies. Approvals typically clear within 24 hours.
3
Add AWS SES in BrokerOS Settings
In the BrokerOS dashboard:
- Navigate to Dashboard -> Marketing -> Email -> Settings.
- Select the Providers & Domains tab (
/dashboard/marketing/email/settings?tab=providers). - Click Add Provider and select AWS SES.
- Fill in the modal fields: Account Name, From Name, From Email, AWS Access Key ID, AWS Secret Key, and AWS Region (e.g.
ap-south-1). - Click Verify & Connect: BrokerOS verifies IAM permissions, encrypts the credentials via AES-256-GCM, and saves them to
MarketingIntegration.
4
Configure Amazon SNS Event Destination
In the SES Console under your verified identity, configure Event Publishing to send Bounce, Complaint, Delivery, Open, and Click events to an Amazon SNS Topic subscribed to:BrokerOS automatically handles the SNS
SubscriptionConfirmation challenge and starts processing delivery events.