View a markdown version of this page

Provide DaaS to Fleet Customers: Data flow - Provide DaaS to Fleet Customers
DaaS data flow diagramFurther readingDiagram history

Provide DaaS to Fleet Customers: Data flow

Publication date: February 16, 2023 (Diagram history)

With this architecture, you can build a serverless Data as a Service (DaaS) platform. Ingest, process, and deliver vehicle data to fleet owner applications. Use a data API subscription model for customer-specific delivery. The solution uses Amazon Kinesis Data Streams for ingestion, Amazon EventBridge for event routing, and AWS Lambda for processing.

DaaS data flow diagram

Reference architecture diagram showing DaaS data flow for fleet customers by using Amazon Kinesis, Amazon EventBridge, and Lambda.

The following steps describe the data ingestion and delivery pipeline for this architecture:

  1. Stream vehicle telemetry and diagnostic events into Amazon Kinesis Data Streams or Amazon MSK. Store raw events in Amazon Simple Storage Service for long-term retention.

  2. Process streaming events with Lambda or AWS Step Functions. Perform event validation, transformation, and filtering. Use Amazon RDS for reference data such as subscription status and event schema.

  3. Store processed events in Amazon DynamoDB. Use DynamoDB as the data layer for on-demand request APIs.

  4. Send transformed events to the Amazon EventBridge default event bus.

  5. Retrieve events from the default event bus with Lambda. Enrich events with customer-specific data from Amazon RDS. Send enriched events to a delivery event bus.

  6. Process matching telemetry events with Amazon EventBridge rules. Route them to customer-specific Amazon Simple Queue Service queues for buffering until consumed.

  7. Make API calls to Amazon API Gateway from fleet applications. Invoke Lambda to process requests.

  8. Pull events from Amazon SQS queues for streaming data. Read events from DynamoDB for on-demand requests.

  9. Route alerts and time-sensitive events to customer-specific HTTP endpoints by using an Amazon EventBridge API target.

Further reading

For additional information, see the following resources:

Diagram history

To receive updates about this reference architecture diagram, subscribe to the RSS feed.

ChangeDescriptionDate

Initial publication

Reference architecture diagram first published.

February 16, 2023

Initial publication

Reference architecture diagram first published.

February 16, 2023

RSS subscription requirement

To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.