{"id":2851,"date":"2018-12-01T22:21:32","date_gmt":"2018-12-01T16:51:32","guid":{"rendered":"http:\/\/navveenbalani.dev\/?p=2851"},"modified":"2019-12-18T22:34:00","modified_gmt":"2019-12-18T17:04:00","slug":"connected-car-solution-using-amazon-iot","status":"publish","type":"post","link":"https:\/\/navveenbalani.dev\/index.php\/articles\/connected-car-solution-using-amazon-iot\/","title":{"rendered":"Connected Car Solution using Amazon IoT"},"content":{"rendered":"\n

This article is part of IoT Architecture Series – https:\/\/navveenbalani.dev\/index.php\/articles\/internet-of-things-architecture-components-and-stack-view\/<\/a><\/p>\n\n\n\n

The strategy for building the IoT application on AWS is pretty much the same as discussed earlier for IBM<\/a> and Microsoft IoT<\/a> offerings. You build IoT applications by composing the relevant AWS services and AWS IoT services. For instance, you could replace the Microsoft Azure services with services being offered by AWS for the connected car solution that we went through earlier. At the end of this article, we have provided a comparison chart of services offered by various IoT cloud platforms.<\/p>\n\n\n\n

To summarize for the connected car solution, we went through three phases of implementation \u2013 real-time flow, offline\/batch phase where we developed machine learning models and finally the third phase where we modified our real-time flow to integrate the machine learning model. We would not go over the entire steps in detail but summarize the integration below. Kindly refer to Microsoft IoT implementation article<\/a> for details on how we arrived at the final (the third) step of the solution. <\/p>\n\n\n\n

Given below is the final step of the connected car solution using Amazon IoT. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

 Hardware and Connectivity<\/a><\/h4>\n\n\n\n

For connecting the hardware device to the\nAmazon IoT platform, we use AWS IoT Device SDKs. We use MQTT protocol over TLS\nfor secure communication. We went through the details earlier in Device\nSecurity, Authorization and Authentication section.   We need to register the device in the registry, create certificates, assign policies\nand use the relevant SDKs. The following are the high-level steps<\/p>\n\n\n\n

  1. Create Thing in Device Registry<\/li>
  2. Create Certificates and\nPolicies for secured communication<\/li>
  3. Attach Certificate to Thing<\/li>
  4. Generate SDKs<\/li><\/ol>\n\n\n\n

    For the above steps, you can use AWS IoT\nWeb console or AWS CLI (command line interface) commands. As part of device\nprovision step, manufacturers would typically use AWS CLI as that would provide\nan ability to automate the process and use their own private key to generate certificates using AWS command.<\/p>\n\n\n\n

    We use the web console and list down the\nAWS CLI specific commands for reference.<\/p>\n\n\n\n