Architecture
This section describes the architecture for Atmos Cloud.
Axis Cloud Architecture from Atmos Agent and Atmos Air (Agentless) Perspective
The following diagram describes how connecting to applications from the Atmos Cloud looks like from the Atmos Agent and Atmos Air (Agentless) perspective.
Components
The following table describes each Axis Cloud architecture component, its role, and capabilities:
| Component | Description |
|---|---|
| Atmos Connector | • Supports TCP, UDP and ICMP. • Provides a connection to applications isolated in a private network. • Load balances traffic automatically when there are at least two Atmos Connector deployed in the same zone as they are added or removed, ensuring high availability. Important: The best practice is to (1) Place the connectors as close to the application as possible and (2) to have a minimum of 2 connectors per zone. • Performs DNS resolution for internal namespaces. After the Atmos Connector resolves the DNS, the connector sends the data to the right connector. |
| Atmos Portal | The front end of the web and application and services. Client requests and server responses pass through it. The Atmos portal provides connection and termination points that the clients use to access the applications delivered by Atmos Cloud. Note: This portal supports Web, RDP, Git SSH, UDP, DB (MSSQL), VNC applications. |
| Outbound Connection Service (Backend Service) | A service that sends the data to a specific connector. Once the Outbound Connection Service receives the connection. |
| Policy | Enforces security policy to traffic. |
Updated over 1 year ago