Amazon Lookout for Equipment Reaches Its Scheduled Shutdown
AWS's industrial predictive-maintenance service has reached its October 7 retirement date, moving existing customers toward IoT SiteWise or partner alternatives.
Edited by Tyronne Panaino
Amazon Lookout for Equipment reached its scheduled discontinuation date on October 7, 2026. The milestone affects industrial teams that used Amazon Web Services' machine-learning service for predictive maintenance, because AWS had allowed existing customers to keep using it only until this date and now points them toward other anomaly-detection products.
The change is narrower than a general AWS machine-learning withdrawal. It closes a service built around monitoring industrial equipment for abnormal behavior, while leaving customers to decide how to replace that workflow and preserve the operational context around their existing models.
What changed at the deadline
AWS's retirement notice says Lookout for Equipment would be discontinued on October 7, 2026. AWS had already ended access for new customers on October 7, 2025, while allowing existing customers to use the service normally through the later deadline.
During that wind-down, AWS said it would continue security, availability and performance improvements but would not introduce new features. Reaching the documented date therefore changes the practical question for users: the relevant decision is no longer whether the product roadmap will resume, but which supported system should take over its monitoring work.
AWS points builders toward IoT SiteWise
AWS recommends AWS IoT SiteWise to builders moving away from Lookout for Equipment. Its notice says SiteWise added native multivariate anomaly detection in July 2025 and can support Lookout for Equipment modelling. AWS describes the feature as detecting anomalies in configured industrial assets with relatively little setup.
The company also points customers to a repository containing migration scripts and instructions, as well as products available through the AWS Partner Network and AWS Solutions Library. Those options create more than one exit path, but the fetched notice does not establish that any option reproduces every model, alert, diagnostic or operating process a customer used in Lookout for Equipment.
What affected teams still need to verify
A migration decision should be based on the specific monitoring system, not on the shared label of anomaly detection. Teams need to check whether historical sensor data, model assumptions, alert thresholds, maintenance workflows and downstream integrations transfer cleanly to the replacement they choose. They should also test how the new system behaves on their own assets before treating a successful data transfer as equivalent operational performance.
Those checks are especially important for predictive maintenance because the value of a model depends on how well it represents an individual asset and how reliably its outputs reach the people and systems responsible for maintenance. AWS's notice identifies alternatives, but it does not publish migration success rates, feature-parity results or independent comparisons.
Evidence quality and remaining uncertainty
This report is based on one official AWS notice, originally published in September 2024 and reviewed by AWS in October 2025. It clearly establishes the scheduled discontinuation date, the earlier new-customer cutoff and AWS's preferred alternatives. It does not state an exact shutdown time, confirm access status across every account or region, or provide independent evidence about replacement performance.
That is why the article is marked medium confidence: the retirement schedule and vendor guidance are confirmed by the service provider, while the real-world state of individual deployments and the effectiveness of each migration path remain outside the fetched evidence.
Status
Confirmed. AWS's documented October 7, 2026 discontinuation date for Amazon Lookout for Equipment has arrived. Product-by-product migration results remain unverified.
Sources
Update note: Last reviewed 2026-10-07. We will revise this post if AWS publishes a more specific operational status or migration update.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.