> For the complete documentation index, see [llms.txt](https://waf-doc.inext.checkpoint.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waf-doc.inext.checkpoint.com/troubleshooting/waf-as-a-service/how-to-extend-connection-timeout-to-upstream.md).

# How To: Extend Connection Timeout to Upstream

Goal: Extend the default timeout configuration from the default 60 seconds for assets that need a longer timeout connection time.

### Overview:

In CloudGuard WAF as a Service, the default connection timeout for both NGINX and CloudFront is set to 60 seconds. To extend the timeout for specific assets, adjust the settings in the asset's advanced options.

{% hint style="info" %}
Adjusting the NGINX timeout configuration will automatically update CloudFront's settings
{% endhint %}

### What To Do?

To configure the extended timeout for a specific asset, follow these steps:

1. Log in to the Infinity Portal.
2. Open the WAF application from the application menu.
3. Navigate to the **Assets** page under the **Policy** tab.
4. Select the desired asset.
5. Click on **Advanced...** proxy field to access the extended timeout configuration.
6. Click on **Advanced Settings**.
7. **Add the following fields** with the desired timeout configuration needed:

| Key                | Value                      |
| ------------------ | -------------------------- |
| Read Timeout       | Numeric Number (up to 180) |
| Proxy Send Timeout | Numeric Number (up to 180) |
| Keep Alive Timeout | Numeric Number (up to 180) |

8. Click **OK**
9. Click **Enforce**.

{% hint style="warning" %}
Extended Timeout configuration is supported up to 180 seconds. \
For longer timeouts, please contact Check Point Support.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://waf-doc.inext.checkpoint.com/troubleshooting/waf-as-a-service/how-to-extend-connection-timeout-to-upstream.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.