> This page is for Data Protection.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.eon.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.eon.io/_mcp/server.

# DynamoDB: Restore a Table

This article explains how to restore a DynamoDB table from your Eon snapshots.

## Restore the table

#### Before you start

Before you restore a DynamoDB table, make sure:

* A [restore account has been connected] to your Eon account.

[restore account has been connected]: /data-protection/restoring/restore-accounts/about-restore-accounts

#### Find the snapshot you want to restore

1. In your

   inventory

   , select the DynamoDB table you want to restore.
   The Resource Details drawer opens.

2. Click the **Eon snapshots** tab.
   You'll see a calendar view with colored dots on the days when snapshots were taken.
   There can be more than one snapshot per day.

   When you click a day, a list of Eon snapshots taken that day is displayed below the calendar.

3. Select the snapshot you want to restore, and then click **Restore**.
   The **Restore DynamoDB** wizard opens.

#### Choose the restore account

In the Restore DynamoDB wizard, you're taken through a two-step process.
The first step is to choose a restore account.

Choose the cloud account you want to restore the table in, and then click **Next**.

#### Set the table details

1. Choose a **Table name** and **Region** for the restored table.
   If you specify the name of an existing table, Eon restores the data to that table.

2. In **Encrypt this resource**, select **Select an existing key** to choose from your available keys, or select **Enter a key ARN** and provide the KMS key ARN.

3. To retain the tags that were present when the snapshot was taken, leave **Keep original tags** on.
   Otherwise, turn it off.

   All restored tables are tagged with `eon:restore=true` regardless of this setting.
   Tags with the `eon:` prefix aren't included in the original tags because Eon uses this prefix for internal operations.

   > **Warning**
   >
   > When using import from S3, tags can be applied only after table creation.
   > If your AWS environment enforces tag policies that require tags on resource creation, use direct restore instead.

#### Choose secondary indexes

Choose which secondary indexes to restore.
The restore method determines which index types are supported.
For a full comparison, see [Restoring].

To restore all indexes from the snapshot, leave **Include all secondary indexes** on.

To choose individually, turn **Include all secondary indexes** off.
Then set **Global secondary indexes (GSI)** and **Local secondary indexes (LSI)** to **Include** or **Exclude**.

> **Note**
>
> If you include LSIs, only the direct restore method is available in the next step.

[Restoring]: /data-protection/cloud-workloads/aws/resources/dynamodb#restoring

#### Choose a restore method

By default, **Use automatic restore method** is on, which allows Eon to choose the best restore method based on the specified restore options.
For a comparison of both methods, see [Restoring].

To choose manually, turn **Use automatic restore method** off and select **Import via S3** or **Direct restore**.

If using direct restore, configure the write capacity under **Select write mode**:

* **Provisioned**: Set the **Write capacity units** for the restore.
  Higher values restore faster but require sufficient account quota.
  See [Direct restore] for sizing guidance.

* **On-demand**: No capacity management needed, but costs significantly more than provisioned mode.

[Direct restore]: /data-protection/cloud-workloads/aws/resources/dynamodb#direct-restore

#### Start the restore job

Click **Restore** to start the asynchronous restore job.

You can see your list of restore jobs on the

Restore jobs tab

in the Jobs page.

After the job is completed, the status changes to **SUCCESS**, and you can work with the restored table as normal.
If you run into issues, see [Restore troubleshooting].

[Restore troubleshooting]: /data-protection/cloud-workloads/aws/resources/dynamodb#restore-troubleshooting