We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.
If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”
Customize cookie preferences
We use cookies and similar tools (collectively, "cookies") for the following purposes.
Essential
Essential cookies are necessary to provide our site and services and cannot be deactivated. They are usually set in response to your actions on the site, such as setting your privacy preferences, signing in, or filling in forms.
Performance
Performance cookies provide anonymous statistics about how customers navigate our site so we can improve site experience and performance. Approved third parties may perform analytics on our behalf, but they cannot use the data for their own purposes.
Allowed
Functional
Functional cookies help us provide useful site features, remember your preferences, and display relevant content. Approved third parties may set these cookies to provide certain site features. If you do not allow these cookies, then some or all of these services may not function properly.
Allowed
Advertising
Advertising cookies may be set through our site by us or our advertising partners and help us deliver relevant marketing content. If you do not allow these cookies, you will experience less relevant advertising.
Allowed
Blocking some types of cookies may impact your experience of our sites. You may review and change your choices at any time by selecting Cookie preferences in the footer of this site. We and selected third-parties use cookies or similar technologies as specified in the AWS Cookie Notice.
Your privacy choices
We display ads relevant to your interests on AWS sites and on other properties, including cross-context behavioral advertising. Cross-context behavioral advertising uses data from one site or app to advertise to you on a different company’s site or app.
To not allow AWS cross-context behavioral advertising based on cookies or similar technologies, select “Don't allow” and “Save privacy choices” below, or visit an AWS site with a legally-recognized decline signal enabled, such as the Global Privacy Control. If you delete your cookies or visit this site from a different browser or device, you will need to make your selection again. For more information about cookies and how we use them, please read our AWS Cookie Notice.
Konten ini tidak tersedia dalam bahasa yang dipilih. Kami terus berusaha menyediakan konten kami dalam bahasa yang dipilih. Terima kasih atas pengertian Anda.
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
Focus on the developer experience
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 easily and securely
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 and store data for analytics and other capabilities
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.
Use event-based alerting
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.
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.
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.
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.