Is this a reasonable piece of hardware to use for this? Seems a bit overpowered and expensive for no more than what it is doing.
I think the answer depends a lot on scale; how many of these will you deploy? By your own admission, it saved you a lot of time and effort compared to the Pi. The answer also depends on how robust this needs to be (temperature, dust ingress, water ingress, vibration, shock and so forth); this device might pay for itself if it's more robust than cheaper alternatives.
Would this be considered a gateway and my sensors/inputs be considered things?
I would say that your inputs/machines have more need to be Things in AWS IoT if you need granularity for security and/or if each machine would be managed individually (configuration, command/control, software updates etc). If all you are doing is ingesting data, there's probably not a strong case to model each machine as an individual Thing.
In our use case (many machines with a few inputs) what kind of hardware solution would you recommend for collecting the data and sending the MQTT packet to AWS with?
I recommend you search the AWS Partner Device Catalog: https://devices.amazonaws.com/search?page=1 . I note that Opto 22 have a device in the catalog: https://devices.amazonaws.com/detail/a3G0h0000076iDGEAY/groov-EPIC . You will find many possible alternatives. Please also consider to reach out to your nearest AWS office to dive deeper into your requirements.
Relevant content
- asked a year ago
- asked a year ago
- asked 7 months ago
- Accepted Answerasked 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 3 months ago
Thanks Greg. I really appreciate the time and guidance. It can be pretty daunting when first starting.
No contract required.