--- title: "Amazon SES connector: setup and compatibility | Stacksync" description: "Amazon SES integration guide: plan Messages (SendEmail / SendBulkEmail) and Contacts, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/amazon-ses last_modified: 2026-09-15 --- Communications · Two-way sync platform # Amazon SES integration. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect your Amazon SES workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Messages (SendEmail / SendBulkEmail), Contacts and Sending Events. Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Messages (SendEmail / SendBulkEmail)** - **Contacts** - **Contact Lists** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=amazon-ses) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## Amazon SES records to discuss. These Amazon SES record examples help scope a technical review. They are not a list of verified Stacksync operations. Messages (SendEmail / SendBulkEmail) Retain message ID, conversation/thread ID, channel, and sender identity. Contacts Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Contact Lists Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Email Templates Identify this record type and the operation you need to review with Stacksync. Suppression List Identify this record type and the operation you need to review with Stacksync. Verified Identities Identify this record type and the operation you need to review with Stacksync. Connection setup ## Amazon SES connection requirements. Review Amazon SES access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the Amazon SES account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Amazon SES, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Amazon SES integration. Define whether the goal is reporting communication activity, resolving customer context, or executing a new message/call action. The last option needs its own confirmed write method and business authorization. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Amazon SES **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Retain message ID, conversation/thread ID, channel, and sender identity. Load related records in the right order Resolve conversation, participant, and customer context before associating messages. ### Mapping checks by record type #### Messages (SendEmail / SendBulkEmail) Confirm object support with Stacksync Identity Retain message ID, conversation/thread ID, channel, and sender identity. Fields to consider Source message ID · Thread reference · Delivery state · Timestamp · Related record ID Related records to resolve first Resolve conversation, participant, and customer context before associating messages. Test before going live Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. #### Contacts Confirm object support with Stacksync Identity Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Fields to consider Source person ID · Display name · Email address · Organization reference · Consent state Related records to resolve first Resolve the organization relationship and any owner or consent references required by the destination. Test before going live Test an email change, two records sharing an email, and a person associated with multiple organizations. #### Sending Events Confirm object support with Stacksync Identity Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. Fields to consider Source event ID · Event type · Occurred-at time · Related record ID · Payload version Related records to resolve first Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID. Test before going live Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the Amazon SES integration in four steps. The reporting dataset retains distinct activity and participant identities. No delivery retry accidentally sends another message or places another call. ### View the four setup tests and expected results 1. ### Verify Amazon SES credentials and resource scope After confirming an implementation path, validate the selected access method with the intended account, region or workspace, and resource scope. Record the credential owner and renewal procedure, then demonstrate access to one selected object. **Expected result:** The selected resource is accessible through the approved credential, with the renewal and revocation procedure assigned to an owner. 2. ### Test record matching for Messages (SendEmail / SendBulkEmail) Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. **Expected result:** The reporting dataset retains distinct activity and participant identities. No delivery retry accidentally sends another message or places another call. 3. ### Test the operation your workflow needs Review one Amazon SES record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your Amazon SES integration. ### Diagnose record matching, delayed changes, and rejected operations A Amazon SES record appears under the wrong destination record Retain message ID, conversation/thread ID, channel, and sender identity. Resolve conversation, participant, and customer context before associating messages. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Amazon SES implementation’s change-detection method for Messages (SendEmail / SendBulkEmail), Contacts and Sending Events. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific Amazon SES object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your Amazon SES workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=amazon-ses) ## Amazon SES integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) FAQ ## Amazon SES connector FAQ ### How should I plan an integration with Amazon SES? Define whether the goal is reporting communication activity, resolving customer context, or executing a new message/call action. The last option needs its own confirmed write method and business authorization. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the Amazon SES connector write changes back? Write-back support is not established for this connection. Review the Amazon SES records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Amazon SES data? Retain message ID, conversation/thread ID, channel, and sender identity. ### Which related records should I load first for Amazon SES? Resolve conversation, participant, and customer context before associating messages. ### How do I validate Amazon SES changes after the initial load? Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. The reporting dataset retains distinct activity and participant identities. No delivery retry accidentally sends another message or places another call. ### What will we cover in a Amazon SES integration demo? Start with one workflow and a sample record from Messages (SendEmail / SendBulkEmail), Contacts and Sending Events. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document. AI assistant ## Set up Amazon SES from Claude or ChatGPT Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### Claude Code ``` claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp ``` Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet. Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my Amazon SES and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Amazon SES. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Amazon SES record changes.” - “Create a Genie that answers questions about our Amazon SES data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore Amazon SES connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [Amazon SES and Google Cloud Platform](https://www.stacksync.com/integrations/amazon-ses-and-google-cloud-platform) - [Amazon SES and Okta](https://www.stacksync.com/integrations/amazon-ses-and-okta) - [Amazon SES and Rockset](https://www.stacksync.com/integrations/amazon-ses-and-rockset) - [Amazon Redshift and Amazon SES](https://www.stacksync.com/integrations/amazon-redshift-and-amazon-ses) - [Amazon SES and Salesforce](https://www.stacksync.com/integrations/amazon-ses-and-salesforce) - [Amazon SES and Databricks](https://www.stacksync.com/integrations/amazon-ses-and-databricks) - [Amazon SES and Datadog](https://www.stacksync.com/integrations/amazon-ses-and-datadog) - [Amazon SES and BambooHR](https://www.stacksync.com/integrations/amazon-ses-and-bamboohr) ### CRM · 41 - [Amazon SES and Affinity](https://www.stacksync.com/integrations/affinity-and-amazon-ses) - [Amazon SES and Apollo.io](https://www.stacksync.com/integrations/amazon-ses-and-apollo-io) - [Amazon SES and Attio](https://www.stacksync.com/integrations/amazon-ses-and-attio) - [Amazon SES and Chorusai](https://www.stacksync.com/integrations/amazon-ses-and-chorusai) - [Amazon SES and Clari](https://www.stacksync.com/integrations/amazon-ses-and-clari) - [Amazon SES and Close](https://www.stacksync.com/integrations/amazon-ses-and-close) - [Amazon SES and Copper CRM](https://www.stacksync.com/integrations/amazon-ses-and-copper-crm) - [Amazon SES and Creatio CRM](https://www.stacksync.com/integrations/amazon-ses-and-creatio-crm) - [Amazon SES and DealCloud](https://www.stacksync.com/integrations/amazon-ses-and-dealcloud) - [Amazon SES and Folk CRM](https://www.stacksync.com/integrations/amazon-ses-and-folk-crm) - [Amazon SES and Freshsales](https://www.stacksync.com/integrations/amazon-ses-and-freshsales) - [Amazon SES and Freshworks CRM](https://www.stacksync.com/integrations/amazon-ses-and-freshworks-crm) - [Amazon SES and Gladly](https://www.stacksync.com/integrations/amazon-ses-and-gladly) - [Amazon SES and Gong](https://www.stacksync.com/integrations/amazon-ses-and-gong) - [Amazon SES and Gorgias](https://www.stacksync.com/integrations/amazon-ses-and-gorgias) - [Amazon SES and HubSpot](https://www.stacksync.com/integrations/amazon-ses-and-hubspot) - [Amazon SES and Infor CRM](https://www.stacksync.com/integrations/amazon-ses-and-infor-crm) - [Amazon SES and Insightly](https://www.stacksync.com/integrations/amazon-ses-and-insightly) - [Amazon SES and Intercom](https://www.stacksync.com/integrations/amazon-ses-and-intercom) - [Amazon SES and Kommo](https://www.stacksync.com/integrations/amazon-ses-and-kommo) - [Amazon SES and Kustomer](https://www.stacksync.com/integrations/amazon-ses-and-kustomer) - [Amazon SES and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/amazon-ses-and-microsoft-dynamics-365-sales) - [Amazon SES and Nimble](https://www.stacksync.com/integrations/amazon-ses-and-nimble) - [Amazon SES and Nutshell](https://www.stacksync.com/integrations/amazon-ses-and-nutshell) - [Amazon SES and Oracle CX Sales](https://www.stacksync.com/integrations/amazon-ses-and-oracle-cx-sales) - [Amazon SES and Outreach](https://www.stacksync.com/integrations/amazon-ses-and-outreach) - [Amazon SES and Pipedrive](https://www.stacksync.com/integrations/amazon-ses-and-pipedrive) - [Amazon SES and Salesforce](https://www.stacksync.com/integrations/amazon-ses-and-salesforce) - [Amazon SES and Salesloft](https://www.stacksync.com/integrations/amazon-ses-and-salesloft) - [Amazon SES and SAP Sales Cloud](https://www.stacksync.com/integrations/amazon-ses-and-sap-sales-cloud) - [Amazon SES and Seismic](https://www.stacksync.com/integrations/amazon-ses-and-seismic) - [Amazon SES and Shopify](https://www.stacksync.com/integrations/amazon-ses-and-shopify) - [Amazon SES and Streak CRM](https://www.stacksync.com/integrations/amazon-ses-and-streak-crm) - [Amazon SES and SugarCRM](https://www.stacksync.com/integrations/amazon-ses-and-sugarcrm) - [Amazon SES and Twenty CRM](https://www.stacksync.com/integrations/amazon-ses-and-twenty-crm) - [Amazon SES and Veeva CRM](https://www.stacksync.com/integrations/amazon-ses-and-veeva-crm) - [Amazon SES and Vitally](https://www.stacksync.com/integrations/amazon-ses-and-vitally) - [Amazon SES and Vtiger CRM](https://www.stacksync.com/integrations/amazon-ses-and-vtiger-crm) - [Amazon SES and Xactly](https://www.stacksync.com/integrations/amazon-ses-and-xactly) - [Amazon SES and Zoho CRM](https://www.stacksync.com/integrations/amazon-ses-and-zoho-crm) - [Amazon SES and Zoho SalesIQ](https://www.stacksync.com/integrations/amazon-ses-and-zoho-salesiq) ### Database · 49 - [Amazon SES and Airtable](https://www.stacksync.com/integrations/airtable-and-amazon-ses) - [Amazon SES and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-amazon-ses) - [Amazon SES and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-ses-and-dynamo-db) - [Amazon SES and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-amazon-ses) - [Amazon SES and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-amazon-ses) - [Amazon SES and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-amazon-ses) - [Amazon SES and Apache Cassandra](https://www.stacksync.com/integrations/amazon-ses-and-apache-cassandra) - [Amazon SES and AWS Aurora MySQL](https://www.stacksync.com/integrations/amazon-ses-and-aws-aurora-mysql) - [Amazon SES and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/amazon-ses-and-aws-aurora-postgresql) - [Amazon SES and Azure Cosmos DB](https://www.stacksync.com/integrations/amazon-ses-and-azure-cosmos-db) - [Amazon SES and Azure SQL Database](https://www.stacksync.com/integrations/amazon-ses-and-azure-sql-database) - [Amazon SES and Citus](https://www.stacksync.com/integrations/amazon-ses-and-citus) - [Amazon SES and CockroachDB](https://www.stacksync.com/integrations/amazon-ses-and-cockroachdb) - [Amazon SES and Couchbase](https://www.stacksync.com/integrations/amazon-ses-and-couchbase) - [Amazon SES and DuckDB](https://www.stacksync.com/integrations/amazon-ses-and-duckdb) - [Amazon SES and Elasticsearch](https://www.stacksync.com/integrations/amazon-ses-and-elasticsearch) - [Amazon SES and Firebase](https://www.stacksync.com/integrations/amazon-ses-and-firebase) - [Amazon SES and Google AlloyDB](https://www.stacksync.com/integrations/amazon-ses-and-google-alloydb) - [Amazon SES and Google Cloud Spanner](https://www.stacksync.com/integrations/amazon-ses-and-google-cloud-spanner) - [Amazon SES and Google Cloud SQL](https://www.stacksync.com/integrations/amazon-ses-and-google-cloud-sql) - [Amazon SES and IBM AS/400](https://www.stacksync.com/integrations/amazon-ses-and-ibm-as400) - [Amazon SES and IBM Db2](https://www.stacksync.com/integrations/amazon-ses-and-ibm-db2) - [Amazon SES and IBM Informix](https://www.stacksync.com/integrations/amazon-ses-and-ibm-informix) - [Amazon SES and InfluxDB](https://www.stacksync.com/integrations/amazon-ses-and-influxdb) - [Amazon SES and InterSystems IRIS](https://www.stacksync.com/integrations/amazon-ses-and-intersystems-iris) - [Amazon SES and JDBC](https://www.stacksync.com/integrations/amazon-ses-and-jdbc) - [Amazon SES and MariaDB](https://www.stacksync.com/integrations/amazon-ses-and-mariadb) - [Amazon SES and MarkLogic](https://www.stacksync.com/integrations/amazon-ses-and-marklogic) - [Amazon SES and MongoDB](https://www.stacksync.com/integrations/amazon-ses-and-mongodb) - [Amazon SES and MySQL](https://www.stacksync.com/integrations/amazon-ses-and-mysql) - [Amazon SES and Neo4j](https://www.stacksync.com/integrations/amazon-ses-and-neo4j) - [Amazon SES and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/amazon-ses-and-oci-database) - [Amazon SES and OpenSearch](https://www.stacksync.com/integrations/amazon-ses-and-opensearch) - [Amazon SES and Oracle DB](https://www.stacksync.com/integrations/amazon-ses-and-oracle-db) - [Amazon SES and Postgres Heroku](https://www.stacksync.com/integrations/amazon-ses-and-postgres-heroku) - [Amazon SES and PostgreSQL](https://www.stacksync.com/integrations/amazon-ses-and-postgresql) - [Amazon SES and RavenDB](https://www.stacksync.com/integrations/amazon-ses-and-ravendb) - [Amazon SES and Redis Enterprise](https://www.stacksync.com/integrations/amazon-ses-and-redis-enterprise) - [Amazon SES and Reltio](https://www.stacksync.com/integrations/amazon-ses-and-reltio) - [Amazon SES and SAP ASE (Sybase)](https://www.stacksync.com/integrations/amazon-ses-and-sap-ase-sybase) - [Amazon SES and SAP HANA](https://www.stacksync.com/integrations/amazon-ses-and-sap-hana) - [Amazon SES and Scaleway Postgres](https://www.stacksync.com/integrations/amazon-ses-and-scaleway-postgres) - [Amazon SES and SingleStore](https://www.stacksync.com/integrations/amazon-ses-and-singlestore) - [Amazon SES and SQL Server](https://www.stacksync.com/integrations/amazon-ses-and-sql-server) - [Amazon SES and Supabase](https://www.stacksync.com/integrations/amazon-ses-and-supabase) - [Amazon SES and TiDB](https://www.stacksync.com/integrations/amazon-ses-and-tidb) - [Amazon SES and TimescaleDB](https://www.stacksync.com/integrations/amazon-ses-and-timescaledb) - [Amazon SES and VoltDB](https://www.stacksync.com/integrations/amazon-ses-and-voltdb) - [Amazon SES and YugabyteDB](https://www.stacksync.com/integrations/amazon-ses-and-yugabytedb) ### Data warehouse · 28 - [Amazon SES and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-amazon-ses) - [Amazon SES and Amazon S3](https://www.stacksync.com/integrations/amazon-ses-and-aws-s3) - [Amazon SES and Apache Doris](https://www.stacksync.com/integrations/amazon-ses-and-apache-doris) - [Amazon SES and Apache Druid](https://www.stacksync.com/integrations/amazon-ses-and-apache-druid) - [Amazon SES and Apache Hive](https://www.stacksync.com/integrations/amazon-ses-and-apache-hive) - [Amazon SES and Apache Impala](https://www.stacksync.com/integrations/amazon-ses-and-apache-impala) - [Amazon SES and Apache Pinot](https://www.stacksync.com/integrations/amazon-ses-and-apache-pinot) - [Amazon SES and Azure Synapse Analytics](https://www.stacksync.com/integrations/amazon-ses-and-azure-synapse-analytics) - [Amazon SES and BigQuery](https://www.stacksync.com/integrations/amazon-ses-and-bigquery) - [Amazon SES and ClickHouse](https://www.stacksync.com/integrations/amazon-ses-and-clickhouse) - [Amazon SES and Cloudera Data Platform](https://www.stacksync.com/integrations/amazon-ses-and-cloudera-data-platform) - [Amazon SES and Databricks](https://www.stacksync.com/integrations/amazon-ses-and-databricks) - [Amazon SES and Dremio](https://www.stacksync.com/integrations/amazon-ses-and-dremio) - [Amazon SES and Exasol](https://www.stacksync.com/integrations/amazon-ses-and-exasol) - [Amazon SES and Firebolt](https://www.stacksync.com/integrations/amazon-ses-and-firebolt) - [Amazon SES and Google Cloud Platform](https://www.stacksync.com/integrations/amazon-ses-and-google-cloud-platform) - [Amazon SES and Greenplum](https://www.stacksync.com/integrations/amazon-ses-and-greenplum) - [Amazon SES and IBM Netezza](https://www.stacksync.com/integrations/amazon-ses-and-ibm-netezza) - [Amazon SES and Materialize](https://www.stacksync.com/integrations/amazon-ses-and-materialize) - [Amazon SES and MotherDuck](https://www.stacksync.com/integrations/amazon-ses-and-motherduck) - [Amazon SES and Rockset](https://www.stacksync.com/integrations/amazon-ses-and-rockset) - [Amazon SES and Snowflake](https://www.stacksync.com/integrations/amazon-ses-and-snowflake) - [Amazon SES and Starburst Enterprise](https://www.stacksync.com/integrations/amazon-ses-and-starburst-enterprise) - [Amazon SES and StarRocks](https://www.stacksync.com/integrations/amazon-ses-and-starrocks) - [Amazon SES and Teradata Vantage](https://www.stacksync.com/integrations/amazon-ses-and-teradata-vantage) - [Amazon SES and Tinybird](https://www.stacksync.com/integrations/amazon-ses-and-tinybird) - [Amazon SES and Vertica](https://www.stacksync.com/integrations/amazon-ses-and-vertica) - [Amazon SES and Yellowbrick](https://www.stacksync.com/integrations/amazon-ses-and-yellowbrick) ### Communications · 1 - [Amazon SES and Gmail](https://www.stacksync.com/integrations/amazon-ses-and-gmail) ### Developer tools · 11 - [Amazon SES and Azure Service Bus](https://www.stacksync.com/integrations/amazon-ses-and-azure-service-bus) - [Amazon SES and Datadog](https://www.stacksync.com/integrations/amazon-ses-and-datadog) - [Amazon SES and Google Cloud Pub/Sub](https://www.stacksync.com/integrations/amazon-ses-and-google-pubsub) - [Amazon SES and Jira](https://www.stacksync.com/integrations/amazon-ses-and-jira) - [Amazon SES and JMS](https://www.stacksync.com/integrations/amazon-ses-and-jms) - [Amazon SES and LDAP](https://www.stacksync.com/integrations/amazon-ses-and-ldap) - [Amazon SES and Microsoft Graph](https://www.stacksync.com/integrations/amazon-ses-and-microsoft-graph) - [Amazon SES and New Relic](https://www.stacksync.com/integrations/amazon-ses-and-newrelic) - [Amazon SES and Opsgenie](https://www.stacksync.com/integrations/amazon-ses-and-opsgenie) - [Amazon SES and PagerDuty](https://www.stacksync.com/integrations/amazon-ses-and-pagerduty) - [Amazon SES and RabbitMQ](https://www.stacksync.com/integrations/amazon-ses-and-rabbitmq) ### E-commerce · 8 - [Amazon SES and Akeneo](https://www.stacksync.com/integrations/akeneo-and-amazon-ses) - [Amazon SES and BigCommerce](https://www.stacksync.com/integrations/amazon-ses-and-bigcommerce) - [Amazon SES and ChannelEngine](https://www.stacksync.com/integrations/amazon-ses-and-channelengine) - [Amazon SES and EasyPost](https://www.stacksync.com/integrations/amazon-ses-and-easypost) - [Amazon SES and Magento](https://www.stacksync.com/integrations/amazon-ses-and-magento) - [Amazon SES and NuORDER](https://www.stacksync.com/integrations/amazon-ses-and-nuorder) - [Amazon SES and Shipwire](https://www.stacksync.com/integrations/amazon-ses-and-shipwire) - [Amazon SES and Shopware](https://www.stacksync.com/integrations/amazon-ses-and-shopware) ### Human resources · 1 - [Amazon SES and BambooHR](https://www.stacksync.com/integrations/amazon-ses-and-bamboohr) ### Marketing · 9 - [Amazon SES and Bingads](https://www.stacksync.com/integrations/amazon-ses-and-bingads) - [Amazon SES and Cvent](https://www.stacksync.com/integrations/amazon-ses-and-cvent) - [Amazon SES and Demandbase](https://www.stacksync.com/integrations/amazon-ses-and-demandbase) - [Amazon SES and Eloqua](https://www.stacksync.com/integrations/amazon-ses-and-eloqua) - [Amazon SES and Iterable](https://www.stacksync.com/integrations/amazon-ses-and-iterable) - [Amazon SES and Marketo](https://www.stacksync.com/integrations/amazon-ses-and-marketo) - [Amazon SES and RollWorks](https://www.stacksync.com/integrations/amazon-ses-and-rollworks) - [Amazon SES and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/amazon-ses-and-salesforce-marketing-cloud) - [Amazon SES and Twitter Ads](https://www.stacksync.com/integrations/amazon-ses-and-twitter-ads) ### Security and identity · 6 - [Amazon SES and Active Directory](https://www.stacksync.com/integrations/active-directory-and-amazon-ses) - [Amazon SES and Auth0](https://www.stacksync.com/integrations/amazon-ses-and-auth0) - [Amazon SES and Azure Active Directory](https://www.stacksync.com/integrations/amazon-ses-and-azure-active-directory) - [Amazon SES and JumpCloud](https://www.stacksync.com/integrations/amazon-ses-and-jumpcloud) - [Amazon SES and Okta](https://www.stacksync.com/integrations/amazon-ses-and-okta) - [Amazon SES and OneLogin](https://www.stacksync.com/integrations/amazon-ses-and-onelogin) ### Storage · 4 - [Amazon SES and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-amazon-ses) - [Amazon SES and Box](https://www.stacksync.com/integrations/amazon-ses-and-box) - [Amazon SES and Egnyte](https://www.stacksync.com/integrations/amazon-ses-and-egnyte) - [Amazon SES and SharePoint](https://www.stacksync.com/integrations/amazon-ses-and-sharepoint) 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](https://www.stacksync.com/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](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)