Hi. The Airbyte Snowflake connector has 4 differen...
# replication-troubleshooting
a
Hi. The Airbyte Snowflake connector has 4 different dataload options (Snowflake’s Internal Stage, AWS S3, GC Bucket, Azure Blob). I was wondering what the benefit would be in not using Snowflake’s Internal Stage but to stage via one of the other storage mechanisms. Would I see any performance/cost benefit if I’m loading from an AWS Aurora MySQL DB to Snowflake and Airbyte is hosted outside of AWS by using the S3 storage data loading method?
✍️ 1
u
@[DEPRECATED] Marcos Marx turned this message into Zendesk ticket 2919 to ensure timely resolution!
r
I suspect it's to support the existing staging options available from Snowflake
If you use a stage in s3 already, you can do so in Airbyte!
s
Yeah, these reflect Snowflake's staging options: https://docs.snowflake.com/en/user-guide/data-load-overview.html#supported-file-locations What you choose really depends on your requirements. Internal stages make sense for most users, they're easier for a few reasons particularly that you don't have to manage the extra credentials etc and yes the data would transit an extra hop back to AWS. But if you need to access or audit the staged files, S3 or another cloud storage provider would make that a lot easier since they usually have a feature to auto archive whatever data had been stored there.