Suggestion: Some technical info on deployment

[Linwood]

I wondered if this might be a good choice for some clients, and my immediate reaction was how can one change from an internally deployed, firewalled zabbix to one that is external, especially in clients with pretty heavy security requirements.

I started reading the web page, the faq, the blog.... there's virtually zero information on architecture, and how all that would work. At lest readily at hand.

So as a suggestion: Provide some. Or if it's there, make it easier to find.

Also, there's some contradictions when it supports full functionality, but not SNMP traps -- we use SNMP traps pretty heavily, and external checks VERY heavily.

[exkg]

Hi Linwood,

We always can use Zabbix (local / on-premisses) Proxies.
My understanding is that (firewall limitations & SNMP Traps) could be managed by local Zabbix Proxies.

[]x,
Luciano

[DmitryL]

Hello,
You are right. Currently, there are no detailed architectural/network explanations, but the most important thing to understand is that it's Zabbix in the cloud.
In the configuration of each node in CLOUD UI, you can set up firewall rules to list who will have access to the Server and/or front, API
Port-wise, it's just like in on-prem Zabbix installation. 10050 for passive checks, 10051 for active, etc.
Encryption is also supported.

SNMP Traps are not available in the Cloud server node ( because of security reasons ), but it is fully supported to deploy Proxy on-prem or in any cloud provider and connect it to your Zabbix clode node. In that case, the Proxy can process all SNMP Traps.
In the future, it will be possible to deploy Proxies within the Zabbix Cloud as well.

[bera]

Hello
I am also new to Zabbix and would be interesting when the Cloud Proxy is available

BR Bernhard