# AWS Bucket Access

**URL:** <https://community.dremio.com/t/aws-bucket-access/67>\
**Category:** Uncategorized\
**Created:** [July 20, 2017, 3:50am UTC](https://community.dremio.com/t/aws-bucket-access/67 "2017-07-20T03:50:10Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Venkat\_Krishnamurthy](https://avatars.discourse-cdn.com/v4/letter/v/278dde/32.png) [@Venkat\_Krishnamurthy](https://community.dremio.com/u/Venkat_Krishnamurthy)\
**Post date:** [July 20, 2017, 3:50am UTC](https://community.dremio.com/t/aws-bucket-access/67/1 "2017-07-20T03:50:10Z")

</div>

Hi - Just trying to get going with data in a public S3 bucket, but not sure how the config is supposed to work. I entered my credentials, and it says a bucket already exists at the path specified (which is true, and I want to load data from that bucket). If I try creating a new bucket, it fails. What should I be doing?

---

<div class="post-metadata">

**Author:** ![doron](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/doron/32/294_2.png) [@doron](https://community.dremio.com/u/doron)\
**Post date:** [July 20, 2017, 4:41pm UTC](https://community.dremio.com/t/aws-bucket-access/67/2 "2017-07-20T16:41:55Z")

</div>

Hi,

I believe you are running into a known issue. If you try to create a source called `Foo` and it fails (connection issues, invalid credentials) you won’t be able to use `Foo` as a Source name after the failure happens. Changing the Source name should allow you to save it successfully.

Doron

---

<div class="post-metadata">

**Author:** ![jacques](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/jacques/32/32_2.png) [@jacques](https://community.dremio.com/u/jacques)\
**Post date:** [July 20, 2017, 5:12pm UTC](https://community.dremio.com/t/aws-bucket-access/67/3 "2017-07-20T17:12:00Z")

</div>

The other possibility, given your description, I think you may be explicitly listing buckets for your account in the external buckets section of the configuration. You should only list buckets for external buckets, not ones under your account. Those ones are automatically made available. External buckets are used for things like publically accessible buckets. (For example, you can add [samples.dremio.com](http://samples.dremio.com) as an external bucket, and see that in addition to your internal buckets).

---

<div class="post-metadata">

**Author:** ![Venkat\_Krishnamurthy](https://avatars.discourse-cdn.com/v4/letter/v/278dde/32.png) [@Venkat\_Krishnamurthy](https://community.dremio.com/u/Venkat_Krishnamurthy)\
**Post date:** [July 20, 2017, 6:57pm UTC](https://community.dremio.com/t/aws-bucket-access/67/4 "2017-07-20T18:57:08Z")

</div>

Thanks.

Seems like my issue is now more basic - I enter my access ID/secret key, and the primary failure is ‘Failed to create workspaces for buckets in specified account’. I haven’t edited or added any external buckets - i only use the ‘name’ field under the ‘general’ section of the AWS config page. I’m assuming this refers to a bucket that Dremio will create, correct?

---

<div class="post-metadata">

**Author:** ![ron](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/ron/32/12_2.png) [@ron](https://community.dremio.com/u/ron)\
**Post date:** [July 20, 2017, 7:41pm UTC](https://community.dremio.com/t/aws-bucket-access/67/5 "2017-07-20T19:41:00Z")

</div>

When creating an Amazon S3 datasource, you provide a name for the Dremio datasource that you’ll use in building queries later. In the following screen shot, what else did you provide other than Name, AWS Access Key, AWS Access Secret?

 ![](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/1X/855b187c14e545e74d0342e5ebf35c45023edcf0.png)

---

<div class="post-metadata">

**Author:** ![nauman](https://avatars.discourse-cdn.com/v4/letter/n/779978/32.png) [@nauman](https://community.dremio.com/u/nauman)\
**Post date:** [July 20, 2017, 10:28pm UTC](https://community.dremio.com/t/aws-bucket-access/67/6 "2017-07-20T22:28:37Z")

</div>

hi Venkat,

It looks like you are trying to connect to a public S3 bucket.

Below is a sample of how to access public S3 buckets - you only need to specify a logical name for the S3 data source (eg, “samples” from below) and you will need to specify the public bucket name (eg: [samples.dremio.com](http://samples.dremio.com)) in the “External Buckets” section and click Add (note you can add multiple public buckets).

 ![](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/1X/72487b021cd812e92da098cc665256980cac6e8f.png)

  
  

If you are trying to connect to buckets in your protected S3 account, instead of public S3 buckets, then you will need to enter your aws access id and key as Ron shows above in his screenshot. When you click save, Dremio will list all the buckets associated with your AWS account automatically (you do not need to add any bucket names explicitly). You can then start browsing, manipulating and querying data in your S3 buckets.

Let us know if this works for you.

---

<div class="post-metadata">

**Author:** ![Venkat\_Krishnamurthy](https://avatars.discourse-cdn.com/v4/letter/v/278dde/32.png) [@Venkat\_Krishnamurthy](https://community.dremio.com/u/Venkat_Krishnamurthy)\
**Post date:** [July 21, 2017, 12:28am UTC](https://community.dremio.com/t/aws-bucket-access/67/7 "2017-07-21T00:28:17Z")

</div>

Ok, I think i figured the problem out - I’m using Safari, and for some reason (bug?) the entire sources view in the UI is always blank at any point after the data source addition/dataset addition steps. Everything works in Firefox though - the Dataset/Sources view looks like it’s supposed to.

---

<div class="post-metadata">

**Author:** ![doron](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/doron/32/294_2.png) [@doron](https://community.dremio.com/u/doron)\
**Post date:** [July 21, 2017, 12:50am UTC](https://community.dremio.com/t/aws-bucket-access/67/8 "2017-07-21T00:50:44Z")

</div>

We actually do not support Safari at this time ([documented here](https://docs.dremio.com/deployment/system-requirements.html#browser)) and show a warning when you login, but not when you signup so sorry about that. We hope the next MacOS release’s Safari will be better supported.
