> For the complete documentation index, see [llms.txt](https://delegates.iotex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://delegates.iotex.io/get-started/advanced/edge-proxy.md).

# Edge Proxy

### Run your node behind an edge proxy like Envoy

[Envoy](https://www.envoyproxy.io/) combined with [rate limit](https://github.com/lyft/ratelimit) provides request rate limiting on HTTP/HTTP2 and connection limits on all network traffic. Putting your IoTeX node behind an Envoy proxy gives you another layer of protection against attackers, especially if you intend to use your node and an IoTeX API gateway.&#x20;

Additionally, since the IoTeX node API utilizes GRPC, if you want to be an IoTeX *service node* and serve API requests to in-browser applications, you will need Envoy's [grpc-web](https://github.com/grpc/grpc-web) filter enabled for this functionality.

Below you find an example configuration file for Envoy where we set the max connection numbers to 50 and enabled the rate limit for HTTP requests (find the respective rate limit configuration file below):

{% embed url="<https://gist.github.com/yutongp/c61292bf5c9c6e3058df96989365cb0c>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://delegates.iotex.io/get-started/advanced/edge-proxy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
