If you are manufacturing IoT devices that will ultimately be used in IT environments that you do not control, this can cause serious headaches. Standard ports for things like HTTPS traffic (port 443) are left open but others that are used for less common protocols, such as MQTT (port 8883) may be intentionally blocked. This is done as a security measure to limit the attack surface for possible cyber attacks.

AWS IoT Core complies with these standards as much as possible (see here), but as we have learned from our customers, there are scenarios where it makes sense to deviate from them.Ĭorporate firewalls and even some home routers often restrict inbound and outbound traffic to be transmitted over a small range of TCP ports. internet traffic) and 8883 is the registered port for MQTT over TLS. A quick search of their database shows that port 443 is the registered port for HTTP over TLS (i.e. While this is not a canonical list, these standards are widely adopted, especially for more popular protocols. To solve this problem, the Internet Assigned Numbers Authority (IANA) maintains a mapping of TCP and UDP port numbers to various messaging protocols that have registered with the organization. This immediately raises the question of which port number to use to ensure that your application can communicate with other 3rd party applications. TCP connections are typically associated with a combination of IP address and port number. So what’s the big deal? Read on to learn more about how this feature makes it easier to connect your devices or skip to the final section to learn how you can start taking advantage of it today. Previously this combination of protocol and authentication mechanism was only supported on port 8883. The AWS IoT Core service now allows you to connect devices using MQTT with TLS client authentication on port 443.

Amzn wplay tcp