Skip to main content
RDS Bulk Output lets users load the contents of a table (or view) into a table in an Amazon RDS database.
To read data from an Amazon RDS database instead of writing to one, use the RDS Query component.
If you’re using a Matillion Full SaaS solution, you may need to allow these IP address ranges from which Full SaaS Maia runners will call out to their source systems or to cloud data platforms.
Currently, you may need to manually enter the endpoint.

Properties

string
required
A human-readable name for the component.
drop-down
required
Select the database type.
drop-down
required
Your RDS database endpoint. If the IAM role attached to the instance (or the manually entered credentials associated with the current environment) has the permissions granted to query the RDS endpoints, you may select the RDS endpoint from a list. Otherwise, you must enter it manually—it can be found in the RDS console and is a long dotted-name and port number, separated by a colon. To acquire your database endpoint and provide it manually, follow these steps:
  1. Log in to the AWS Console.
  2. In the Find Services search bar, search for RDS.
  3. In the Amazon RDS navigation column on the left side of your screen, click Databases.
  4. Select a database.
  5. Locate the endpoint for that database in the Connectivity & security section.
Users must include the port number when manually typing the endpoint.
string
required
Provide the name of the database within your RDS instance. In the AWS Console, this is the “DB identifier”.
string
required
The RDS connection username.
drop-down
required
Choose the secret definition that represents your credentials for this connector.If you have not already saved your credentials for this connector as a secret definition, click Add secret to create a secret definition representing these credentials. Read Secrets and secret definitions for details about creating a secret definition.
column editor
  • Parameter: A JDBC parameter supported by the database driver. The available parameters are explained in the data model. Manual setup is not usually required, since sensible defaults are assumed.
  • Value: A value for the given parameter.
drop-down
required
The Snowflake database. The special value [Environment Default] uses the database defined in the environment. Read Databases, Tables and Views - Overview to learn more.
drop-down
required
The Snowflake schema. The special value [Environment Default] uses the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.
drop-down
required
The table (or view) on your cluster to copy to RDS.
string
required
A name for the new table.
string
required
A schema in the target database. Required if the RDS Type is PostgreSQL or SQL Server.
object selector
Select the columns to load. Leave this blank to load all columns.
drop-down
required
  • None: Assume the RDS database already has the table defined with the correct structure.
  • Create if not exists: Only create the table if it doesn’t already exist.
  • Replace: Always drop and recreate the table.
object selector
Select one or more columns to use as the table’s primary key. The component uses the primary key to identify matching rows in the target table when determining the update strategy.If you select multiple columns, the component creates a composite primary key using the combination of the selected columns.Leave this blank to load all rows without duplicate checking.
drop-down
required
Select how the output will handle replacing rows with matching primary keys. Options are:
  • Ignore: Any existing row in the target that matches the primary key is not replaced and the matching row from the source table is not uploaded.
  • Replace: Rows in the target table that match the primary key are replaced with the matching rows from the source table.
yes/no
required
Whether or not to truncate the target table before loading data.
drop-down
required
Choose whether to continue with the load if an error is raised, or to fail the run.
column editor
Any additional options that you want to apply to the copy operation. Some of these may conflict with the options the component already sets—in particular, care is taken to escape the data to ensure it loads into the target database even if the data contains row and/or column delimiters, so you should never override the escape or delimiter options.
integer
This is optional, and specifies the number of rows to load to the target between each commit. On a very large export, this may be desirable to keep the size of the Amazon RDS log files from growing very large before the data is committed.