---
title: AWS for Logistics & Supply Chain
description: AWS for logistics — Supply Chain vs custom lake, fleet ETA, ERP/WMS freshness. Inventory and operations agents when joins are real. No logistics-agent SKU.
url: https://www.joinhorizon.co/industries/aws-logistics/
updated: 2026-08-31
---

# AWS for Logistics & Supply Chain

> Inventory risk maps, fleet ETA accuracy, and partner N-Tier visibility on top of the WMS you already run — without a rip-and-replace program. Built by an AWS Select Tier Partner.

> **What's New (June 30, 2026)** — **AWS Interconnect – last mile** is in gated preview with AT&T for US customers: private, SLA-backed connections from DCs and branches into a Direct Connect Gateway, with partner provisioning via an activation key. Use it for logistics sites, not plant-floor OT. [Announcement](https://aws.amazon.com/about-aws/whats-new/2026/06/aws-announces-AWS-interconnect-last-mile-ATT-gated-preview/).

## AI opportunity — inventory and ops, not a new SKU

When the pain is “what should we reorder” or “what needs a human this morning,” that is already [inventory](https://www.joinhorizon.co/ai-agents/inventory/) and [operations](https://www.joinhorizon.co/ai-agents/operations/). Same families, same approval rules. We did not add `/ai-agents/logistics/`.

If the dashboard is green on a stale WMS extract, that is a data-freshness problem — EventBridge on failed Glue jobs, not a model. Join keys first; see [knowledge](https://www.joinhorizon.co/ai-agents/knowledge/). Fleet tracking and AWS Supply Chain vs a custom lake stay on this page as AWS architecture.

## Why Logistics Teams Choose AWS

Supply chain visibility programs stall when dashboards look healthy on stale extracts, or when “real-time tracking” is bolted onto fleets that already get adequate ETAs from the TMS. AWS provides AWS Supply Chain, IoT Core, Location Services, EventBridge, Glue, and QuickSight — the architecture decision is which layer earns its operational tax.

FactualMinds is an [AWS Select Tier Services Partner](https://www.joinhorizon.co/aws-partner/) that treats logistics as a data-integration problem first: ERP/WMS/TMS freshness SLAs, then intelligence (risk maps, ETA), then optional device telemetry.

For the full reference architecture — planning tiers, fleet tracking decisioning, and KPI baselines — see [Logistics and Supply Chain on AWS (2026)](https://www.joinhorizon.co/blog/aws-logistics-supply-chain-reference-architecture-2026/).

## Intelligence Layer, Not WMS Replacement

_Figure: ERP/WMS extracts into SCDL or a custom lake, extract-failure alarms, optional Location Services. [Open draw.io](https://www.joinhorizon.co/examples/architecture-blog-2026/logistics-supply-chain/logistics-scdl-fleet.drawio)_

```
ERP / WMS / TMS / OMS
        ↓ (connectors + Glue / EventBridge)
Supply Chain Data Lake (SCDL) or S3 lakehouse
        ↓
AWS Supply Chain insights  OR  Athena + QuickSight
        ↓
OTIF, inventory risk, lead-time prediction, N-Tier visibility
```

AWS Supply Chain does not replace Manhattan, Blue Yonder, or SAP EWM. Execution stays in the WMS; AWS owns the cross-system risk picture.

On a mid-market 3PL silhouette (~2.1M shipments/year, OTIF 82%), layering AWS Supply Chain on ERP ingest plus Location Services fleet tracking moved ETA accuracy from 71% to 87% in 90 days — without replacing the WMS.

## AWS Supply Chain vs Custom Lake

| Situation                                                | Prefer                                                                  |
| -------------------------------------------------------- | ----------------------------------------------------------------------- |
| Multi-ERP, multi-DC, partner N-Tier visibility           | AWS Supply Chain                                                        |
| Single ERP, one region, under ~10k SKUs                  | Glue + Athena + QuickSight                                              |
| Need ML lead-time and inventory risk maps out of the box | AWS Supply Chain                                                        |
| Strong BI team already owns lakehouse patterns           | Custom lake on [data analytics services](https://www.joinhorizon.co/services/aws-data-analytics/) |

## Fleet Tracking Decision

Skip IoT + Location Services when:

- Fewer than ~50 daily routes
- TMS already pushes reliable ETA webhooks
- Nobody owns device certificate lifecycle day-to-day

Add Location Services when last-mile ETA variance is a board KPI and geofence events drive customer notifications. Pair with [managed services](https://www.joinhorizon.co/services/aws-managed-services/) if you need 24/7 extract and device health coverage. For DC and branch backhaul, evaluate **AWS Interconnect – last mile** (AT&T gated preview as of 30 June 2026) before standing up another DIY Direct Connect order.

## Extract Freshness Is the Real Reliability Problem

Silent ERP extract failures produce green dashboards and falling OTIF. Minimum controls:

- EventBridge (or equivalent) on failed Glue/connector jobs
- Row-count anomaly alarms vs yesterday’s baseline
- Freshness SLA (e.g., alert if WMS snapshot older than 2 hours)

This is the same class of reliability work we do in [architecture reviews](https://www.joinhorizon.co/services/aws-architecture-review/) — observability before prettier maps.

## Logistics vs Manufacturing IoT

Plant-floor OEE and PLC/OPC-UA patterns live on the [manufacturing industry hub](https://www.joinhorizon.co/industries/aws-manufacturing/) and the [manufacturing IoT reference architecture (2026)](https://www.joinhorizon.co/blog/aws-manufacturing-industrial-iot-reference-architecture-2026/). Logistics KPIs are shipment movement, partner networks, and last-mile ETA — different sources, different ownership.

## Where to Start

1. Inventory ERP/WMS/TMS sources and current extract freshness
2. Choose AWS Supply Chain vs custom lake from SKU/partner complexity
3. Add fleet tracking only if TMS ETAs are demonstrably insufficient
4. Wire failure alarms before launching OTIF dashboards to executives

Whether you run a 3PL or an in-house distribution network, we help you improve visibility without a rip-and-replace program.

## AWS Services for This Industry

### Inventory and operations (opportunity)
Reorder risk, open POs, and a morning exception brief — the same families as eCommerce, against WMS/ERP joins. Not a logistics-agent SKU. Dashboards on stale extracts are not an agent problem.

Learn more: /ai-agents/inventory/

### Data Analytics
Glue + Athena + QuickSight or AWS Supply Chain SCDL — inventory risk, lead-time prediction, and OTIF dashboards on ERP/WMS extracts.

Learn more: /services/aws-data-analytics/

### Architecture Review
Decide AWS Supply Chain vs custom lake, define extract SLAs, and design EventBridge failure alarms before dashboards go green-stale.

Learn more: /services/aws-architecture-review/

### Serverless Integration
Event-driven ERP/TMS connectors, shipment state machines, and webhook fan-out without standing up always-on middleware.

Learn more: /services/aws-serverless/

### Managed Services
24/7 monitoring for Glue jobs, extract freshness SLAs, and Location Services device certificate lifecycle.

Learn more: /services/aws-managed-services/

### Cost Optimization
Right-size IoT/Location spend for fleet size, and avoid real-time tracking overhead when TMS webhooks already suffice.

Learn more: /services/aws-cloud-cost-optimization-services/

### Cloud Security
Partner data sharing controls, encrypted extracts, and least-privilege IAM across ERP, WMS, and carrier integrations.

Learn more: /services/aws-cloud-security/

## By the Numbers

- **2.1M** — Shipments/yr Mid-Market Silhouette
- **87%** — ETA Accuracy After 90 Days
- **82→87** — OTIF Lift in Engagement Shape
- **N-Tier** — Partner Visibility Patterns

## FAQ

### When should we use AWS Supply Chain vs a custom data lake?
Use AWS Supply Chain when you need enterprise-wide inventory risk maps, ML lead-time predictions, and N-Tier partner visibility across multiple ERP/WMS/TMS sources. Build Glue + Athena + QuickSight when you have a single ERP, one region, and under ~10k SKUs — a nightly S3 extract may be sufficient without the application license.

### Can AWS Supply Chain replace our WMS?
No. AWS Supply Chain is an intelligence layer on top of ERP, WMS, TMS, and OMS — it ingests data into a supply chain data lake (SCDL) and surfaces risk insights. Execution (picking, putaway, slotting) stays in Manhattan, Blue Yonder, SAP EWM, or similar.

### When should we NOT deploy real-time fleet tracking?
Skip IoT + Location Services for fleets under ~50 daily routes if your TMS vendor API already provides adequate ETA webhooks. Real-time tracking adds device cert lifecycle, mobile app maintenance, and geofence tuning — overhead that small operators cannot operationalize.

### What breaks when ERP extracts fail silently?
Inventory health maps show stale green donuts while DCs are stock-out. Symptom: OTIF drops before dashboard alerts fire. Fix: EventBridge rules on failed Glue/connector jobs, row-count anomaly alarms, and an SLA on extract freshness (for example, alert if the WMS snapshot is older than 2 hours).

### Do you sell a logistics AI agent?
No. Inventory and operations families already cover reorder risk and exception briefs. Those pages are commerce-rooted; they apply when WMS/ERP joins are real. We do not invent /ai-agents/logistics/. If extracts are stale, fix freshness before you host a loop.

---

*Source: https://www.joinhorizon.co/industries/aws-logistics/*