Skip to content
Data warehouse ⇄ CRM

AWS S3 to Dun And Bradstreet integration — real-time data sync

Keep AWS S3 and Dun And Bradstreet 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 Dun And Bradstreet

Flow Dun And Bradstreet data into AWS S3 in real time — no exports, no schedulers, no custom scripts.

Dun And Bradstreet is a read-only source: Stacksync reads its data in real time and delivers it into AWS S3, so AWS S3 always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.

The CRM feeds the warehouse and the warehouse should feed the CRM: relationship data flows one way, and computed scores, segments, and customer context flow back. Most teams build the first half as a batch pipeline and never quite get to the second.

Stacksync does both with one connection. Criteria Search, Monitoring Notifications, Company Information (Data Block), Principals & Contacts (Data Block) from Dun And Bradstreet land in AWS S3 as live tables, updated within seconds, and columns computed in AWS S3 write back to fields in Dun And Bradstreet. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.

Common use cases

  • 01 Build target-account lists with Criteria Search and land the resulting DUNS plus firmographics in a database for outbound and TAM analysis.
  • 02 Poll D&B Monitoring notifications for a registered portfolio of key accounts and suppliers and update the CRM or warehouse record whenever a firmographic or risk score changes.
  • 03 Ingest partner or vendor file drops (CSV, JSON, Parquet) from a bucket into a database or CRM as records.
  • 04 Export synced operational data to S3 as files feeding a data lake or downstream batch jobs.

Common sync patterns

Scores and segments back on the record

Lead scores, churn risk, or usage segments computed in AWS S3 appear as fields in Dun And Bradstreet, where the people working accounts actually see them.

A single customer view

Join Dun And Bradstreet's relationship data with billing, product, and support data in AWS S3 to build the customer picture the CRM alone cannot hold.

Cleanup that sticks

Deduplication and normalization done in AWS S3 can be written back, so warehouse-side cleanup actually fixes the CRM.

What you can sync between AWS S3 and Dun And Bradstreet

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 Dun And Bradstreet objects How this pairing syncs
Access Points Scoped network endpoints used to grant a sync narrow access to a bucket. Monitoring Notifications Change notices for a registered portfolio of DUNS; read-only feed pulled from the notifications endpoint (retained ~60 days) or delivered as bundled push. Access Points is specific to AWS S3 and Monitoring Notifications to Dun And Bradstreet — each maps to any object or custom field on the other side.
Multipart Uploads The mechanism used to write large export files reliably. Company Information (Data Block) Core firmographics for a D-U-N-S Number - legal name, addresses, industry codes, employees, sales, status. Retrieved read-only via the Enrich endpoint; blocks come in levels L1-L4. Multipart Uploads is specific to AWS S3 and Company Information (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side.
Buckets Top-level containers a sync targets; region and policy are set at this level. Principals & Contacts (Data Block) Company officers, executives, and contacts tied to a D-U-N-S Number; read-only enrichment used to populate CRM contact and account-owner fields. Buckets is specific to AWS S3 and Principals & Contacts (Data Block) to Dun And Bradstreet — 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. Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. Objects is specific to AWS S3 and Company Hierarchy & Connections (Family Tree) to Dun And Bradstreet — 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. Financial Strength & Risk Insight (Data Block) D&B risk and credit signals - D&B Rating, PAYDEX, Failure Score, Delinquency Score, Viability - keyed by D-U-N-S Number; read-only. Prefixes is specific to AWS S3 and Financial Strength & Risk Insight (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side.
Object Metadata System and user-defined metadata read alongside object contents. Identity Resolution (Match / cleanseMatch) Sends a company name and address and returns ranked candidate DUNS with confidence codes and a MatchGrade; read-only scored match, not an exact lookup. Object Metadata is specific to AWS S3 and Identity Resolution (Match / cleanseMatch) to Dun And Bradstreet — each maps to any object or custom field on the other side.

How changes propagate between AWS S3 and Dun And Bradstreet

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 Dun And Bradstreet 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.

DeliveryDun And Bradstreet does not accept inbound record writes, so this direction carries requests rather than records: Dun And Bradstreet's output flows back as field updates on the originating AWS S3 records.

Dun And Bradstreet AWS S3 Interval-based propagation

DetectionStacksync polls Dun And Bradstreet for changes on an incremental schedule, reading only records changed since the previous pass. Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days).

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.
  • Dun And Bradstreet: Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
What ships with AWS S3 ⇄ Dun And Bradstreet

Connect AWS S3 and Dun And Bradstreet for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every AWS S3–Dun And Bradstreet connection.

Real-time

Real-time sync

Changes in AWS S3 or Dun And Bradstreet instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever AWS S3 or Dun And Bradstreet 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 Dun And Bradstreet record.

Observability

Monitoring

Track your AWS S3 ⇄ Dun And Bradstreet 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 Dun And Bradstreet.

How the AWS S3 and Dun And Bradstreet 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

Dun And Bradstreet

Integration surface
D&B Direct+ REST API (plus.dnb.com) - capability groups for Identity Resolution (Match), Search, Enrich (Data Blocks by D-U-N-S Number), Multi-Process, Data File/Batch, and Monitoring
Authentication
OAuth 2.0 client-credentials: Base-auth a consumer key/secret to POST /v3/token for a bearer token; access tokens expire after 24 hours.
Change detection
Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days). Bundled push delivery is configured with your D&B rep; there is no standard HTTP webhook and no log-based CDC.
Capabilities
read
Rate limits
Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
How it works

How to connect AWS S3 to Dun And Bradstreet — 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 Dun And Bradstreet 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
    Dun And Bradstreet connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the AWS S3 and Dun And Bradstreet 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 ⇄ Dun And Bradstreet
    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 Dun And Bradstreet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

AWS S3 and Dun And Bradstreet 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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 520 integrations available for AWS S3 and Dun And Bradstreet.

Popular · 8 of 520
Coworkers laughing in front of a laptop in a casual office setting

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