Verkada devices need to communicate with Verkada Command in AWS GovCloud via their local network. In most cases, minimal updates to your network settings are needed. Additional configuration may be required for complex or highly secure networks.

Verkada devices are incompatible with local area networks (LANs) that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for your Verkada devices to communicate with Verkada Command.

Verkada devices must be assigned an IPv4 address to communicate on the LAN and to Verkada Command through the internet. By default, all Verkada devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations.

If you require your device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device's label). You can also set up static IP addresses in Command for cameras.

Verkada devices use the Domain Name System (DNS) server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Verkada device where the DNS server is on the network, and the device communicates using UDP port 53.

Most Verkada devices are powered through Power over Ethernet (PoE). You can use the product datasheets to figure out the power requirements for your Verkada devices.

These are the most common power requirements:

Verkada cameras require access to many endpoints to ensure they can communicate with Command and all features will be accessible.

Need more help? Contact Verkada Support.