# Dremio Cloud : Query timeout

**URL:** https://community.dremio.com/t/dremio-cloud-query-timeout/10607
**Category:** Dremio Cloud
**Created:** [May 10, 2023, 7:39pm UTC](https://community.dremio.com/t/dremio-cloud-query-timeout/10607 "2023-05-10T19:39:14Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![cclairmont](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/cclairmont/32/4730_2.png) [@cclairmont](https://community.dremio.com/u/cclairmont)
#### Post date: [May 10, 2023, 7:39pm UTC](https://community.dremio.com/t/dremio-cloud-query-timeout/10607/1 "2023-05-10T19:39:14Z")

</div>

Hi All,

It’s not my first attemp deploying Dremio Cloud. But we faced a very strange behavior of Dremio Cloud now. We are able to deploy Dremio Cloud. The engine instance start in the AWS env… And finally we won’t get any result for any query !

We followed the documentation as detailed here  
Getting Started with Dremio Sonar : [https://docs.dremio.com/cloud/getting-started/](https://docs.dremio.com/cloud/getting-started/)  
We have a special attention when we created

- Security Group - [https://docs.dremio.com/cloud/appendix/aws-resources/create-security-group/](https://docs.dremio.com/cloud/appendix/aws-resources/create-security-group/)
- VPC and Subnets - [https://docs.dremio.com/cloud/appendix/aws-resources/create-vpc-and-subnets/](https://docs.dremio.com/cloud/appendix/aws-resources/create-vpc-and-subnets/)

The cloud formation application is **OK**

 ![image(2)](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/5/5d92604676e9300c9291f5ed8d3787e55593d574.png)

Engines are launched in VPC with a private subnet.

 ![image(3)](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/2/208ec917b465515adf93543653ce2e49a1b9bccd.png)

But we never get results for a query execution

 ![image(4)](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/1/19569e2687e0c3ce39ca3ebdbddbf867ca1987ab.png)

The query keep in a ““continuous execution without obtain the result””

 ![image](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/b/b1ca33d2977377ca1c2ad8289bbe3e94ff77d309.png)

I spend some time on the community forum, and support knowledge base. We do not understand the missing element…

The cloudformation creates all resources needed by Dremio Cloud. Isn’t it? Why something is missing? All network rules are defined in the cloudformtion…

If you have any suggestion…

Kind regards

---

<div class="post-metadata">

### Author: ![cindy.la](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/cindy.la/32/6730_2.png) [@cindy.la](https://community.dremio.com/u/cindy.la)
#### Post date: [May 11, 2023, 9:30pm UTC](https://community.dremio.com/t/dremio-cloud-query-timeout/10607/2 "2023-05-11T21:30:42Z")

</div>

Hi @cclairmont ,

Thanks for sharing the steps you have taken. Our CloudFormation template only creates the VPCEndpoints, Security groups, and IAM roles needed. The additional network configurations need to be created by you. Just to confirm, have you also created a NAT gateway and a route table for those private subnets?

[https://docs.dremio.com/cloud/appendix/aws-resources/create-route-table/](https://docs.dremio.com/cloud/appendix/aws-resources/create-route-table/)  
[https://docs.dremio.com/cloud/appendix/aws-resources/create-nat-gateway/](https://docs.dremio.com/cloud/appendix/aws-resources/create-nat-gateway/)

Additionally, would you mind sharing your Organization ID with me through a private message?

---

<div class="post-metadata">

### Author: ![cclairmont](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/cclairmont/32/4730_2.png) [@cclairmont](https://community.dremio.com/u/cclairmont)
#### Post date: [May 16, 2023, 12:54pm UTC](https://community.dremio.com/t/dremio-cloud-query-timeout/10607/3 "2023-05-16T12:54:42Z")

</div>

Hi @cindy.la ,

Thanks a lot for you links 🙂. They were very helpful. Now we have a better understanding how we could connect Dremio control plane and Customer Data plane with a public sub-network or a private sub-network.

Kind regards

---

<div class="post-metadata">

### Author: ![cclairmont](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/cclairmont/32/4730_2.png) [@cclairmont](https://community.dremio.com/u/cclairmont)
#### Post date: [June 8, 2023, 8:46pm UTC](https://community.dremio.com/t/dremio-cloud-query-timeout/10607/4 "2023-06-08T20:46:52Z")

</div>

Hi all,

One more question please.

In the documentation of Dremio Cloud

# Creating a NAT Gateway

> **[Creating a NAT Gateway | Dremio Documentation](https://docs.dremio.com/cloud/help-support/appendix/aws-resources/create-nat-gateway/)**
>
> You may need to create an NAT gateway if it is not already configured for your VPC setup. See the steps below for creating this resource using the VPC Dashboard in the AWS Management Console.

It’s indicated that the NAT Gateway is created on the private subnet. With this setup Dremio Cloud does not work. In fact, on a vm in the private subnet, with this command

```auto
curl -v https://gw.dremio.cloud

```

we couldn’t reach dremio cloud.

Finally as many documentation on the AWS NAT Gateway explain, to allow a VM on a private subnet reach internet, it’s a standard to route trafic through a Nat Gateway in a public subnet.

And in fact, Dremio Cloud works well with a Nat Gateway on a public subnet.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/a/adbebc11d047e9c50fde5a396eb0072f637d836b.png)

Could someone confirm please ?

Cheers

---

<div class="post-metadata">

### Author: ![cindy.la](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/cindy.la/32/6730_2.png) [@cindy.la](https://community.dremio.com/u/cindy.la)
#### Post date: [June 8, 2023, 8:51pm UTC](https://community.dremio.com/t/dremio-cloud-query-timeout/10607/5 "2023-06-08T20:51:46Z")

</div>

Hi @cclairmont ,

You are correct, the NAT gateway should be created on the public subnet.

It looks like that documentation is incorrect. We’ll get this fixed on our end!

Cindy
