Configuring Amazon Redshift workspace data connections
During workspace creation, under Connection Type, click Redshift.
Connecting to the source database
In the Source Settings section, provide the details about the source database:
Specifying the source connection details
To provide the connection details for the source database:
In the Server field, provide the server where the database is located.
In the Database field, provide the name of the database.
In the Port field, provide the port to use to connect to the database.
In the Username field, provide the username for the account to use to connect to the database.
For the password, you can either specify the password manually, or you can select a secret name from a secrets manager. The selected secret must store a password. The secrets manager option is only available if you have configured at least one secrets manager. For information about configuring the available secrets managers, go to Configuring secrets managers for database connections. To enter the password manually:
Click Provide Password.
In the password field, enter the password.
To use a secret name from a secrets manager:
Click Use Secrets Manager.
From the secrets manager dropdown list, select the secrets manager. Structural connects to the secrets manager and retrieves a list of available secret names.
From the secret name dropdown list, select the secret name.
In the S3 Bucket Path field, specify the S3 bucket where Tonic Structural places temporary CSV files that it uses to load and unload Amazon Redshift tables. During data generation, CSV files containing the source data are copied to an
input
folder in the S3 bucket. After the generators are applied, CSV files containing the destination data are copied to anoutput
folder in the S3 bucket.To test the connection to the source database, click Test Source Connection.
Ensuring encryption of source database authentication
The Enable SSL/TLS setting indicates whether to encrypt source database authentication data.
By default, the toggle is in the on position. We strongly recommend that you do not turn off this setting.
Blocking data generation on all schema changes
By default, data generation is not blocked for schema changes that do not conflict with your workspace configuration.
To block data generation when there are any schema changes, regardless of whether they conflict with your workspace configuration, toggle Block data generation on schema changes to the on position.
Determining ownership in the destination database
By default, the source database owner relationships, such as schema and table ownership, are preserved in the destination database. The Preserve source database owners in destination database toggle is in the on position.
To instead have the admin user for the destination database gain ownership of the schema and tables, toggle Preserve source database owners in destination database to the off position.
Limiting the included schemas
By default, the source database includes all of the schemas. To specify a list of specific schemas to either include or exclude:
Toggle Limit Schemas to the on position.
From the filter option dropdown list, select whether to include or exclude the listed schemas.
In the field, provide the list of schemas to either include or exclude. Use commas or semicolons to separate the schemas.
Do not exclude schemas that are referred to by included schemas, unless you create those schemas manually outside of Structural.
Connecting to the destination database
In the Destination Settings section, you specify the connection information for the destination database.
Copying the source connection details
To copy the connection details from the source database:
Click Copy Settings from Source.
For the password, you can either specify the password manually, or you can select a secret name from a secrets manager. The selected secret must store a password. The secrets manager option only displays if at least one secrets manager is configured. For information about configuring the available secrets managers, go to Configuring secrets managers for database connections. To enter the password manually:
Click Provide Password.
In the password field, enter the password.
To use a secret name from a secrets manager:
Click Use Secrets Manager.
From the secrets manager dropdown list, select the secrets manager. Structural connects to the secrets manager and retrieves a list of available secret names.
From the secret name dropdown list, select the secret name.
To test the connection to the destination database, click Test Destination Connection.
Specifying the destination connection details
If you do not copy the source connection details, then to specify the connection information for the destination database:
In the Server field, provide the server where the database is located.
In the Database field, provide the name of the database.
In the Port field, provide the port to use to connect to the database.
In the Username field, provide the username for the account to use to connect to the database.
For the password, you can either specify the password manually, or you can select a secret name from a secrets manager. The selected secret must store a password. The secrets manager option only displays if at least one secrets manager is configured. For information about configuring the available secrets managers, go to Configuring secrets managers for database connections. To enter the password manually:
Click Provide Password.
In the password field, enter the password.
To use a secret name from a secrets manager:
Click Use Secrets Manager.
From the secrets manager dropdown list, select the secrets manager. Structural connects to the secrets manager and retrieves a list of available secret names.
From the secret name dropdown list, select the secret name.
To test the connection to the destination database, click Test Destination Connection.
Ensuring encryption of destination database authentication
The Enable SSL/TLS setting indicates whether to encrypt authentication data for the destination database.
By default, it is in the on position. We strongly recommend that you do not turn off this setting.
Last updated
Was this helpful?