Overview
The Connected Mobility Solution (CMS) on AWS helps you establish the foundational components of a well-architected connected vehicle program. Our dedicated Automotive Cloud Developer Portal (ACDP) facilitates and oversees this AWS Solution’s deployment, providing developers with a seamless experience. This portal is meticulously designed to expedite customer initiatives by centralizing and streamlining the visibility, collaboration, and implementation of connected vehicle assets.
Benefits
Establish a centralized location for engineers and developers to collaborate, curate, deploy, and operate connected vehicle assets while using AWS Cloud infrastructure and services. Developers and engineers can focus on delivering value through cloud infrastructure, re-usable code assets, and easily accessible documentation and metrics.
Onboard vehicles into AWS IoT Core and ingest telemetry data emitted to topics. Use well-architected components to manage certificates, vehicle onboarding, and lifecycle events to stay connected and communicate with AWS IoT Core.
Standardize, route, and store data coming from vehicles using AWS IoT Core, AWS Glue, and Amazon Simple Storage Service (Amazon S3), then use Amazon Athena, Amazon Managed Grafana, and other AWS analytics tools to serve data to value-added services and applications.
Set alerts and notifications for use case-driven thresholds and anomalies. Query and analyze alerts based on vehicle data ingested by the solution in near real-time.
Technical details
You can automatically deploy this architecture using the implementation guide.
Step 1
The ACDP is the centralized hub for deploying subsequent CMS on AWS modules. The ACDP uses the CMS Backstage module as its presentation layer to provide a configurable developer hub for managing and monitoring the deployment of CMS on AWS modules.
Step 2
The CMS Authentication module allows for the authentication and authorization of users and services throughout the solution. The module provides a default identity provider option through Amazon Cognito.
Step 3
The CMS Vehicle Provisioning module provides a means to onboard and register vehicles with AWS IoT Core. Vehicle provisioning uses the method of fleet provisioning by claim.
Step 4
A centralized Amazon Simple Storage Service (Amazon S3) bucket deployed within the CMS Connect and Store module serves as the repository for all CMS on AWS data. Centralized data storage allows for vehicle telemetry data queries and alerts based on data insertion and thresholds.
Step 5
CMS on AWS users can interact with vehicle telemetry data stored in the CMS on AWS data lake through the CMS API module. The API provided by the module uses AWS AppSync and AWS Lambda functions to build and execute Amazon Athena queries on vehicle data stored in Amazon S3.
Step 6
The CMS Alerts module allows users to receive notifications invoked by data stored in the CMS on AWS data lake. CMS modules can publish to Amazon Simple Notification Service (Amazon SNS) topics defined by the CMS Alerts module by using an API that AWS AppSync provides. Users can subscribe to these same topics to receive email notifications.
Step 7
The CMS EV Battery Health module provides a dashboard through Amazon Managed Grafana which is authenticated by AWS IAM Identity Center. From the dashboard, users can visualize data and set up alerts based on configurable data thresholds.
Step 8
The CMS Vehicle Simulator module provides a user interface (UI) and backend engine for creating, operating, and monitoring simulations of vehicle data emissions.
Step 1
The ACDP is the centralized hub for deploying subsequent CMS on AWS modules. The ACDP uses the CMS Backstage module as its presentation layer to provide a configurable developer hub for managing and monitoring the deployment of CMS on AWS modules.
Step 2
The CMS Authentication module allows for the authentication and authorization of users and services throughout the solution. The module provides a default identity provider option through Amazon Cognito.
Step 3
The CMS Vehicle Provisioning module provides a means to onboard and register vehicles with AWS IoT Core. Vehicle provisioning uses the method of fleet provisioning by claim.
Step 4
A centralized Amazon Simple Storage Service (Amazon S3) bucket deployed within the CMS Connect and Store module serves as the repository for all CMS on AWS data. Centralized data storage allows for vehicle telemetry data queries and alerts based on data insertion and thresholds.
Step 5
CMS on AWS users can interact with vehicle telemetry data stored in the CMS on AWS data lake through the CMS API module. The API provided by the module uses AWS AppSync and AWS Lambda functions to build and execute Amazon Athena queries on vehicle data stored in Amazon S3.
Step 6
The CMS Alerts module allows users to receive notifications invoked by data stored in the CMS on AWS data lake. CMS modules can publish to Amazon Simple Notification Service (Amazon SNS) topics defined by the CMS Alerts module by using an API that AWS AppSync provides. Users can subscribe to these same topics to receive email notifications.
Step 7
The CMS EV Battery Health module provides a dashboard through Amazon Managed Grafana which is authenticated by AWS IAM Identity Center. From the dashboard, users can visualize data and set up alerts based on configurable data thresholds.
Step 8
The CMS Vehicle Simulator module provides a user interface (UI) and backend engine for creating, operating, and monitoring simulations of vehicle data emissions.
- Publish Date