> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/home-cloud-user-manual/appendix/firewall-rule/firewall-rule-1.md).

# Japan Site

cloud-jp.engenius.ai

Below are the firewall rules that devices are needed to access EnGenius Cloud.

<table data-header-hidden data-full-width="true"><thead><tr><th>
Cloud Devices</th><th width="244">
 Cloud Services</th><th>Source IP</th><th>Destination IP</th><th width="462">FQDN</th><th width="147">Ports</th><th>Protocol (TCP/UDP/ICMP..)</th><th>Direction (Inbound / outbound / bi-direction)</th></tr></thead><tbody><tr><td>
<strong>Cloud Devices</strong></td><td>
 <strong>Cloud Services</strong></td><td><strong>Source IP</strong></td><td><strong>Destination IP</strong></td><td><strong>FQDN</strong></td><td><strong>Ports</strong></td><td><strong>Protocol (TCP/UDP/ICMP..)</strong></td><td><strong>Direction (Inbound / outbound / bi-direction)</strong></td></tr><tr><td>AP, SW, GW, PDU, CAM, Ensky,ROAM</td><td>Periodical Cloud communication, Firmware Upgrade, Real-Time Meter</td><td>Your Networks</td><td>any</td><td><p>swallow-jp.production.engenius.ai</p><p></p><p>services-jp.engenius.ai</p><p>               </p><p>dolphin-jp-*.production.engenius.ai</p><p></p><p>device-jp.production.engenius.ai</p><p>chicken-jp.production.engenius.ai</p></td><td>443</td><td>TCP</td><td>Outbound</td></tr><tr><td>AP, SW, GW, PDU, CAM, Ensky,ROAM</td><td>Persistent Cloud communication</td><td>Your Networks</td><td>3.114.71.151</td><td>raccoon-jp.production.engenius.ai</td><td>80</td><td>TCP</td><td>Outbound</td></tr><tr><td>AP</td><td>Cloud Radius</td><td>Your Networks</td><td>35.79.186.153</td><td>NA</td><td>1812/1813</td><td>TCP &#x26; UDP</td><td>Outbound</td></tr><tr><td>AP, SW, GW, PDU, Ensky,ROAM</td><td>NTP time synchronization</td><td>Your Networks</td><td>any</td><td>NA</td><td>123</td><td>UDP</td><td>Outbound</td></tr><tr><td>AP, SW, GW, PDU, Ensky, EPC,ROAM</td><td>SSH Tunnel for local UI remote access</td><td>Your Networks</td><td>35.73.31.229</td><td>sshserver-jp-0.production.engenius.ai</td><td>22</td><td>TCP</td><td>Outbound</td></tr><tr><td>AP, GW</td><td>Splash Page</td><td>Your Networks</td><td>any</td><td><p>s3.ap-northeast-1.amazonaws.com</p><p>falcon-jp.production.engenius.ai</p></td><td>80/443</td><td>TCP</td><td>Outbound</td></tr><tr><td>CAM</td><td>Cloud AI Analytics</td><td>Your Networks</td><td>any</td><td>owl-jp.production.engenius.ai</td><td>443</td><td>TCP</td><td>Outbound</td></tr><tr><td>CAM</td><td>WebRTC STUN &#x26; TURN communication</td><td>Your Networks</td><td>any</td><td>beaver-jp-*.production.engenius.ai</td><td>3478</td><td>UDP</td><td>Outbound</td></tr><tr><td>CAM</td><td>WebRTC P2P Streaming</td><td>Your Networks</td><td>any</td><td>NA</td><td>1024 to 65535</td><td>UDP</td><td>Outbound</td></tr></tbody></table>

Below are the firewall rules needed to access the EnGenius Cloud API

| Source Domain                    | Destination Domain               | Port | Purpose                                                   |
| -------------------------------- | -------------------------------- | ---- | --------------------------------------------------------- |
| Your Server                      | falcon-jp.production.engenius.ai | 443  | Sending API requests to retrieve data from EnGenius Cloud |
| falcon-jp.production.engenius.ai | Your Server                      | 443  | Receiving responses from EnGenius Cloud API               |
|                                  |                                  |      |                                                           |


---

# 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://doc.engenius.ai/home-cloud-user-manual/appendix/firewall-rule/firewall-rule-1.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.