Enable PITR on an existing table: `aws dynamodb update-continuous-backups --table-name MyTable --point-in-time-recovery-specification PointInTimeRecoveryEnabled=true`.
Confirm PITR is active: `aws dynamodb describe-continuous-backups --table-name MyTable` — check `PointInTimeRecoveryStatus` is ENABLED.
To restore, call `aws dynamodb restore-table-to-point-in-time --source-table-name MyTable --target-table-name MyTable-Restored --restore-date-time <ISO8601_TIMESTAMP>` — restores to a new table.
Wait for the restore to complete by polling `aws dynamodb describe-table --table-name MyTable-Restored` until status is ACTIVE.
Validate data in the restored table, then update application config or swap table references as needed.
Known gotchas
PITR restores create a new table; you must update application endpoints or rename tables (DynamoDB does not support rename — export/reimport may be needed for a rename).
PITR retention window is 35 days — restores beyond that window are not possible; for longer retention use on-demand or scheduled backups.
GSIs, LSIs, and streams are restored, but TTL settings and auto-scaling policies must be re-applied manually on the restored table.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp