> For the complete documentation index, see [llms.txt](https://docs.higiocloud.vn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.higiocloud.vn/network/3.-load-balancer/open-firewall-rule-to-public-service-to-internet.md).
# Open Firewall Rule To Public Service To Internet
## **Overview**
The default Edge gateway firewall rule on Tenant is set to **Deny all**. We must create firewall rules for traffic to virtual services from the internet. [More detail on edge way firewall.](/network/1.-working-with-network/using-edge-gateway-firewall.md)
## **Procedure**
{% tabs %}
{% tab title="I. Create IP set" %}
**Step 1:** Log in to the HI GIO PORTAL as an Organization Administrator and Navigate to
**Step 2: Networking > Edge Gateway > Security > IP Sets.**
Press **NEW** to define the **IP Set for VIPs.**
* ***Name:** type IP Set name (example VIP-Web)*
* ***IP Address:** type IP Address or IP Range (this IP for VIP that was created before).*
{% endtab %}
{% tab title="II. Create an Edge Firewall Rule" %}
**Step 1:** Log in to the HI GIO PORTAL as an Organization Administrator and Navigate to
**Networking > Edge Gateway > Services > Firewall.**
**Step 2:** Press **EDIT RULES** to add NEW RULE for VIPs**.**
* ***Name:** type Rule name (example Allow\_VSWeb)*
* ***Applications:** choose your application types (example: HTTP and HTTPS)*
* ***Source:** Any (for internet users)*
* ***Destination:** Select **IP Set** configured before (example VS\_192.168.2.10)*
* ***Action:** Allow*
**Step 3:** Click **Save** to complete EDIT RULES
{% hint style="warning" %}
In case we’re using a distributed firewall in our environment. we should create and distribute firewall rules for virtual service and pool
{% endhint %}
{% endtab %}
{% endtabs %}
---
# 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://docs.higiocloud.vn/network/3.-load-balancer/open-firewall-rule-to-public-service-to-internet.md?ask=&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.
