Structural differences and limitations with DynamoDB

Amazon DynamoDB is a document-based database.

For workspaces that use DynamoDB, the Tonic Structural application has the following differences.

Terminology changes

On the following Structural views, the term "collection" replaces the term "table":

• Privacy Hub

• Schema Changes

References to columns are also replaced:

• On Privacy Hub, the protection status panels refer to "fields" instead of "columns".

• On the Schema Changes view, the change lists refer to "paths" instead of "columns".

Privacy Hub - Latest Collection Scan

For DynamoDB workspaces, Structural must scan each collection to determine the fields and data types within that collection. Until a scan is performed, you cannot configure the collection modes and generators.

For DynamoDB workspaces, Privacy Hub includes an additional Latest Collection Scan section that shows the most recent time that a scan was performed on each scanned collection.

For more information, go to Performing scans on collections.

No Privacy Report downloads

For DynamoDB workspaces, there are no options to download a Privacy Report CSV or PDF.

No workspace inheritance

DynamoDB workspaces do not support workspace inheritance.

Collection View replaces Database View and Table View

For DynamoDB workspaces, there is no Database View or Table View. Instead, DynamoDB workspaces have a Collection View.

This view allows you to perform the same functions as Table View, but the display is more like Database View. For more information, go to Using Collection View.

Collection mode (table mode) limitations

Collection mode is the term for table mode in DynamoDB workspaces.

DynamoDB only supports De-Identify, Truncate, and Preserve Destination modes.

Generator limitations

DynamoDB workspaces cannot use the following generators:

• Algebraic

• Alphanumeric Key

• Array Character Scramble

• Array JSON Mask

• Array Regex Mask

• Cross-Table Sum

• CSV Mask

• Event Timestamps

• HTML Mask

• JSON Mask

• SIN

• Timestamp Shift

• URL

Self-consistency only

DynamoDB workspaces only support self-consistency.

You cannot make a DynamoDB field consistent with another field.

No subsetting

DynamoDB workspaces do not support subsetting.

No upsert

DynamoDB workspaces do not support upsert.

No output to a container repository

For DynamoDB workspaces, you cannot write the destination data to a container repository.

No output to an Ephemeral snapshot

For DynamoDB workspaces, you cannot write the destination data to an Ephemeral snapshot.

No post-job scripts

For DynamoDB workspaces, there is no option to run post-job scripts after a job.

You can create webhooks that are triggered by data generation jobs.