Amazon DynamoDB
Seeding orders into a destination table that , with and .
| orderId | expiresAt | What the run does |
|---|---|---|
order-1001 | WrittenExpires after the cutoff | |
order-1002 | Left outExpired at the cutoff | |
order-1003 | WrittenNo TTL value | |
order-1004 | WrittenMore than five years before the cutoff: not counted as expired | |
order-1005In the destination | Already there, the sameExpires after the cutoff | |
order-1006In the destination | Left as it is: it differsExpires after the cutoff |
3 written, 1 left out, 1 already there, 1 left as it is.
Change an expiresAt value to try your items. The rules are Douklar's; the table, its items and the cutoff, 2026-10-01T00:00:00.000Z, are samples. The console proposes the time of preflight as the cutoff, and Exclude expired at cutoff needs TTL turned on for the source table.
- What moves
- Items that are missing from an existing table
- Your choices
- Keep every item, or leave out items whose TTL has expired
How it moves
- Checks table and key compatibility and an approximate item-count ceiling first.
- Asks for a TTL decision per mapping: keep everything, or leave out items expired at a recorded cutoff.
- Strong per-item reads after copying.
Limits
- Seeds an existing table; it does not create tables or indexes, or change TTL, capacity, streams or policies.
- Items already in the destination are left as they are.
- Scan-based: it uses read capacity and has no snapshot isolation.
For a full-table move into a new table, DynamoDB export and import is the better tool.