This Guidance helps oil and gas facility operators deploy AWS services and Independent Software Vendor (ISV) Partner applications to optimize asset tracking, fleet management, driving directions, and other location-centric business processes. You can increase efficiency and mitigate supply chain risks of feed, products, and intermediates through waterborne cargoes, pipelines, railcars, and trucks. This Guidance aims to improve logistics operational agility, lower operating expenses, and reduce field risk.
Architecture Diagram

[text]
Step 1
An industrial data lake built with Amazon Simple Storage Service (Amazon S3), AWS Glue, and Amazon Timestream stores timeseries data. Scheduled AWS Glue crawlers and the AWS Glue Data Catalog organize data sources and relationships.
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 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.
Implementation Resources

A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.
The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.
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.