View a markdown version of this page

Transportation and logistics data lake - Data and Analytics Reference Architecture Diagrams

Transportation and logistics data lake

Publication date: March 15, 2020 (Diagram history)

This architecture shows how to break data silos and create a single repository for transportation and logistics data from multiple sources. You can use a fully managed, pay-per-use, and scalable architecture to remove the complexity and costs of managing on-premises databases.

Transportation and logistics data lake diagram

Data from sources lands in an Amazon S3 data lake governed by Lake Formation, cataloged by AWS Glue, analyzed with Athena.

The following steps describe the architecture:

  1. Ingest data from multiple sources: historical and large databases with AWS Snowball, real-time data with Amazon Kinesis Data Streams, ERP data synchronization with AWS DataSync, and mobile app data with AWS AppSync.

  2. Automatically extract, transform, and load raw data with Lake Formation. Discover schemas and create a data catalog for further data exploration.

  3. Create an Amazon Simple Storage Service data lake where you can store, organize, and access business-critical data securely. Use Amazon EMR for fine-grained control over extraction, transformation, and loading (ETL) jobs. Use AWS Glue to manage your data catalog.

  4. Turn raw data into actionable knowledge with Athena and AWS Quick Sight. Disseminate key business intelligence insights across your organization. Use SageMaker AI to deliver ML-based predictive and prescriptive analytics.

  5. Use AWS fully managed databases to deliver specific capabilities: Amazon Neptune graph database for network optimization, Amazon Aurora for fast relational queries, and Amazon DynamoDB for interactive mobile and web apps with real-time updates. Avoid data latency with live data stream ingestion from Kinesis Data Streams.

Further reading

For additional information, refer to the following resources: