Two-way sync
Changes in Box or Dynamo DB instantly reflect in both systems. No stale data, no manual imports.
Keep Box and Dynamo DB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
A database holds structured records; a storage system holds the files those records depend on, such as contracts, images, exports, uploads, and documents. The two describe the same things from opposite sides: a row in Dynamo DB says a file exists and carries its name, location, and status, while Box holds the bytes. Linked only by a hand-kept path or a one-off script, the two drift the moment a file is renamed, moved, or deleted and the record still points at where it used to be.
Stacksync syncs Global Tables, Tables, Items, Attributes in Dynamo DB with Tasks, Events, Files, Folders in Box bi-directionally and in real time. File attributes, including name, path or object key, size, type, modified time, owner, and tags or custom properties, map field by field to columns on the matching row, and a change on either side shows up on the other within seconds. New files appear as rows, metadata edits travel in the direction you choose, and deletes stay consistent, with conflict rules you set in place of nightly reconciliation scripts.
Where a record in Dynamo DB references a file in Box, such as a contract, an image, an export, or an upload, the reference, path, and status stay consistent as files are renamed, moved, or replaced, so stored links keep resolving.
Files that arrive in a folder or bucket in Box become rows in Dynamo DB as they land, so a database-driven process can pick them up without polling the storage system's API.
Rows from Dynamo DB are written out to Box as files on a schedule or as they change, giving a durable, low-cost copy for backup, compliance, or a data lake, without a custom export job to maintain.
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.
| Box objects | Dynamo DB objects | How this pairing syncs | |
|---|---|---|---|
| Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. | Items Schemaless records keyed by partition (and optional sort) key, mapped to rows or SaaS objects in syncs. | Collaborations is specific to Box and Items to Dynamo DB — each maps to any object or custom field on the other side. | |
| Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. | Attributes Per-item fields, including nested maps and lists, flattened or mapped during sync. | Users is specific to Box and Attributes to Dynamo DB — each maps to any object or custom field on the other side. | |
| Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. | Partition and Sort Keys The primary key pair used as the match key for bi-directional sync. | Groups is specific to Box and Partition and Sort Keys to Dynamo DB — each maps to any object or custom field on the other side. | |
| Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. | Global Secondary Indexes Alternate access paths used when sync queries filter on non-key attributes. | Tasks is specific to Box and Global Secondary Indexes to Dynamo DB — each maps to any object or custom field on the other side. | |
| Events Enterprise admin event stream, an audit log of uploads, deletes, logins, and shares across the account; read-only, consumed for reporting or change feeds. | DynamoDB Streams Ordered item-level change records consumed for incremental sync. | Events is specific to Box and DynamoDB Streams to Dynamo DB — each maps to any object or custom field on the other side. | |
| Files Core content object with versions, name, size, and metadata; synced two-way so files and their attributes move between Box and a database or another store. | Global Tables Multi-region replicas relevant when syncs must read from a specific region. | Files is specific to Box and Global Tables to Dynamo DB — each maps to any object or custom field on the other side. |
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.
DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.
DeliveryEach detected change is applied to Dynamo DB as a row-level write, with types converted between the two schemas.
DetectionChanges in Dynamo DB are captured at the source via change data capture — no polling loop against its API. Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration.
DeliveryEach detected change is written to Box through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Dynamo DB connection.
Changes in Box or Dynamo DB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Box or Dynamo DB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Box or Dynamo DB record.
Track your Box ⇄ Dynamo DB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Box and Dynamo DB.
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.
Authenticate Box and Dynamo DB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Box and Dynamo DB 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Box and Dynamo DB: authenticate both systems, choose the objects to sync (such as Box's Collaborations and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Box and Dynamo DB: Records that point at documents; A landing zone for incoming files; Continuous archival to file storage. Where a record in Dynamo DB references a file in Box, such as a contract, an image, an export, or an upload, the reference, path, and status stay consistent as files are renamed, moved, or replaced, so stored links keep resolving.
Box: REST API (api.box.com/2.0), plus the Events API and V2 Webhooks. Authentication: OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing. Dynamo DB: Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries. Authentication: AWS IAM credentials with SigV4 request signing. Stacksync manages authentication, retries, and rate limits on both sides.
Dynamo DB: Items are schemaless apart from the mandatory partition key (and optional sort key), so sync field mappings are defined per attribute rather than from a fixed schema. Box: Files and folders share the Box ID namespace but are distinct object types; the account root is always folder ID 0. Stacksync's field mapping accounts for these differences between Box and Dynamo DB without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Box and Dynamo DB records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Box and Dynamo DB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Box–Dynamo DB integration in-house.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 441 integrations available for Box and Dynamo DB.