Skip to content

Advanced configuration — AWS DynamoDB Discovery

For general Discovery connector options (scan targets, formats), see Advanced configuration for Discovery connectors.

Include untagged DynamoDB tables in classification search (Solr)

By default, table-level DynamoDB resources that have schema/metadata but no data tags are not written to the classification Solr collection. When you enable the option below, those untagged tables are published (together with tagged resources) so they can appear in Discovery classification flows and APIs that read from Solr.

What you see for untagged data

For untagged tables and columns, Discovery lists table-level results only: one entry per table, with table schema (including column names and types) on that table record. Untagged columns do not appear as separate rows in classification search or the resourceinfo API. Tagged columns still appear as their own entries, in addition to the table.

Enable the feature

  1. In the Privacera Portal, open Settings > Data Source Registration, select your system, and open the AWS DynamoDB application (or use the Discovery Admin Console equivalent in Data Plane deployments).

  2. Under Application properties, set:

    privacera.discovery.dynamodb.untagged.tables.publish.to.solr = true

    Alternatively, for AWS Discovery installs, add DISCOVERY_DYNAMODB_UNTAGGED_TABLES_PUBLISH_TO_SOLR: "true" to config/custom-vars/vars.discovery.aws.yml (under Privacera Manager). 3. Run a new scan (or otherwise republish classification) so table-level resources are re-indexed with the new setting.

Scope

This property applies only to the AWS DynamoDB connector. Other database connectors do not use this setting.

After enabling — API behavior (GET /api/discovery/resourceinfo)

The resourceinfo endpoint queries classification Solr. To retrieve schema and tagging information for both tagged and untagged DynamoDB tables (once they exist in Solr):

  • Do not send the status query parameter, or ensure it is not set to Accepted (status=A).
    When status is Accepted, the service adds a Solr filter that requires resources to be tagged (is_tagged:true), which excludes untagged tables.

  • The examples in the Discovery Scan API user guide often use autoClassified=1 and manualReviewed=1. That combination restricts results to documents with certain classification flags. Untagged table rows may not satisfy those filters. To list all tables (tagged and untagged), omit autoClassified and manualReviewed from the request, or adjust them according to the classification states you need.

Untagged rows may return an empty tagsInfo (or no tags) while still including resourceMetaInfo (schema).

For curl examples and parameter reference, see Retrieve scan results — resourceinfo.