Serverless vehicle tracking at scale: Bosch L.OS on AWS

Summary

Bosch Mobility Platform Solutions developed the Logistics Operating System on AWS to unify vehicle tracking across fragmented spot logistics markets. The system standardizes multiple telematics providers, disparate data formats, and diverse communication protocols into a centralized visibility layer. Orchestration is handled by a Tracking Connector running on Amazon ECS with AWS Fargate, while AWS Lambda functions act as provider-specific adapters for protocol translation. Event-driven message ingestion and streaming rely on Amazon MSK, complemented by Amazon ElastiCache for low-latency caching and Amazon DynamoDB for compliance policy enforcement. Currently operational in India with ten integrated ISVs, the platform reportedly reduces integration costs by 15–20% and lowers total tracking costs for small transporters by 25–30%.

Context

Fragmented logistics networks face incompatible data formats, point-to-point integration complexity, high concurrent tracking volumes, manual coordination, and regional compliance mandates like India's AIS140 and FASTag.

Approach / What changed

Bosch deployed the L.OS platform using Amazon ECS on AWS Fargate for central orchestration, AWS Lambda for serverless provider-specific translation adapters, Amazon MSK for event streaming, Amazon ElastiCache for caching, and Amazon DynamoDB for rule and policy management.

Takeaways

• Consent workflows vary by tracking mode: SIM tracking routes consent requests to the driver, whereas GPS tracking routes requests to the fleet owner.
• Tracking automatically terminates when a vehicle enters a destination geo-fence, or manually via an explicit API request routed through the service provider.
• The architecture reduces integration costs by 15–20% and potentially lowers total tracking costs for small transporters by 25–30%.

Related reading

• Grab · Feb 20, 2024

  The journey of building a comprehensive attribution platform

  Grab needed to modernize its marketing analytics from manual ad hoc queries and high data latency to a platform supporting real-time attribution for pricing models like cost per order. The engineering team initially deployed a pure stream-processing engine using Kappa architecture, Kafka, ScyllaDB, and Redis, which reduced latency from days to minutes and merged ads and promo touchpoints. However, stream-only processing faced high costs, out-of-order event issues, and difficulties running multi-touch models across longer historical windows. Grab transitioned to a Lambda architecture pairing Coban stream processing with Spark-based batch ETL and Amazon S3. This hybrid design separated real-time operational metrics from historical batch reporting, cutting real-time processing costs by approximately 25% while maintaining under 1% data discrepancy.

  Kang Huang

• AWS · Aug 19, 2026

  AI-powered clinical trial eligibility and safety using Amazon Bedrock AgentCore