Forum Discussion
IoT Device connectivity to Azure via FTP
Hi All, I'm working with 30+ waterflow meters and the connectivity option is limited to FTP (I'm hoping SFTP is supported but haven't found a definitive yes/no in the Doc). The data to be passed is ...
Hi PBradz,
I am currently having the same problem in my company where we want to let weather stations ingest data via FTP. Currenlty the folder structure on the FTP server offers one folder per device. So my idea was to use:
your option 3)
Host a FTP server which provides FTP protocol support via a Azure Service / VM. The backing storage is monitored by some serverless logic on Azure and "microbatched"/parsed/forwared to the streaming (fast path) architecture.
My idea hear is to use IoT Hub also for "provisioning" the FTP server by having each weather station defined as "Iot device". The device agent (sideloaded with the ftp server) would react to new "device registrations" and create a new folder in the FTP server data store as well as provision the ACLs for the folder.
or
your option 4)
forget about a "real" ftp server but write a "facade FTP Bridge to Azure IoT Hub" which from the outside looks like a FTP server but has no storage built-in. But this would only allso for "write" scenarios not if some other user whats to use the FTP to read weather data from.
Did you choose one solution for your use-case? If yes, did you re-use opensource components for is?
Thanks in advance,
Dominic
I am currently having the same problem in my company where we want to let weather stations ingest data via FTP. Currenlty the folder structure on the FTP server offers one folder per device. So my idea was to use:
your option 3)
Host a FTP server which provides FTP protocol support via a Azure Service / VM. The backing storage is monitored by some serverless logic on Azure and "microbatched"/parsed/forwared to the streaming (fast path) architecture.
My idea hear is to use IoT Hub also for "provisioning" the FTP server by having each weather station defined as "Iot device". The device agent (sideloaded with the ftp server) would react to new "device registrations" and create a new folder in the FTP server data store as well as provision the ACLs for the folder.
or
your option 4)
forget about a "real" ftp server but write a "facade FTP Bridge to Azure IoT Hub" which from the outside looks like a FTP server but has no storage built-in. But this would only allso for "write" scenarios not if some other user whats to use the FTP to read weather data from.
Did you choose one solution for your use-case? If yes, did you re-use opensource components for is?
Thanks in advance,
Dominic
Dominic, apologies for delay in responding...I'll go back and check for correct info, however, as I remember it we ended up with a linux VM w/ IoT Edge installed; FTP went to Linux VM and Edge would transfer "new" files added to a Dir into IoT Hub which would direct as needed. For your case you could also have files copied to Azure Blob storage that is shared. I'll dig up my notes and add any details or corrections....