Skip to content
Database ⇄ Storage

Amazon DynamoDB to Egnyte integration — real-time, two-way sync

Keep Amazon DynamoDB and Egnyte 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 DynamoDB and Egnyte

Keep Amazon DynamoDB and Egnyte in step: a row in Amazon DynamoDB for every file in Egnyte, with names, paths, metadata, and status staying consistent in real time, in both directions.

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 Amazon DynamoDB says a file exists and carries its name, location, and status, while Egnyte 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 Time to Live (TTL), Tables, Items, Global secondary indexes (GSIs) in Amazon DynamoDB with Events and Audit reports, Files, Folders, Users in Egnyte 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.

Common use cases

  • 01 Mirror a high-write DynamoDB table into a relational database so teams can join NoSQL application data against relational tables for reporting.
  • 02 Use DynamoDB Streams as a change-data-capture source to push item INSERT, MODIFY, and REMOVE events into a CRM, search index, or operational database in near-real-time.
  • 03 Stream Egnyte audit Events (file, login, permission, and Link changes) into a warehouse or SIEM for compliance and governance reporting.
  • 04 Provision and deprovision Egnyte Users and Groups from an HRIS or IdP so folder access follows employee onboarding and offboarding.

Common sync patterns

Continuous archival to file storage

Rows from Amazon DynamoDB are written out to Egnyte 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.

A queryable index of the file store

Every file or object in Egnyte shows up as a row in Amazon DynamoDB, with its name, folder or key, size, type, and modified date as columns, so the contents of the store can be listed, filtered, and joined like any other table.

File metadata kept in step

Tags, custom properties, owner, or status columns edited on a row in Amazon DynamoDB write back to the matching file's metadata in Egnyte, and metadata changed in Egnyte updates the row, so the two never disagree about a file.

What you can sync between Amazon DynamoDB and Egnyte

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 DynamoDB objects Egnyte objects How this pairing syncs
Time to Live (TTL) Per-item expiry timestamps; DynamoDB deletes expired items in the background and emits a Streams REMOVE record for each deletion. Files File content managed via the fs-content endpoint (upload/download, chunked for large files); synced two-way with other stores. Time to Live (TTL) is specific to Amazon DynamoDB and Files to Egnyte — each maps to any object or custom field on the other side.
Tables Top-level containers, each with a partition key and optional sort key; Stacksync syncs a table as a stream of items with full read and write via PutItem, UpdateItem, and DeleteItem. Folders Folder hierarchy managed via the fs endpoint (create, move, rename, delete); the tree structure is mirrored during sync. Tables is specific to Amazon DynamoDB and Folders to Egnyte — each maps to any object or custom field on the other side.
Items Individual schemaless records (attributes up to 400 KB each); read with GetItem, Query, and Scan and written with PutItem or BatchWriteItem, so write is supported here. Users Accounts managed via the Users API; provisioned, updated, and deactivated in sync with an HRIS or identity provider. Items is specific to Amazon DynamoDB and Users to Egnyte — each maps to any object or custom field on the other side.
Global secondary indexes (GSIs) Alternate key projections that let you Query by non-key attributes without a full table Scan; read-only views maintained automatically by DynamoDB. Groups Groups and membership managed via the Groups API; kept aligned with directory or IdP groups that drive folder access. Global secondary indexes (GSIs) is specific to Amazon DynamoDB and Groups to Egnyte — each maps to any object or custom field on the other side.
Local secondary indexes (LSIs) Extra sort keys within the same partition key, defined at table creation; queried like the base table for alternate access patterns. Permissions Folder permissions listed, set, and removed via the Permissions API; effective permission for a user/folder is computable. Local secondary indexes (LSIs) is specific to Amazon DynamoDB and Permissions to Egnyte — each maps to any object or custom field on the other side.
DynamoDB Streams Ordered item-level change records (INSERT, MODIFY, REMOVE) with old/new image views and 24-hour retention; the native change-data-capture source Stacksync reads for near-real-time sync. Links Shared file and folder links created, listed, and revoked via the Links API; useful for governing and auditing external sharing. DynamoDB Streams is specific to Amazon DynamoDB and Links to Egnyte — each maps to any object or custom field on the other side.

How changes propagate between Amazon DynamoDB and Egnyte

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 DynamoDB Egnyte Sub-second propagation

DetectionChanges in Amazon DynamoDB are captured at the source via change data capture — no polling loop against its API. DynamoDB Streams emit ordered item-level change records (INSERT, MODIFY, REMOVE) with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views.

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

Egnyte Amazon DynamoDB Sub-second propagation

DetectionEgnyte notifies Stacksync of record changes through webhook events. Events API polled with an incremental cursor (Egnyte recommends an interval of 5 minutes or more), or Webhooks push notifications for fs, metadata,.

DeliveryEach detected change is applied to Amazon DynamoDB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Amazon DynamoDB: Throughput is metered in read/write capacity units (provisioned or on-demand): 1 WCU = one 1 KB write per second, 1 RCU = one strongly-consistent 4 KB read per second. Exceeding capacity or the ~3,000 RCU / 1,000 WCU per-partition ceiling returns ProvisionedThroughputExceededException with throttling.
  • Egnyte: Auto-generated keys default to 2 requests/second and 1,000 requests/day, enforced per access token; monitor X-Accesstoken-Qps-Current/Allotted and X-Accesstoken-Quota-Current headers; higher limits on request.
What ships with Amazon DynamoDB ⇄ Egnyte

Connect Amazon DynamoDB and Egnyte for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Amazon DynamoDB or Egnyte 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 DynamoDB or Egnyte record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Amazon DynamoDB and Egnyte.

How the Amazon DynamoDB and Egnyte connectors work

Amazon DynamoDB

Integration surface
AWS SDK / low-level HTTPS JSON API at dynamodb.<region>.amazonaws.com (PutItem, GetItem, UpdateItem, DeleteItem, Query, Scan, BatchWriteItem, TransactWriteItems), plus PartiQL (ExecuteStatement) for SQL-style access and DynamoDB Streams for change capture.
Authentication
AWS Signature Version 4 (SigV4) signed requests using an IAM access key ID and secret key, or temporary STS credentials from an assumed IAM role; IAM policies scope access down to table and item level.
Change detection
DynamoDB Streams emit ordered item-level change records (INSERT, MODIFY, REMOVE) with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views and 24-hour retention, read via shard iterators (or Kinesis Data Streams for longer retention). No native HTTP webhooks.
Capabilities
read · write · CDC
Rate limits
Throughput is metered in read/write capacity units (provisioned or on-demand): 1 WCU = one 1 KB write per second, 1 RCU = one strongly-consistent 4 KB read per second. Exceeding capacity or the ~3,000 RCU / 1,000 WCU per-partition ceiling returns ProvisionedThroughputExceededException with throttling.

Egnyte

Integration surface
REST Public API (pubapi/v1) with File System, Users, Groups, Permissions, Links, Metadata, Events, and Webhooks endpoints
Authentication
OAuth 2.0 scoped access tokens (Authorization Code or Implicit for partner apps, Resource Owner Password for internal apps, Refresh Token flow); token sent in the Authorization header
Change detection
Events API polled with an incremental cursor (Egnyte recommends an interval of 5 minutes or more), or Webhooks push notifications for fs, metadata, permission, and comment events
Capabilities
read · write · webhooks
Rate limits
Auto-generated keys default to 2 requests/second and 1,000 requests/day, enforced per access token; monitor X-Accesstoken-Qps-Current/Allotted and X-Accesstoken-Quota-Current headers; higher limits on request
How it works

How to connect Amazon DynamoDB to Egnyte — 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 DynamoDB and Egnyte 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 DynamoDB connected
    Egnyte connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Amazon DynamoDB and Egnyte 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 DynamoDB ⇄ Egnyte
    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 DynamoDB Egnyte
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Amazon DynamoDB and Egnyte 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 529 integrations available for Amazon DynamoDB and Egnyte.

Popular · 7 of 529
All Amazon DynamoDB integrations All Egnyte 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