PLTs rely on secured connectivity with the PLTcloud cloud backend, used for:
Receiving firmware, test plans from PLTcloud
Executing webhooks during tests execution
Sending test reports to PLTcloud
The Ethernet port of the PLT should be connected to a network with (outbound) Internet access.
TCP (outbound) and UDP traffic should be allowed to these AWS API endpoints:
Amazon AWS IoT
Amazon AWS S3
Communication between the PLT and the AWS endpoints is encrypted with mutual TLS authentication.
TCP and UDP NTP traffic should be allowed for these NTP Time servers:
Specify a set of NTP servers in the DHCP server that can be accessed by the PLT, if access to the default NTP servers is not available.
The DNS server specified by the DHCP server should be able to resolve: