# Can't add s3 data source

**URL:** <https://community.dremio.com/t/cant-add-s3-data-source/4199>\
**Category:** Uncategorized\
**Created:** [September 27, 2019, 7:43pm UTC](https://community.dremio.com/t/cant-add-s3-data-source/4199 "2019-09-27T19:43:29Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![eellsworth](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/eellsworth/32/2643_2.png) [@eellsworth](https://community.dremio.com/u/eellsworth)\
**Post date:** [December 21, 2020, 6:00pm UTC](https://community.dremio.com/t/cant-add-s3-data-source/4199/19 "2020-12-21T18:00:55Z")

</div>

Hi @balaji.ramaswamy,  
I am having a similar issue with Wasabi S3 buckets (like Minio).

> [@S3 bucket from non-Amazon provider](https://community.dremio.com/t/s3-bucket-from-non-amazon-provider/6755/3):
>
> Ben, Thanks so much for this advice! Unfortunately I can’t seem to get Dremio to connect to the wasabi host ([s3.wasabisys.com](http://s3.wasabisys.com)). Here are the parameters I used: The exceptions sometimes show Dremio attempting to connect to [sts.amazonaws.com](http://sts.amazonaws.com), and other times don’t list host names - they never show traffic to [s3.wasabisys.com](http://s3.wasabisys.com) at com.dremio.plugins.s3.store.STSCredentialProviderV1.getCredentials(STSCredentialProviderV1.java:71) at org.apache.hadoop.fs.s3a.AWSCredentialProvid…

@Ben kindly helped me, but I thought I’d loop you in in case you had seen this.  
It appears the Dremio S3 layer is trying to authenticate against AWS rather than Wasabi. Is there a property or configuration that would force Dremio to authenticate against Wasabi?

Thanks,

Eric

---

_[View the full topic](https://community.dremio.com/t/cant-add-s3-data-source/4199)._