This week brought dueling announcements from AWS and Azure around industrial edge computing, and it’s clear that the cloud giants see manufacturing and industrial IoT as the next major growth frontier. AWS expanded its IoT Greengrass V3 platform with new ML inference capabilities at the edge, while Azure announced preview availability of Azure IoT Operations — a Kubernetes-based edge runtime designed for factory environments. Having spent a chunk of my career working on IoT systems before “IoT” was even a term, these developments feel like a significant inflection point.
The Industrial Edge Opportunity#
Here’s why the cloud providers are so interested in the factory floor: manufacturing represents one of the largest untapped markets for cloud services. Factories generate enormous amounts of data from sensors, PLCs, SCADA systems, and machine vision cameras, but most of that data is processed locally using proprietary industrial control systems and never touches the cloud.
The promise of industrial edge computing is to bring cloud-native capabilities — ML inference, data analytics, fleet management, over-the-air updates — to these environments without requiring all the data to travel to a distant cloud region. This isn’t just about cost savings on data transfer; it’s about latency requirements. When you’re controlling a robotic arm or monitoring a safety-critical process, you can’t afford the 50-200ms round trip to a cloud region. Decisions need to happen in single-digit milliseconds.
The total addressable market is staggering. McKinsey estimates that IoT applications in factory settings alone could generate $1.2-3.7 trillion in value annually by 2030. Even capturing a small slice of that is enormous for cloud providers whose core markets are maturing.
What AWS Announced#
AWS IoT Greengrass V3 is an evolution of their edge runtime that runs on industrial gateways and edge servers. The new ML inference pipeline is the standout feature — you can now deploy SageMaker-trained models to Greengrass devices and run inference locally with hardware acceleration on NVIDIA Jetson, Intel Movidius, and AWS’s own Graviton-based edge hardware.
The practical application is predictive maintenance. Deploy a vibration analysis model to a gateway connected to dozens of motors and pumps, run inference on sensor data locally, and only send anomaly alerts to the cloud. I’ve built similar systems from scratch, and the amount of custom plumbing required was substantial. Having this as a managed service significantly lowers the barrier.
AWS also introduced Greengrass Streams Manager for buffered data ingestion, which handles the messiest part of industrial IoT: unreliable connectivity. Factory networks are noisy, connections drop, and you need to guarantee that sensor data isn’t lost when the WAN link goes down. Streams Manager provides local buffering with configurable retention and prioritization, syncing to cloud storage when connectivity is available.
What Azure Announced#
Azure IoT Operations takes a different architectural approach. Rather than building a proprietary edge runtime, Microsoft is going all-in on Kubernetes at the edge. Azure IoT Operations runs on Arc-enabled K3s clusters — lightweight Kubernetes distributions designed for resource-constrained environments.
This is a bold bet. Running Kubernetes on an industrial gateway with 4GB of RAM and an ARM processor sounds like madness if you’ve only seen Kubernetes in the data center. But K3s has matured to the point where it’s genuinely viable on modest hardware, and the operational benefits are significant. You get the same deployment model, observability stack, and security posture at the edge as you do in the cloud.
The platform includes MQTT broker integration, OPC-UA connectivity for industrial protocols, and a data pipeline framework that processes and transforms sensor data before forwarding it to Azure services. The OPC-UA support is crucial — it’s the lingua franca of industrial automation, and any serious IoT platform needs native support for it.
Microsoft is also leveraging its acquisition of AT&T’s Network Cloud operations to provide private 5G connectivity for factories. This addresses the networking challenge directly: instead of relying on flaky WiFi or running Ethernet to every sensor, factories can deploy private 5G cells that provide reliable, low-latency connectivity across the facility.
The Convergence of OT and IT#
What excites me most about these announcements is the convergence of operational technology (OT) and information technology (IT). Historically, factory automation was a completely separate world from cloud computing. Different protocols (Modbus, PROFINET, EtherCAT vs. HTTP, gRPC), different tooling (PLCs, HMIs, SCADA vs. containers, CI/CD), and different teams that rarely talked to each other.
Edge computing platforms are bridging this gap. When you can run a container on an industrial gateway that speaks OPC-UA to a PLC and MQTT to a cloud broker, you’ve created a common layer where OT and IT can collaborate. Factory engineers can focus on the physical processes while software engineers handle the data pipeline and ML models.
But this convergence also brings challenges. Industrial systems have safety requirements that cloud systems don’t. A misconfigured container won’t kill anyone in a data center, but an incorrect signal to a safety controller in a factory absolutely could. Both AWS and Azure need to ensure their edge platforms integrate properly with safety instrumented systems (SIS) and don’t introduce new failure modes into critical processes.
My Take#
I’m genuinely excited about industrial edge computing, but I’ve been in this industry long enough to remember the early IoT hype cycle of 2015-2018 and how long it took for the reality to catch up with the marketing. The technology is significantly better now, and the cloud providers are committing serious engineering resources rather than just marketing dollars.
The choice between AWS and Azure for industrial IoT will often come down to existing cloud relationships and specific industry partnerships. AWS has a head start in general-purpose IoT, while Azure has stronger enterprise relationships and the advantage of integrating with the Microsoft ecosystem that many manufacturers already use.
If you’re an engineering team looking at industrial edge computing, my advice is to start small. Pick one production line, one use case (predictive maintenance is the easiest win), and build a proof of concept. The platforms are mature enough for production use, but the organizational change management — getting IT and OT teams to collaborate effectively — is usually the harder challenge.
This is part of my ongoing Infrastructure Notes series, covering developments in cloud, infrastructure, and operational technology.