Snowflake target

target-snowflake loads Singer records through staged CSV files and supports native FastSync for selected database sources.

Support
Target	Status	Native transfer
Snowflake	Available	FullSync from MariaDB/MySQL, PostgreSQL, or MongoDB; PartialSync from MariaDB/MySQL or PostgreSQL

Prerequisites

Create these Snowflake objects before importing a pipeline:

a warehouse used for loading;
a target role and user;
an external S3 stage; and
a named CSV file format.

The role needs warehouse usage, database usage, schema creation, and usage on the stage and file format. Grant ownership or table privileges only where the target must create, merge, alter, or replace tables.

Example stage and file format:

CREATE STAGE <database>.<schema>.<stage>
  URL = 's3://<bucket>';

CREATE FILE FORMAT <database>.<schema>.<file_format>
  TYPE = 'CSV'
  ESCAPE = '\\'
  FIELD_OPTIONALLY_ENCLOSED_BY = '"';

Use a storage integration, instance role, or AWS profile where possible. If the stage uses client-side encryption, configure the same master key in PipelineWise.

aws_profile falls back to AWS_PROFILE. aws_access_key_id, aws_secret_access_key, and aws_session_token fall back to AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_SESSION_TOKEN. Configure the access-key ID and secret together; add the session token for temporary credentials. With none configured, Boto3 uses its default credential chain.

Configuration

id: "snowflake"
name: "Analytics Snowflake"
type: "target-snowflake"
db_conn:
  account: "<ACCOUNT>"
  dbname: "<DATABASE>"
  user: "<USER>"
  private_key: "/run/secrets/snowflake-key.pem"
  warehouse: "<WAREHOUSE>"
  s3_bucket: "<STAGING_BUCKET>"
  s3_key_prefix: "pipelinewise/"
  stage: "<SCHEMA>.<STAGE>"
  file_format: "<SCHEMA>.<FILE_FORMAT>"
  iceberg_create: false

Connector-specific settings
Setting	Required	Default	Effect
`account` / `dbname`	Yes	—	Snowflake account and target database.
`user` / `private_key`	Yes	—	Key-pair authentication for the target role.
`warehouse`	Yes	—	Warehouse used for load and merge statements.
`s3_bucket` / `s3_key_prefix`	Yes	—	Staging location used by target loads.
`aws_profile`	No	`AWS_PROFILE`	Selects a named profile when no static key pair is configured.
`aws_access_key_id` / `aws_secret_access_key`	No	AWS environment	Supplies a static credential pair; encrypt both YAML values.
`aws_session_token`	With temporary keys	`AWS_SESSION_TOKEN`	Completes temporary static credentials.
`s3_acl`	No	None	Applies a canned ACL to staged uploads. Leave unset for bucket-owner-enforced buckets.
`stage` / `file_format`	Yes	—	Pre-created Snowflake objects used by `COPY` and `MERGE`.
`client_side_encryption_master_key`	No	None	Encrypts staged files using the stage’s matching master key.
`iceberg_create`	No	`false`	Creates new Singer-path tables as managed Iceberg tables.
`max_parallelism`	No	`16`	Caps automatic Singer stream-flush threads. Configure this in the target `db_conn`; tap-level `parallelism_max` is currently ineffective.

Generate the full template with pipelinewise init. Common target and tap-side batch settings are documented in YAML configuration.

Publication and grants

MariaDB/MySQL and PostgreSQL FastSync apply configured select roles only after a table is published. They do not grant schema-wide access while an obfuscated _TEMP staging table may exist. When adding a role, sync each existing table that needs the role or grant it explicitly. MongoDB FastSync retains its legacy schema-wide grant behaviour.

Iceberg tables

Singer-path loads can create new managed Iceberg tables. FastSync and PartialSync cannot currently create or load Iceberg tables. Existing native tables can be converted with the bundled utility. See Snowflake Iceberg tables for prerequisites, cutover, limitations, and recovery.