# Problems with connection to AWS Glue Catalog Iceberg table

**URL:** <https://community.dremio.com/t/problems-with-connection-to-aws-glue-catalog-iceberg-table/9535>\
**Category:** Dremio University\
**Created:** [August 11, 2022, 3:05pm UTC](https://community.dremio.com/t/problems-with-connection-to-aws-glue-catalog-iceberg-table/9535 "2022-08-11T15:05:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ritik](https://avatars.discourse-cdn.com/v4/letter/r/dec6dc/32.png) [@Ritik](https://community.dremio.com/u/Ritik)\
**Post date:** [August 11, 2022, 3:05pm UTC](https://community.dremio.com/t/problems-with-connection-to-aws-glue-catalog-iceberg-table/9535/1 "2022-08-11T15:05:32Z")

</div>

Hi,

I have gone through the steps here:

> **[Getting Started with Apache Iceberg Using AWS Glue and Dremio](https://www.dremio.com/resources/tutorials/getting-started-with-apache-iceberg-using-aws-glue-and-dremio/)**
>
> Adding the Dremio and Iceberg Advantage to Data Lakes Accept the terms on the next page, and when the “Continue to Configuration” button in the upper right activates by turning orange (which can take a minute or two), click it. Then, on the next...

And have managed to create a physical dataset, with everything, including the glue job working fine. In the relevant S3 bucket, I can also see the data and metadata files. However on trying to query that dataset, I am getting this error:

dataset at [/dataset/###.db.###] not found.

Can anyone help here?

---

<div class="post-metadata">

**Author:** ![hope](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/hope/32/4068_2.png) [@hope](https://community.dremio.com/u/hope)\
**Post date:** [September 9, 2022, 4:35pm UTC](https://community.dremio.com/t/problems-with-connection-to-aws-glue-catalog-iceberg-table/9535/2 "2022-09-09T16:35:55Z")

</div>

Can you check that you have set the connection property: `hive.metastore.warehouse.dir` to your s3 bucket location

More information here: [Dremio](https://docs.dremio.com/software/sql-reference/sql-commands/apache-iceberg-tables/apache-iceberg-create/#locations-in-which-iceberg-tables-are-created)

---

<div class="post-metadata">

**Author:** ![Ritik](https://avatars.discourse-cdn.com/v4/letter/r/dec6dc/32.png) [@Ritik](https://community.dremio.com/u/Ritik)\
**Post date:** [September 12, 2022, 6:49am UTC](https://community.dremio.com/t/problems-with-connection-to-aws-glue-catalog-iceberg-table/9535/3 "2022-09-12T06:49:18Z")

</div>

Hi, thanks for your reply.

I have done it now, by pointing the data source in Dremio to the S3 bucket location where the AWS Glue job created the iceberg table with the data. However, I still get the same error:

dataset at [/dataset/###.db.###] not found.

My Dremio version is 21.3. Also, the AWS instance on which I am running Dremio is in Ireland, not in N. Virginia. Could these have anything to do with it?

---

<div class="post-metadata">

**Author:** ![hope](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/hope/32/4068_2.png) [@hope](https://community.dremio.com/u/hope)\
**Post date:** [September 12, 2022, 4:24pm UTC](https://community.dremio.com/t/problems-with-connection-to-aws-glue-catalog-iceberg-table/9535/4 "2022-09-12T16:24:27Z")

</div>

Your VPC and s3 bucket location need to be in the same aws region. As long as all of your resources are in Ireland, you should be fine.

---

<div class="post-metadata">

**Author:** ![Ritik](https://avatars.discourse-cdn.com/v4/letter/r/dec6dc/32.png) [@Ritik](https://community.dremio.com/u/Ritik)\
**Post date:** [September 13, 2022, 6:38am UTC](https://community.dremio.com/t/problems-with-connection-to-aws-glue-catalog-iceberg-table/9535/5 "2022-09-13T06:38:18Z")

</div>

Ah. So my Dremio instance is deployed in Ireland, but my S3 bucket and Glue job are in Virginia (I did it that way since the Iceberg connector for the Glue job works only in Virginia).

However, the issue just seems to be with iceberg tables. I created other glue databases in Virginia pointing to normal flat files in S3 and they seem to work fine on Dremio.

Could the version have something to do with it? Or is there a configuration which I may have missed?
