In brief: AWS lists Amazon FinSpace, Fraud Detector, IoT Greengrass V1, Lookout for Equipment, Proton and WAF Classic with end of support on October 7, 2026. The effects are specific for Proton, FinSpace and Lookout. Official pages conflict for Greengrass V1 and WAF Classic, so operators should verify their AWS Health Dashboard and regional status.
What the central register says ends today
AWS places all six offerings in “Services in Sunset”. That does not always mean infrastructure disappears immediately: the date ends operations and support, while the outcome varies by service.
Existing CloudFormation stacks and their resources survive AWS Proton. Proton's management and delivery layer, plus stored service data, do not. AWS suggests CloudFormation Git Sync, CodePipeline and CodeBuild, GitHub Actions, or the Backstage-based Harmonix partner solution.
Amazon FinSpace documentation says customers lose access to its console and resources. Managed kdb Insights users should export database contents and application code to S3, then run kdb themselves. For Lookout for Equipment, AWS recommends AWS IoT SiteWise anomaly detection or partner products and provides migration scripts.
AWS points Amazon Fraud Detector users to AutoGluon with SageMaker AI, or WAF Fraud Control for certain registration attacks. Its dedicated availability page, however, mentions only the November 7, 2025 new-customer cutoff, not the support end shown in the central register.
Official pages provide three WAF timelines
The clearest discrepancy concerns AWS WAF Classic. The central register says October 7, 2026, while the migration guide says support ended on September 30, 2025. Another WAF page directs customers to the regional AWS Health Dashboard for specific milestones. These statements do not establish one global shutdown time.
IoT Greengrass V1 documentation also conflicts. The current migration guide names October 7, 2026 and stresses that V1 and V2 are not backwards compatible. The Greengrass product page instead says June 1, 2026. A normal V1 over-the-air update cannot upgrade Core devices to V2, so fleets require migration through the selected V2 runtime path.
Pandorex Analysis
The shared date reflects a portfolio shift more than one uniform technical shutdown: specialised services are being replaced by broader building blocks, open-source tools or partner products. The documentation mismatch is itself an operational risk. Teams should verify inventory, exports, upgrade paths and regional health notices individually; the central sunset table is not sufficient on its own for a go/no-go decision.