[SEO Subhead]
This Guidance shows how to gather, collect, and distribute data from your connected vehicles using AWS IoT FleetWise to Salesforce Automotive Cloud. To build lasting customer relationships through informed interactions, customer service agents must be empowered with timely, relevant vehicle information. With AWS IoT FleetWise and Salesforce Automotive Cloud, you can take action on vehicle events in near real-time to provide impactful customer experiences that drive brand loyalty and differentiate your business.
Note: [Disclaimer]
Architecture Diagram
[Architecture diagram description]
Step 1
A connected vehicle has numerous sensors monitoring various data points, such as tire pressure, which need to be collected, analyzed, and acted upon.
Step 1 (continued)
AWS IoT Core can serve as a communication mechanism to facilitate the transfer of data from the edge to the cloud, supporting protocols like a controller area network (CAN), CAN-FD, an extension of the CAN protocol that allows for faster data rates, and on-board diagnostics (OBDII). Data from various electronic control units (ECUs) can also be collected and analyzed using AWS IoT Core.
Step 2
The AWS IoT FleetWise Edge Agent communicates with the vehicle’s network, decodes signals and sends data payloads through AWS IoT Core. AWS IoT FleetWise campaigns define how the data is selected, collected, and transferred.
Step 3
AWS IoT Core functions as a secure communication mechanism, facilitating the transfer of data from the edge devices to the cloud infrastructure. AWS IoT Core collaborates with AWS IoT FleetWise to transmit vehicle signal data, such as low tire pressure indications, directly from the vehicle to an Amazon Simple Storage Service (Amazon S3) event bucket.
Step 4
When an event, originating from either the AWS IoT Core rules engine or an AWS IoT FleetWise campaign, is detected in the specified event bucket, it is automatically ingested into an Amazon Simple Queue Service (Amazon SQS) queue.
Step 5
Implement an Amazon EventBridge Pipe to source events from the Amazon SQS queue, transform, and potentially enrich the event payload. Next, forward it to a custom event bus target.
Step 6
The custom event bus is configured with rules to dispatch each incoming event to multiple targets, including a designated application endpoint within the Salesforce Automotive Cloud, which initiates the downstream processing of the event for service technicians.
Step 7
Select Amazon DynamoDB as a secondary target from the custom event bus, and record all events to display in the fleet management platform.
Step 8
Salesforce Automotive Cloud then uses internal routing mechanisms to send the event notification to one or more downstream personas.
Step 1
A connected vehicle has numerous sensors monitoring various data points, such as tire pressure, which need to be collected, analyzed, and acted upon.
Step 1 (continued)
AWS IoT Core can serve as a communication mechanism to facilitate the transfer of data from the edge to the cloud, supporting protocols like a controller area network (CAN), CAN-FD, an extension of the CAN protocol that allows for faster data rates, and on-board diagnostics (OBDII). Data from various electronic control units (ECUs) can also be collected and analyzed using AWS IoT Core.
Step 2
The AWS IoT FleetWise Edge Agent communicates with the vehicle’s network, decodes signals and sends data payloads through AWS IoT Core. AWS IoT FleetWise campaigns define how the data is selected, collected, and transferred.
Step 3
AWS IoT Core functions as a secure communication mechanism, facilitating the transfer of data from the edge devices to the cloud infrastructure. AWS IoT Core collaborates with AWS IoT FleetWise to transmit vehicle signal data, such as low tire pressure indications, directly from the vehicle to an Amazon Simple Storage Service (Amazon S3) event bucket.
Step 4
When an event, originating from either the AWS IoT Core rules engine or an AWS IoT FleetWise campaign, is detected in the specified event bucket, it is automatically ingested into an Amazon Simple Queue Service (Amazon SQS) queue.
Step 5
Implement an Amazon EventBridge Pipe to source events from the Amazon SQS queue, transform, and potentially enrich the event payload. Next, forward it to a custom event bus target.
Step 6
The custom event bus is configured with rules to dispatch each incoming event to multiple targets, including a designated application endpoint within the Salesforce Automotive Cloud, which initiates the downstream processing of the event for service technicians.
Step 7
Select Amazon DynamoDB as a secondary target from the custom event bus, and record all events to display in the fleet management platform.
Step 8
Salesforce Automotive Cloud then uses internal routing mechanisms to send the event notification to one or more downstream personas.
Get Started
Well-Architected Pillars
The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.
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.
-
Operational ExcellenceRead the Operational Excellence whitepaper
The low-code, no code services, including AWS IoT Core, Amazon DynamoDB, EventBridge, and Amazon SQS collectively address key challenges in connected vehicle, Internet of Things (IoT) systems, and downstream interactions with your partners. These managed services handle your data transfer, processing, and storage needs while helping ensure security and proactive payload health monitoring. The shared responsibility model lets you concentrate on product development while AWS manages the underlying infrastructure.
-
SecurityRead the Security whitepaper
AWS IoT Core provides secure communication and authentication for IoT devices, preventing unauthorized access. EventBridge provides both encryption at rest and encryption in transit to protect your data. EventBridge encrypts data that passes between EventBridge and other services by using Transport Layer Security (TLS). By using these services, you can mitigate security risks, protect sensitive data, and maintain the integrity and confidentiality of information, crucial for building trust and helping ensure compliance in vehicle-to-Salesforce Auto Cloud deployments.
-
ReliabilityRead the Reliability whitepaper
The services in this Guidance help you reduce the risk of system failures, downtime, and data loss in your IoT deployments. Specifically, AWS IoT Core helps ensure reliable and secure data transfer between devices and the cloud, reducing the risk of data loss or communication failures. In addition, all of the cloud resources in this Guidance are serverless and scale with demand, helping prevent system downtime even if demand increases.
-
Performance EfficiencyRead the Performance Efficiency whitepaper
This Guidance uses serverless systems to allow for scalability as well as minimum configuration and maintenance for you. For example, AWS IoT Core is purpose-built to manage a large fleet of devices, such as vehicles, through dynamic policies and device configuration for near real-time updates from the edge to the cloud. Additionally, Amazon S3 provides the capability of querying, scaling, and storing the workload data requirements. Lastly, AWS IoT Core offers features such as shared subscriptions, topic aliasing, and payload size reduction, which optimize data transfer and reduce latency, enhancing the overall performance of this architecture and contributing to faster data processing.
-
Cost OptimizationRead the Cost Optimization whitepaper
AWS IoT FleetWise can help minimize data transfer charges by limiting the data transferred in and out of the AWS Region to only the necessary information, as determined by the configured campaigns. Additionally, AWS IoT Core optimizes data transfer and communication, reducing data transmission costs and improving overall efficiency, which directly contributes to cost savings. Moreover, the usage-based pricing model of AWS IoT Core helps ensure that you only pay for the resources you consume. These services can assist in striking a balance between maintaining high-quality services and controlling costs, leading to more efficient and cost-effective IoT operations.
-
SustainabilityRead the Sustainability whitepaper
The services described in this Guidance reduce the need for on-premises infrastructure and its associated energy consumption. AWS IoT Core enables efficient data processing and transmission, leading to energy savings. AWS IoT Core also supports over-the-air (OTA) updates, reducing the need for physical recalls or manual updates, and incorporate monitoring and analytics tools to identify inefficiencies and anomalies. This helps optimize resource utilization and reduce the environmental impact.
Related Content
[Title]
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.
References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.