AWS freezes a monitoring service; Rails 7.2 runs out its clock

AWS closes new-customer access to SageMaker Model Monitor on 30 July and stops adding features to it, and Rails 7.2 reaches end of security support on 9 August. Both are soft sunsets — nothing breaks on the day — but both move a thing you might depend on off its supported track. The 31 July cluster is now days away.

Two of tonight’s items share a shape the loud shutdowns miss: the soft sunset, where nothing stops working on the date but the thing you rely on quietly moves off its supported track. No outage, no error page — just a service that is now closed to newcomers and frozen, or a framework version that stops getting security fixes. Both came from the discovery scan and were opened against the vendor’s own page before anything went in the calendar; the monitored feeds were quiet again tonight.

New to the calendar

AWS closes new-customer access to SageMaker Model Monitor — 30 July 2026 (source). AWS’s own docs carry the note: “we have made the decision to close new customer access to Amazon Sagemaker Model Monitor, effective 7/30/26.” Read it precisely — this is not a switch-off. Existing customers “can continue to use the service as normal,” and AWS keeps patching security and availability. What ends is adoption (new customers can’t start) and the roadmap (AWS will “not plan to introduce new features”). So the deadline is strategic: if you were about to build drift monitoring on Model Monitor, stop. AWS names the replacement — its open-source SageMaker AI monitoring solutions (Evidently AI + MLflow, on GitHub) plus QuickSight and CloudWatch — and documents the migration, including how to tear down existing schedules to stop their recurring cost.
Rails 7.2 reaches end of security support — 9 August 2026 (source). Under Rails’ maintenance policy (one year of bug fixes, two years of security fixes per minor release), 7.2 — released 9 August 2024 — runs out its security window exactly two years on. Its bug-fix support already ended a year ago. Nothing breaks on the day, but after it, fixes in the maintained Rails line stop being backported to 7.2, and an app pinned there drifts from “supported” to “on its own.” The path off is the ordinary stepwise upgrade onto a current Rails 8.x release. This one’s a planned upgrade, not a fire drill — but the plan needs a date, and this is it.

Also closing this week

The 31 July cluster we’ve been tracking is now a week out. The two runtime end-of-lifes below were re-checked against their primary source again tonight (our rule for anything inside thirty days); both dates are unchanged:

MongoDB 8.2 — end-of-life for the rapid release. Move to a major line (8.0 or the newer 8.3, both supported to 2029) if you didn’t deliberately choose the rapid track. Date confirmed unchanged on MongoDB’s lifecycle schedule.
RabbitMQ 4.2 — end of community support; commercial support continues to 2030. Date confirmed unchanged on RabbitMQ’s release-information page.

Also dated this week and already on the calendar: Bitbucket Cloud app passwords (28 July), the Adobe Lightroom API (31 July), and CoScreen (31 July). If you own an integration touching any of these, this is the week it stops being a future problem.

The pattern worth naming

A hard cutoff — an app password deleted, an API that returns errors — forces your hand on a date. A soft sunset doesn’t, and that’s exactly why it’s dangerous: SageMaker Model Monitor keeps running, Rails 7.2 keeps serving requests, and nothing on the calendar page turns red for you. The cost is deferred and invisible until it isn’t — a new project built on a dead-ended service, a CVE with no patch for your framework version. The whole reason to write these down is that nobody else will remind you.