Skip to content
Communications ⇄ Database

Amazon SES to Reltio integration — real-time, two-way sync

Keep Amazon SES and Reltio in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Amazon SES and Reltio

Turn the messages, calls, and events Amazon SES handles into live rows in Reltio, and write back to trigger new outbound communication, with both sides in sync in seconds.

Engineers reach communications tools like Amazon SES through APIs, which means auth tokens, webhooks, delivery callbacks, and rate limits, all maintained forever and all shaped differently for every tool. The data those tools produce, who was contacted, what was sent, and what came back, would be simple to use if it lived in Reltio next to everything else.

Stacksync mirrors Sending Events, Messages (SendEmail / SendBulkEmail), Contacts, Contact Lists from Amazon SES into Interactions, Matches (Potential Matches), Activity Log, Data Change Requests (DCR) in Reltio and keeps both sides in sync in real time. Communication activity lands in the database as ordinary rows you can query and join, and rows your code writes, such as a queued outbound message or an updated contact, flow back into Amazon SES so the tool and the database never disagree.

There is no webhook endpoint to host, no rate limit to babysit, and no nightly export that leaves your services reading yesterday's activity.

Common use cases

  • 01 Push warehouse or CRM audience segments into SES as Contacts using CreateContact or a bulk CreateImportJob (up to 1M contacts per job) to feed marketing sends.
  • 02 Stream SES sending events (delivery, bounce, complaint, open, click) from a configuration-set event destination into a warehouse for deliverability reporting.
  • 03 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
  • 04 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.

Common sync patterns

React to activity as it happens

Sends, replies, answered calls, or completed meetings arrive in Reltio as row changes, so triggers, jobs, and services can respond in near real time.

One integration pattern for every channel

Each communications tool looks like tables in the database, so adding email, voice, or messaging is configuration rather than a new codebase.

Communication history as database rows

Every message, call, or event Amazon SES records becomes rows in Reltio, ready to query, join with your own data, and report on without touching the vendor API.

What you can sync between Amazon SES and Reltio

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Amazon SES objects Reltio objects How this pairing syncs
Suppression List Addresses auto-added on bounce or complaint; read with ListSuppressedDestinations and written with Put/DeleteSuppressedDestination to control re-sends. Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. Suppression List is specific to Amazon SES and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side.
Verified Identities Email-address and domain identities cleared to send; managed via CreateEmailIdentity, ListEmailIdentities, GetEmailIdentity (DKIM and verification status). Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. Verified Identities is specific to Amazon SES and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side.
Configuration Sets Named send-time rule groups that attach event destinations, IP pools, and suppression options; managed via Create/List ConfigurationSet operations. Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. Configuration Sets is specific to Amazon SES and Entities to Reltio — each maps to any object or custom field on the other side.
Sending Events Per-message send, delivery, bounce, complaint, open, and click events; not on any API, read from a configuration-set event destination (SNS/EventBridge/Firehose). Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Sending Events is specific to Amazon SES and Relations to Reltio — each maps to any object or custom field on the other side.
Messages (SendEmail / SendBulkEmail) Outbound email is produced via SendEmail and SendBulkEmail, accepting raw MIME or a template plus destination list. Send-only; there is no message store to read back. Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. Messages (SendEmail / SendBulkEmail) is specific to Amazon SES and Crosswalks to Reltio — each maps to any object or custom field on the other side.
Contacts Subscribers in the contact list with per-topic opt-in state; CRUD via CreateContact/ListContacts/UpdateContact/DeleteContact, each carrying a LastUpdatedTimestamp for polling. Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. Contacts is specific to Amazon SES and Interactions to Reltio — each maps to any object or custom field on the other side.

How changes propagate between Amazon SES and Reltio

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Amazon SES Reltio Sub-second propagation

DetectionAmazon SES notifies Stacksync of record changes through webhook events. Message events (delivery, bounce, complaint, open, click) are pushed in near real time through configuration-set event destinations.

DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.

Reltio Amazon SES Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

DeliveryEach detected change is written to Amazon SES through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Amazon SES: Every SES API action except SendEmail, SendRawEmail, and SendTemplatedEmail is throttled to 1 request/second per Region; the send rate and 24-hour sending quota are account-specific, adjustable, and per Region.
  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Amazon SES ⇄ Reltio

Connect Amazon SES and Reltio for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon SES–Reltio connection.

Real-time

Two-way sync

Changes in Amazon SES or Reltio instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Amazon SES or Reltio data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Amazon SES or Reltio record.

Observability

Monitoring

Track your Amazon SES ⇄ Reltio sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Amazon SES and Reltio.

How the Amazon SES and Reltio connectors work

Amazon SES

Integration surface
AWS SES API v2 (REST/JSON over HTTPS) plus an SMTP sending interface
Authentication
AWS IAM credentials (access key + secret) signed with Signature Version 4, or an assumed IAM role via STS; the SMTP interface uses SMTP credentials derived from an IAM user
Change detection
Message events (delivery, bounce, complaint, open, click) are pushed in near real time through configuration-set event destinations (SNS/EventBridge/Firehose); contacts, templates, and suppression entries are polled via List/Get operations
Capabilities
read · write · webhooks
Rate limits
Every SES API action except SendEmail, SendRawEmail, and SendTemplatedEmail is throttled to 1 request/second per Region; the send rate and 24-hour sending quota are account-specific, adjustable, and per Region

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works

How to connect Amazon SES to Reltio — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Amazon SES and Reltio with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Amazon SES connected
    Reltio connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Amazon SES and Reltio objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Amazon SES ⇄ Reltio
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Amazon SES Reltio
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Amazon SES and Reltio integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 335 integrations available for Amazon SES and Reltio.

Popular · 8 of 335
All Amazon SES integrations All Reltio integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own