CREATE ANALYTICS REPLICA — move reporting off the live table

View .md

When a report should stop reading the live table, provision a DynamoDB to Amazon S3 Tables zero-ETL replica. DynoStudio expands the statement into the ordered AWS setup plan — PITR and resource-policy checks, the S3 Tables bucket and analytics catalog, Lake Formation and Glue wiring, the IAM service role, and the integration itself — with every native call, likely permission gap, and recurring cost line previewed before consent.

Syntax

sql 
CREATE ANALYTICS REPLICA [IF NOT EXISTS] FOR TABLE "table"  [WITH (refresh_interval = INTERVAL 'n' HOUR, unnest = FULL)]​ALTER ANALYTICS REPLICA FOR TABLE "table" SET setting = value​DROP ANALYTICS REPLICA FOR TABLE "table"

Routing stays explicit: DynoStudio does not silently reroute a live-table query — replica reads carry their own engine and cost disclosure when routed there, just as Query vs Scan is visible today. Guide: Tables, indexes & replicas.

Use cases

Provision a replica (resume-friendly) Lowered

Stand up the analytics copy of a busy orders table. IF NOT EXISTS makes the create path resumable — a provision that stopped partway continues from the saved step instead of re-minting resources.

sql 
CREATE ANALYTICS REPLICA IF NOT EXISTS FOR TABLE "stage.Orders"  WITH (refresh_interval = INTERVAL '1' HOUR, unnest = FULL)
Executes asOrdered plan: PITR check → S3 Tables bucket + catalog → Lake Formation/Glue wiring → IAM role → Glue integration
  • The preview lists the plan's native calls, the permissions it will likely need, and the recurring cost lines — consent comes after the disclosure, never before.
Slow the refresh cadence down Lowered

The report runs daily; an hourly refresh buys nothing. ALTER … SET updates supported settings — and warns when a change can force a full resync.

sql 
ALTER ANALYTICS REPLICA FOR TABLE "stage.Orders"  SET refresh_interval = INTERVAL '12' HOUR
Executes asUpdate integration settings · warns if the change forces a full resync
Tear the replica down Lowered

Reporting moved elsewhere — remove the integration through the same gated control-plane path it was created by.

sql 
DROP ANALYTICS REPLICA FOR TABLE "stage.Orders"
Executes asGated teardown of the zero-ETL integration

Try it

Try it · ANALYTICS REPLICASample
Run it live in DynoStudio →
Executes asProvisioning plan · stage.Orders → S3 Tables
1 PITR/policy checks → 2 S3 Tables bucket + catalog → 3 Lake Formation/Glue wiring → 4 IAM service role → 5 Glue zero-ETL integration
Five ordered steps, each a disclosed native call — the preview also lists likely permission gaps and recurring costs.
Nothing provisions until you consent to the previewed plan.
Plan previewed · 5 steps · recurring costs listed · awaiting consent

Related: Tables, indexes & replicas · Aggregates & profiling for the folds that push tables toward a replica · the DynoStudio overview for the Analytics surface.

Was this page helpful?