S3 import & export

For moving large datasets, Tablyne drives DynamoDB’s own server-side ImportTable and ExportTableToPointInTime operations through S3 — no data flows through your machine.

When to use this

Use S3 import/export when the dataset is too big for the row-by-row import/export in the data grid. Because the work happens inside AWS, throughput isn’t limited by your connection, and import doesn’t consume table write capacity. The trade-off is that both operations are asynchronous and route through an S3 bucket.

Open the dialog from the data toolbar (S3 import/export). It has two independent sections: import on top, export below.

Importing from S3

Import always creates a brand-new table — it never writes into an existing one. You define the new table’s keys and point Tablyne at the source objects in S3.

Source

Field	Notes
Bucket	the S3 bucket holding your data
Prefix	optional key prefix (e.g. exports/2026/)
Format	DynamoDB JSON, CSV or Amazon Ion
Compression	NONE, GZIP or ZSTD
CSV delimiter	shown only for CSV; defaults to ,

New table

You specify the table name and key schema:

• Partition key (PK) + type (S, N, B)
• Sort key (SK) + type — optional

The new table is created with on-demand (PAY_PER_REQUEST) billing. You can adjust capacity afterwards in table settings.

Running and tracking it

Click Import. Tablyne issues ImportTable and gets back an ImportArn, then polls DescribeImport every few seconds, showing:

• the status (IN_PROGRESS → COMPLETED / FAILED / CANCELLED)
• the imported item count as it climbs
• a failure message if AWS reports one

On COMPLETED, a button refreshes your table list so the new table shows up. You can start another import with New import.

Table:   minha-tabela
Status:  COMPLETED
Items:   1,204,557

Exporting to S3

Export writes a snapshot of a table into an S3 bucket as DynamoDB JSON.

Requirements

• PITR must be enabled on the table. Export uses ExportTableToPointInTime, which reads from continuous backups — enable PITR in Backups & PITR first, or the export fails.
• A table must be selected (export targets the table currently open).

Running it

Enter a destination bucket and optional prefix, then click Export. Tablyne resolves the table’s ARN via DescribeTable, calls ExportTableToPointInTime, and returns an ExportArn confirming the job started.

The export then runs entirely inside AWS and lands the files in your bucket. Tablyne shows the ExportArn for reference but does not poll export progress — check the AWS Console or your bucket for completion.

Export format is always DynamoDB JSON. CSV is supported for import but not for export.

Limitations & notes

• Import creates a new table — pick a name that doesn’t already exist.
• Export needs PITR and produces DynamoDB-JSON only.
• The bucket must be in a region AWS allows for the operation, and the calling profile needs the relevant dynamodb: and s3: permissions.
• These are AWS-cloud features; against DynamoDB Local they’re generally unavailable.

Related

• Import & export — smaller, client-side data moves (JSON/CSV).
• Backups & PITR — enable PITR before exporting.
• Create table — define a table manually instead of via import.
• Concepts: the S3 import/export learn guide.