Guidance for Connected Vehicles on AWS
Use real-time connected vehicle updates to transform vehicle support and roadside assistance
Overview
This Guidance helps you modernize your broker to gather, collect, and distribute data with your connected vehicle workloads using AWS IoT Core and Message Queuing Telemetry Transport (MQTT) 5. Most connected vehicle workloads require the vehicle to be connected to a cellular connection; otherwise, the vehicle would lack connectivity to receive commands from the cloud. With AWS IoT Core and the MQTT protocol, original equipment manufacturers (OEMs) can scale connected vehicles to meet demands during peak usage and right-size their workloads.
This Guidance is composed of five architecture diagrams that address the following using Internet of Things (IoT) services: modernizing connected vehicle workloads, gathering and processing vehicle data, setting up operational certificate lifecycles, encryption and monitoring security, and connecting a companion application.
How it works
Modernized Connected Vehicles
This architecture diagram shows you how to modernize your connected vehicle workloads.

Data Gathering and Processing
This architecture diagram shows you how to gather, process, analyze, and act on connected vehicle data.

Operational Certificate Lifecycle
This architecture diagram shows an operational certificate lifecycle.

Encryption and Monitoring Security
This architecture diagram shows you how to secure connected vehicles through encryption and monitoring.

Companion Application
This architecture diagram shows you how to build a connected vehicle companion application.

Well-Architected Pillars
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
Related Content
Disclaimer
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages