Guidance for Downstream Logistics Optimization on AWS
Overview
How it works
This architecture diagram uses an industrial data lake and location-based data to increase asset utilization.
Well-Architected Pillars
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 Excellence
Lambda application code emits information about logic and outcomes directly into Amazon CloudWatch. Logs and insights from CloudWatch use the instrumented logic to create operational dashboards for monitoring and alerts.
Security
All services in this Guidance, including Amazon S3, Timestream, and Amazon Aurora, have server-side encryption using encryption keys stored in AWS Key Management Service (AWS KMS).
Reliability
This Guidance is event-driven, providing a modular, microservices approach for AWS services, including Amazon Location. Data processing pathways are loosely coupled, and you can remove these pathways or replace them with ISV AWS Partner software with minimal impact on the overall architecture.
Performance Efficiency
Amazon Location provides fleet tracking, optimized routing, and geofencing capabilities that are crucial for logistics-dependent business processes. If asset locations are better aligned with AWS IoT Core, you can instead send the data as MQTT messages, providing different configurations to match business and technical requirements.
Cost Optimization
Lambda participates in Compute Savings Plans, which allows 1- or 3-year terms of discounted rates for the amount of Lambda usage.
Sustainability
Amazon S3 Lifecycle configuration supports transfers of data objects to a more sustainable storage class tier based on pre-defined rules.
Disclaimer
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages