IBM Watson IoT Platform is continually making improvements to its service to enhance scalability, security and performance for our clients.   Most of these changes are completely transparent to our users.
However one upcoming change will modify the IP address of the messaging endpoints, i.e. the IP addresses that your devices and applications connect to at <orgId>.messaging.internetofthings.ibmcloud.com. It will not affect the addresses used by the endpoint at <orgId>.internetofthings.ibmcloud.com that are used mainly for administering the platform.

What is changing?

The host name used for your organization – <orgid>.messaging.internetofthings.ibmcloud.com – will not change, but the underlying DNS record will change to map it to three new IP addresses to provide higher availability.

We will be staging the change as follows:

  1. The new IP addresses will be made available first, with the DNS records still pointing to the old IP address
  2. The DNS records will be switched to point to the new addresses
  3. The old IP addresses will be withdrawn, but only when devices and applications have switched over to use new addresses

This change will not be deployed until April 15th 2019 at the earliest to give users time to prepare for this change.

Will this affect me?

This change affects public instances of the Watson IoT Platform service running in the IBM Cloud us-south, eu-gb and eu-de regions.  This includes Watson IoT SaaS offerings that include Watson IoT Platform.

We expect most users will not be affected by the change, and the switchover will happen automatically. Devices or applications that perform a DNS lookup when they connect to Watson IoT Platform will simply start using a new IP address the first time that they connect after the change has been made. 

There are two situations where the change will have an effect:

1. If you have had to configure a firewall rule to allow devices, gateways or applications to make outbound connections to the existing Watson IoT Platform endpoint. These rules are typically expressed using an IP address range, so you will need a rule that uses the three new IP ranges.

2. If you have devices, gateways or applications that connect using an explicit IP address, e.g. 169.45.2.20, they will need to be reconfigured to use the new addresses. We would recommend that devices, gateways and applications are configured to use a host name rather than an IP address.

What do I need to do if I am affected?

1. If you have firewall rules you will need to update them, as follows: 

i) Add rules to allow access to the new IP address ranges, leaving the old rules in place so that devices can continue to connect in the interim.  You can find the new IP address ranges here:https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/platform/reference/security/connect_devices_apps_gw.html.

ii) We will update the platform documentation when we have finally removed the old addresses, and you can remove the old firewall rules at that point. 

2. If you have devices that use explicit IP addresses, you should reconfigure them to use the host name <orgId>.messaging.internetofthings.ibmcloud.com. 

As always we welcome your feedback.

Join The Discussion

Your email address will not be published. Required fields are marked *