Atmos Agent Device Prerequisites
The Atmos Agent allows you to seamlessly navigate traffic through Axis Security. The Atmos Agent takes all traffic to applications configured in the Management Console, and routes it through the Axis Cloud.
The update frequency is determined by the organization's policy.
End User Access (Firewall Rules)
Agent Access: agent-geo.axisapps.io (udp 443)
- 3.218.242.122
- 52.202.240.174
- 13.239.90.116
- 3.24.60.39
- 3.8.107.216
- 13.41.40.26
- 18.162.34.22
- 43.198.8.41
- 192.9.245.57
- 129.159.134.191
- 141.148.173.4
- 104.210.157.15
- 52.173.247.116
- 3.0.105.216
- 52.77.86.133
- 15.207.5.150
- 43.204.206.75
- 54.207.51.119
- 54.94.160.154
- 13.246.143.205
- 13.245.59.57
TLS Fallback for agent access: agent-geo-gw.axisapps.io (tcp+udp 443)
In case the Atmos agent cannot establish a connection using udp, it will fallback to tls using the "agent-geo-gw.axisapps.io" addresses below. It may be required to pause and restart the agent in case the tls fallback does not apply automatically.
- 3.33.219.65
- 15.197.208.139
- 52.173.247.116
- 104.210.157.15
- 4.204.211.61
Agent Authentication: *.axissecurity.com
- 52.223.54.170 (TCP:443)
- 35.71.180.65 (TCP:443)
Windows
Windows 10, windows 8.1, windows 7 and above.
2 GB RAM
macOS
mac OS Catalina and above
2GB RAM
iOS
iOS 14.1 and above.
Identity and Authentication
The Atmos Agent authenticates through the default Identity Provider (IdP) that is configured in the tenant. This means that all of the network range applications authenticate through the default IdP.
Users logged in to the Atmos Agent are automatically logged in to the User Portal and web applications. The applications log the user in with the same authentication as the Atmos Agent.
Updated about 1 month ago