Question 1

Why send Redshift data to Azure storage?

Accepted Answer

Almost always because the consumer sits in a Microsoft centred estate. A reporting layer, a data platform or a processing job running in Azure cannot easily reach a cluster inside AWS, and files in a container are the neutral handoff. It also suits organisations whose retention and compliance tooling is built around Azure, since the archive then falls under the same policies as everything else they keep.

Question 2

What credentials are needed on each side?

Accepted Answer

Redshift takes cluster details and credentials, plus an SSH tunnel if the cluster is not publicly reachable and an S3 staging bucket as part of the connection. Azure takes a storage account and container along with one of an account key, a SAS token, service principal credentials, or OAuth. Which Azure credential you choose has no bearing on formats, paths or write behaviour, so pick whichever matches how your organisation handles cloud identity.

Question 3

How do the write modes differ?

Accepted Answer

Replicate maintains one stable object replaced on every run, which suits a consumer pointed at a fixed path indefinitely. Snapshot writes a new timestamped object per run, which builds history in the container. An incremental option on replicate writes only changed records as new timestamped files, which suits a downstream process consuming deltas. Output subfolders and names accept datetime expressions, so files can organise themselves by date.

Question 4

What should I watch on cost and load?

Accepted Answer

Two separate things. On the Redshift side the constraint is cluster compute rather than a per query charge, so put the connecting user in a suitable workload management queue, use a tracking field, and keep the column list tight. Separately, moving data out of AWS and into Azure incurs cross cloud egress. Neither matters much for a modest daily export, but both are worth checking before running a wide table frequently.

Question 5

How do I connect Redshift to Azure Blob Storage?

Accepted Answer

Connect Redshift with cluster details, credentials and an S3 staging bucket, adding an SSH tunnel if the cluster is private, then connect Blob Storage with an account key, SAS token, service principal, or OAuth, naming the storage account and container. After that, choose the Redshift data to export, the output format, and whether each run replaces one object or writes a new timestamped one.

Connect Redshift with Azure Blob Storage

Connect Redshift and Azure Blob Storage with Polytomic

Several Azure credential types

Typed output with Parquet

Stable file or history

Trusted by businesses worldwide

Step-by-step integration guide

Connect Redshift in Polytomic

Connect Azure Blob Storage in Polytomic

Create a sync between Redshift and Azure Blob Storage

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect Redshift with Azure Blob Storage?