PLT Connectivity

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

Network Requirements

The Ethernet port of the PLT should be connected to a network with (outbound) Internet access.

Firewall Settings

TCP (outbound) and UDP traffic should be allowed to these AWS API endpoints:

PLTcloud

  • *.pltcloud.com

Amazon AWS IoT

  • a347l7e88enrtv-ats.iot.us-west-2.amazonaws.com

Amazon AWS S3

  • s3.us-west-2.amazonaws.com

  • plt-asset-production.s3.us-west-2.amazonaws.com

Communication between the PLT and the AWS endpoints is encrypted with mutual TLS authentication.

References

NTP

TCP and UDP NTP traffic should be allowed for these NTP Time servers:

  • 0.pool.ntp.org

  • 1.pool.ntp.org

  • 2.pool.ntp.org

  • 3.pool.ntp.org

  • 0.cn.pool.ntp.org

  • 1.cn.pool.ntp.org

  • 2.cn.pool.ntp.org

  • 3.cn.pool.ntp.org

Tip

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.

DNS

The DNS server specified by the DHCP server should be able to resolve:

  • *.pltcloud.com

  • *.amazonaws.com

  • *.ntp.org

See also