Real-time
Two-way sync
Changes in Dynamo DB or Splunk instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Analytics
Dynamo DB to Splunk integration — real-time, two-way sync
Keep Dynamo DB and Splunk 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 Dynamo DB and Splunk
Give Splunk the users, events, and records that live in Dynamo DB in real time, and sync the cohorts and scores Splunk computes back into Dynamo DB where your applications read them.
A database holds the rows your business runs on: the users, events, orders, and records that every service reads and writes. Splunk is where people make sense of them, as dashboards, funnels, cohorts, and metrics. Moving the data from Dynamo DB into Splunk usually means a hand-built extract or a change-data-capture pipeline that breaks the moment a column is renamed, and reporting that always trails last night's load.
Stacksync syncs Global Tables, Tables, Items, Attributes in Dynamo DB with Fired Alerts, KV Store Collections, Indexes, HTTP Event Collector in Splunk in real time and in both directions. Operational rows flow into Splunk as they change, so dashboards read current data with no pipeline to maintain, and the segments, cohorts, or scores Splunk computes flow back into Dynamo DB, where the applications and services that read from it get them at normal query latency. Field-level mapping, schema and type translation, and conflict resolution are handled for you.
Common use cases
- 01 Read and write KV Store collections to keep Splunk lookups — asset inventories, allow/deny lists, enrichment tables — in sync with an external source of truth in both directions.
- 02 Provision and update Saved Searches, alerts, and Dashboards from a Git-backed config repository so detections and reports stay versioned and consistent across search heads.
- 03 Consolidate multi-region Global Tables data into a single reporting store.
- 04 Replace ad-hoc export scripts with continuous sync driven by DynamoDB Streams.
Common sync patterns
Where Splunk builds cohorts or scores: results your services can read
Segments, cohorts, or scores computed in Splunk sync back into Dynamo DB, where the services that read from the database act on them at query speed without calling the analytics API.
Analytics on live operational data, minus the pipeline
The users, events, orders, and records stored in Dynamo DB land in Splunk as they change, so dashboards, funnels, and metrics run on current data instead of last night's extract.
One version of each user or account
A user, account, or record corrected in either system updates the other, so the identity your reports group by matches the identity your database stores.
What you can sync between Dynamo DB and Splunk
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.
| Dynamo DB objects | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Partition and Sort Keys The primary key pair used as the match key for bi-directional sync. | Indexes Index inventory and settings (retention, max size, event counts) via /services/data/indexes, with create and edit; loaded into a database for capacity, retention, and data-onboarding tracking. | Partition and Sort Keys is specific to Dynamo DB and Indexes to Splunk — each maps to any object or custom field on the other side. | |
| Global Secondary Indexes Alternate access paths used when sync queries filter on non-key attributes. | HTTP Event Collector The write-in path: POST events and metrics to /services/collector (port 8088, or 443 on Splunk Cloud) authenticated with a per-input HEC token, so external records are indexed alongside logs for search and correlation. | Global Secondary Indexes is specific to Dynamo DB and HTTP Event Collector to Splunk — each maps to any object or custom field on the other side. | |
| DynamoDB Streams Ordered item-level change records consumed for incremental sync. | Users and Roles Accounts at /services/authentication/users and role/capability definitions at /services/authorization/roles, with full CRUD; exported for access reviews or provisioned from an identity source of truth. | DynamoDB Streams is specific to Dynamo DB and Users and Roles to Splunk — each maps to any object or custom field on the other side. | |
| Global Tables Multi-region replicas relevant when syncs must read from a specific region. | Dashboards Simple XML dashboard and view definitions at /servicesNS/{owner}/{app}/data/ui/views; exported for backup and audit, or created and updated programmatically from version control. | Global Tables is specific to Dynamo DB and Dashboards to Splunk — each maps to any object or custom field on the other side. | |
| Tables The top-level containers a sync targets; each table is addressed independently. | Search Results SPL searches dispatched via POST /services/search/jobs return a search ID (SID); results are pulled from /services/search/jobs/{sid}/results once the job completes, or synchronously via oneshot/export mode. The primary read path for streaming indexed events out to a warehouse. | Tables is specific to Dynamo DB and Search Results to Splunk — each maps to any object or custom field on the other side. | |
| Items Schemaless records keyed by partition (and optional sort) key, mapped to rows or SaaS objects in syncs. | Saved Searches Scheduled searches, reports, and the definitions behind alerts at /services/saved/searches with full create, update, and delete. Read out for governance and coverage review, or provisioned and updated from a config source. | Items is specific to Dynamo DB and Saved Searches to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Dynamo DB and Splunk
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.
Dynamo DB Splunk Sub-second propagation
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 Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Dynamo DB Sub-second propagation
DetectionSplunk notifies Stacksync of record changes through webhook events. Time-range searches over indexed events (earliest/latest on _time or _indextime).
DeliveryEach detected change is applied to Dynamo DB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Dynamo DB: Throughput is governed by the table's provisioned or on-demand capacity mode.
- Splunk: The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
What ships with Dynamo DB ⇄ Splunk
Connect Dynamo DB and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamo DB–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dynamo DB or Splunk 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 Dynamo DB or Splunk record.
Observability
Monitoring
Track your Dynamo DB ⇄ Splunk sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Dynamo DB and Splunk.
How the Dynamo DB and Splunk connectors work
Dynamo DB
- Integration surface
- Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries
- Authentication
- AWS IAM credentials with SigV4 request signing
- Change detection
- Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration
- Capabilities
- read · write · CDC
- Rate limits
- Throughput is governed by the table's provisioned or on-demand capacity mode
Splunk
- Integration surface
- REST API (management API + HTTP Event Collector)
- Authentication
- HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud).
- Change detection
- Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action.
- Capabilities
- read · write · webhooks
- Rate limits
- The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
How it works
How to connect Dynamo DB to Splunk — 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.
- 01
Connect your apps
Authenticate Dynamo DB and Splunk with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Dynamo DB
connected
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dynamo DB and Splunk 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.
objects · Dynamo DB ⇄ SplunkCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Dynamo DB SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dynamo DB and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Dynamo DB and Splunk: authenticate both systems, choose the objects to sync (such as Dynamo DB's Partition and Sort Keys and Global Secondary Indexes), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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. Splunk: REST API (management API + HTTP Event Collector). Authentication: HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud). Stacksync manages authentication, retries, and rate limits on both sides.
-
Splunk: The KV Store is a MongoDB-backed, app-scoped collection store with full CRUD and batch endpoints (/servicesNS/{owner}/{app}/storage/collections/data/{collection}), so lookup records can be read and written in both directions. Dynamo DB: PartiQL provides a SQL-compatible query layer over the same key-based access model. Stacksync's field mapping accounts for these differences between Dynamo DB and Splunk 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 Dynamo DB and Splunk records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Dynamo DB and Splunk connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dynamo DB–Splunk integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Dynamo DB and Splunk. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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
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 422 integrations available for Dynamo DB and Splunk.
Popular · 7 of 422
-
Dynamo DB ⇄ Mixpanel -
Dynamo DB ⇄ Microsoft Power Bi -
Dynamo DB ⇄ Tableau -
Splunk ⇄ Google AlloyDB -
Splunk ⇄ IBM Db2 -
Splunk ⇄ Firebase -
Splunk ⇄ SingleStore
No integrations match .
