TLS encryption is used on the MQTT protocol, but no other specific security features are used. A custom certificate handling system has been built for short-lived and device-specific IoT device certificates, so a custom security model has been built. AWS IoT Core is used for the core only, and events are streamed to Kafka where they are further processed. Whether AWS IoT Core or another solution is used, it would not make that big of a difference because it just throws the events to the Kafka broker. There are no lacking features because the pure core is used and the rest is managed in-house. Discussions have been had with the AWS team itself. If AWS IoT Core is used just for basic functionality, it is very expensive. Price calculations were done together with AWS, the core product team, and the product manager for AWS IoT Core. They made an adaptation, and a few quarters ago, they introduced a feature that allows paying a decent price for just using the basic things that are needed. The price setting point of view is satisfactory. Building it ourselves was looked at because it was too expensive. Some open source tooling was considered because the key thing about having a good solution is that the open source tools that could be found were more than enough. The key thing is, of course, to make it resilient.
One of the areas where AWS IoT Core lacks is in terms of the fact that it does not serve as a good visualization tool like Grafana or Kibana, making it an area where improvements are required. It is quite ugly to see the visualization part offered by AWS IoT Core, so the data pipeline did upset some of the clients who used it. Visualization is a very important key feature, in my opinion, because most people would like to see results from graphs, etc., for which visualization, in my opinion, is a key feature. The tool wasn't very easy to configure.
Find out in this report how the two IoT Connectivity solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
TLS encryption is used on the MQTT protocol, but no other specific security features are used. A custom certificate handling system has been built for short-lived and device-specific IoT device certificates, so a custom security model has been built. AWS IoT Core is used for the core only, and events are streamed to Kafka where they are further processed. Whether AWS IoT Core or another solution is used, it would not make that big of a difference because it just throws the events to the Kafka broker. There are no lacking features because the pure core is used and the rest is managed in-house. Discussions have been had with the AWS team itself. If AWS IoT Core is used just for basic functionality, it is very expensive. Price calculations were done together with AWS, the core product team, and the product manager for AWS IoT Core. They made an adaptation, and a few quarters ago, they introduced a feature that allows paying a decent price for just using the basic things that are needed. The price setting point of view is satisfactory. Building it ourselves was looked at because it was too expensive. Some open source tooling was considered because the key thing about having a good solution is that the open source tools that could be found were more than enough. The key thing is, of course, to make it resilient.
One of the areas where AWS IoT Core lacks is in terms of the fact that it does not serve as a good visualization tool like Grafana or Kibana, making it an area where improvements are required. It is quite ugly to see the visualization part offered by AWS IoT Core, so the data pipeline did upset some of the clients who used it. Visualization is a very important key feature, in my opinion, because most people would like to see results from graphs, etc., for which visualization, in my opinion, is a key feature. The tool wasn't very easy to configure.