Integrations · Data warehouses · Available now
Amazon Redshift test data, inside your network
Dedicated Redshift connector on the PostgreSQL protocol with Redshift's own system views: svv_tables/svv_columns discovery, declared keys, svv_table_info row estimates, bounded aggregate profiles and server-side-cursor reads into the local engine, over verified TLS.
Available now Data warehouses
Shipped in the standard agent and backed by recorded conformance evidence.
What works today
Dedicated Redshift connector on the PostgreSQL protocol with Redshift's own system views: svv_tables/svv_columns discovery, declared keys, svv_table_info row estimates, bounded aggregate profiles and server-side-cursor reads into the local engine, over verified TLS.
Database user and password as a secret reference. sslmode defaults to verify-full; every session sets statement_timeout and a query_group label for cost attribution. Redshift is not PostgreSQL: it has its own connector and its own conformance record.
Authentication: database user and password (secret reference).
Known limitations
- Requires agent 0.4.1 or later: earlier agents cannot prove a Redshift credential read-only (its driver, psycopg, ships in the standard agent image).
- Database user and password only; IAM temporary credentials and identity-provider federation are not supported yet.
- Primary and foreign keys are informational in Redshift (never enforced); relationships are only as good as the declarations.
- External (Spectrum) and datashare objects are not read.
- Run against a real Redshift Serverless workgroup (8 RPU); provisioned clusters are not yet tested. No local engine exists and PostgreSQL runs are not accepted as Redshift evidence.
Capability matrix
Each capability is tracked separately and shown at the level the recorded conformance evidence supports. A connector that only discovers metadata is never presented as equivalent to one that runs the whole workflow.
| Capability | Level |
|---|---|
| Discovery | Supported |
| Classification | Supported |
| Profiling | Supported |
| Masking | Supported |
| Deterministic masking | Supported |
| Entity-aware subsetting | Supported |
| Relationship preservation | Supported |
| Synthetic workflows | Supported |
| Certification | Supported |
| Provisioning | Supported |
| CI/CD | Supported |
| Evidence generation | Supported |
Read-only proof
Proven from Redshift's permission model before reading: the user must not be a superuser or have CREATEDB; it must hold no CREATE on the database or any schema, no INSERT, UPDATE, DELETE or DROP on any visible relation (has_table_privilege, which includes group, role and PUBLIC grants), no write privilege in svv_relation_privileges, no system role other than sys:monitor and no write-capable system privilege. One built-in grant is ignored: Redshift's own PUBLIC UPDATE on pg_catalog.pg_settings (the view behind SET, which changes only the session's settings and cannot be revoked); any other write grant refuses the source.
Conformance evidence
DataNivra runs every connector through a common conformance kit on synthetic data: no write statements, proven read-only access, secret redaction, schema and relationship discovery, bounded streaming, cancellation, clear reason codes, egress canaries and no raw values in logs, then the discover, mask, subset, certify and provision workflow. The published status is computed from those results.
| Engine or service | Version | Environment | Driver | Authentication | Verified on |
|---|---|---|---|---|---|
| Amazon Redshift | service | managed-service | psycopg 3.3.6 | password | 2026-10-12 |
Connector version 0.1.0, last verified 2026-10-12.
What crosses the boundary
Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:
- Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
- Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
- Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
- Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.
Never sent:
- Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
- Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
- Free text copied from your data, or exception messages that contain values.
See the customer-resident architecture and how to verify these claims yourself.
Setup outline
- Use agent 0.4.1 or later: earlier agents cannot prove a Redshift user read-only (the standard agent image includes the driver, psycopg).
- Create a dedicated database user with USAGE on the schemas to read and SELECT on their tables, and nothing else: not a superuser, no CREATEDB, no CREATE on the database or any schema, no INSERT, UPDATE, DELETE, DROP, ALTER or TRUNCATE, and no system role other than sys:monitor.
- Store the connection document with the password as a secret reference. TLS with certificate and host-name verification (verify-full) is the default; prefer and allow are not offered.
- In the console, register the source with the secret reference of that document (for example vault://tdm/source-connection) and the agent that can reach it, then run discovery.
- Before reading, the agent proves the user is read-only from Redshift’s own permission views and refuses to continue if it is not. The one grant it ignores is Redshift’s built-in PUBLIC UPDATE on pg_catalog.pg_settings, which only changes the session’s own settings and cannot be revoked. Keys are informational in Redshift, so relationships are only as good as the declarations.
Example connection document, stored in your secret store and resolved by the agent locally (DataNivra only ever sees its reference):
{
"kind": "AMAZON_REDSHIFT",
"host": "example-wg.123456789012.us-east-1.redshift-serverless.amazonaws.com",
"database": "dev",
"user": "tdm_reader",
"password_ref": "vault://tdm/claims-redshift#password",
"schemas": ["claims"]
}Next: install the agent, then follow the getting started guide.
All integrations · Data warehouse test data management · Guides · Start free