locked
Migration of IOT systems from custom written cloud service to IOT hub RRS feed

  • General discussion

  • We have a custom written ‘collector’ which is simply an asp.net MVC application with an endpoint that accepts JSON encoded data and stores it in a table storage account.

    We are investigating a migration to IOT hub and other related technologies. One issue that recently came up is our use of reserved IP addresses with our asp.net application running in a cloud service (classic).

    Do we have any ability to maintain that endpoint if we were to begin the process of migrating our implementation over to using IOT hubs? Or, would we need to maintain a cloud service proxy (and thus the known reserved IP address) and then manage traffic from devices through that cloud service to the IOT hub, similar to a field gateway, but in this case as a service running in Azure.

    I did find one blurb about IP addresses for IOT Hub here: https://azure.microsoft.com/en-us/documentation/articles/iot-hub-devguide-messaging/ That suggests that the IP address will remain but could change due to movement of the hub internally due to scaling issues. We have customers that are poking holes in their firewall based on the IP address and would need to somehow maintain that if we were to migrate to IOT Hub.

    Thoughts?

    Tuesday, November 8, 2016 4:20 PM