Skip to content
Data warehouse ⇄ Marketing

AWS S3 to Salesforce Marketing Cloud integration — real-time, two-way sync

Keep AWS S3 and Salesforce Marketing Cloud 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 AWS S3 and Salesforce Marketing Cloud

Put modeled data to work and measure what it drives: AWS S3 and Salesforce Marketing Cloud keep contacts, audiences, and campaign results in step in real time, in both directions.

AWS S3 is where your team models customers, product usage, and revenue into trusted tables; Salesforce Marketing Cloud runs the campaigns, audiences, and messages that reach those people. The two overlap wherever the same person, account, or segment matters to both, and when the bridge between them is a nightly export or a hand-built list, marketing targets stale data while analytics never sees what the campaign returned.

Stacksync syncs Prefixes, Object Metadata, Object Versions, Event Notifications in AWS S3 with Journeys (Journey Builder), Content Assets (Content Builder), Automations (Automation Studio), Tracking Events in Salesforce Marketing Cloud field by field, in real time, and in both directions. You decide which system owns which fields — a computed score or segment can flow out to Salesforce Marketing Cloud while sends, opens, and conversions flow back to AWS S3 — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Export synced operational data to S3 as files feeding a data lake or downstream batch jobs.
  • 02 Trigger incremental sync runs from S3 event notifications when new files land in a prefix.
  • 03 Two-way sync Data Extension rows between Marketing Cloud and a Postgres database or warehouse so audience attributes and opt-out state stay aligned in both systems.
  • 04 Push CRM or warehouse audience segments into Data Extensions via the async rows API (background bulk insert) so marketing sends to freshly built audiences without manual CSV imports.

Common sync patterns

Activate a modeled audience

A segment or score built in AWS S3 — high-intent accounts, churn risk, a lifetime-value tier — lands as an audience or contact field in Salesforce Marketing Cloud, so campaigns target the people your data actually points to instead of a static export.

Keep the contact and audience list current

New and updated contacts, leads, or audience members flow between AWS S3 and Salesforce Marketing Cloud, so the marketing audience reflects the people in your warehouse and corrections propagate instead of the two sides drifting apart.

Suppression and consent stay aligned

Unsubscribes, bounces, and consent or opt-out flags held in either system propagate to the other, so no one is messaged after opting out and AWS S3 holds the current state for auditing.

What you can sync between AWS S3 and Salesforce Marketing Cloud

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.

AWS S3 objects Salesforce Marketing Cloud objects How this pairing syncs
Buckets Top-level containers a sync targets; region and policy are set at this level. Contacts / Subscribers The contact model keyed by Subscriber Key, holding channel addresses and subscription status; managed through the Contacts API (/contacts/v1/contacts) and the SOAP Subscriber object, and referenced by every send and journey. Buckets is specific to AWS S3 and Contacts / Subscribers to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Objects The stored files (CSV, JSON, Parquet); syncs read them as datasets or write exports into them. Journeys (Journey Builder) Multi-step automated flows read and managed via /interaction/v1/interactions; contacts are injected by firing an entry event to /interaction/v1/events with an EventDefinitionKey and contact data. Objects is specific to AWS S3 and Journeys (Journey Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Prefixes Key-name paths used to partition synced datasets, since S3 has no real directories. Content Assets (Content Builder) Emails, templates, images, and reusable content blocks stored in Content Builder and read or written via /asset/v1/content/assets, used to compose the messages a journey or send delivers. Prefixes is specific to AWS S3 and Content Assets (Content Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Object Metadata System and user-defined metadata read alongside object contents. Automations (Automation Studio) Scheduled or triggered workflows of import, query, extract, and send activities managed via /automation/v1/automations; SQL Query Activities read Data Views and write results into Data Extensions. Object Metadata is specific to AWS S3 and Automations (Automation Studio) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Object Versions Prior copies retained when versioning is enabled, relevant for reprocessing. Tracking Events Sent, Open, Click, Bounce, Unsubscribe, and NotSent events retrieved through the SOAP tracking objects (SentEvent, OpenEvent, ClickEvent, BounceEvent) or the Automation Studio Data Views (_Sent, _Open, _Click, _Bounce) - the queryable record of engagement per send. Object Versions is specific to AWS S3 and Tracking Events to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Event Notifications Notifications on object creation or deletion that trigger incremental processing. Transactional Sends Triggered and transactional Email/SMS delivered through the Messaging API (/messaging/v1/email/messages/{key}); the Event Notification Service reports each message's disposition (delivered, bounced, opened, clicked). Event Notifications is specific to AWS S3 and Transactional Sends to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.

How changes propagate between AWS S3 and Salesforce Marketing Cloud

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.

AWS S3 Salesforce Marketing Cloud Sub-second propagation

DetectionAWS S3 notifies Stacksync of record changes through webhook events. S3 Event Notifications on object create/delete delivered to SQS, SNS, Lambda, or EventBridge.

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

Salesforce Marketing Cloud AWS S3 Sub-second propagation

DetectionSalesforce Marketing Cloud notifies Stacksync of record changes through webhook events. The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback.

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

Rate-limit considerations

  • AWS S3: Request throughput scales per prefix; sustained high-volume workloads should spread keys across prefixes.
  • Salesforce Marketing Cloud: Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.
What ships with AWS S3 ⇄ Salesforce Marketing Cloud

Connect AWS S3 and Salesforce Marketing Cloud for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every AWS S3–Salesforce Marketing Cloud connection.

Real-time

Two-way sync

Changes in AWS S3 or Salesforce Marketing Cloud instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever AWS S3 or Salesforce Marketing Cloud 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 AWS S3 or Salesforce Marketing Cloud record.

Observability

Monitoring

Track your AWS S3 ⇄ Salesforce Marketing Cloud sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between AWS S3 and Salesforce Marketing Cloud.

How the AWS S3 and Salesforce Marketing Cloud connectors work

AWS S3

Integration surface
REST API (the S3 API), accessed directly or through AWS SDKs
Authentication
AWS IAM credentials with SigV4 signing; commonly a role scoped to specific buckets and prefixes
Change detection
S3 Event Notifications on object create/delete delivered to SQS, SNS, Lambda, or EventBridge; list-based polling as a fallback
Capabilities
read · write · webhooks
Rate limits
Request throughput scales per prefix; sustained high-volume workloads should spread keys across prefixes

Salesforce Marketing Cloud

Integration surface
Two APIs on tenant-specific endpoints: a REST API (JSON over HTTPS) for Data Extensions, Journeys, Contacts, Content Builder, and Automations, plus a legacy SOAP API (ExactTarget WSDL) for tracking events and bulk Retrieve.
Authentication
OAuth 2.0 via an Installed Package (Client ID + Client Secret). Server-to-server uses the client_credentials grant and web apps use authorization_code, both against {subdomain}.auth.marketingcloudapis.com/v2/token. The 20-minute access token response also returns the account's rest_instance_url and soap_instance_url.
Change detection
The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback URL and subscription are registered and verified. There is no general data-change feed, so Data Extension and Data View syncs poll by date fields.
Capabilities
read · write · webhooks
Rate limits
Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.
How it works

How to connect AWS S3 to Salesforce Marketing Cloud — 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 AWS S3 and Salesforce Marketing Cloud 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
    AWS S3 connected
    Salesforce Marketing Cloud connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the AWS S3 and Salesforce Marketing Cloud 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 · AWS S3 ⇄ Salesforce Marketing Cloud
    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
    AWS S3 Salesforce Marketing Cloud
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

AWS S3 and Salesforce Marketing Cloud 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 503 integrations available for AWS S3 and Salesforce Marketing Cloud.

Popular · 8 of 503
All AWS S3 integrations All Salesforce Marketing Cloud 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