Connector Improvement: Allow AWS S3 with Access Key ID and Secret
Completed
Current AWS S3 connector only allows use of External ID and IAM roles. We get access to files in S3 from a third party (in this case, Toast) and they only offer Access ID and Secret Key as the means for authentication. Many other tools use this means to access S3, and the current AWS S3 implementation within Fivetran is centered around the concept that you are sharing your own AWS S3 bucket rather than having a third party share it to you.
-
Official comment
Hi Bob,
Thank you for taking the time to let us know about this need. This is a great feature enhancement request that we don't currently have a committed time line for. We will continue to collect customer demand to justify the commitment to expand our Fivetran connector functionality. Every upvote on this request increases the case to build it.
Best regards,
Alison
-
We would like to have that option too
-
We are in need of this as well. The current connector only works if the S3 bucket is in our own AWS Account. It's extremely rare, if not unheard of, for a vendor to give you anything but an access key and secret. We have resorted to using other SaaS tools to load data from vendor S3 buckets because of this deficiency within the Amazon S3 connector.
-
I agree 100% with Bryan - access keys are the industry standard for sharing S3 buckets.
For real-world use, your current connectivity method is extremely insecure, and violates all standard security best practices. We are the vendor, and would never expect a client to give us full AWS access simply for the convenience of accessing their reports through Fivetran.
Someone made a very poor, and questionable business decision on this.
-
I'm excited to let everyone know this feature is now live.
Happy data pipelining
Alison
Please sign in to leave a comment.
Comments
5 comments