That's what safeties are for! We already have a lot of engineering around making elevators safe. TLDR the elevator will clamp on to the rails to slow the free fall.
Neat info below on snapping elevator cables and some of the things that would help you.
https://science.howstuffworks.com/science-vs-myth/everyday-m...
What rails? They're not going to run more than one of these difficult-to-build structures up for each elevator. There will be a single cable, and the car will climb it. What happens if the cable snaps will depend on how far up the car is. Low enough, and it will descend to the surface on a builtin parachute. High enough, and it will perform some portion of an orbit, before descending on its parachute.
Once you have a space elevator, it’s relatively easy to send up some rockets and demolition explosives that just sit on the cables at appropriate locations and stay there waiting for a disaster; should the cable be broken by malice, accident, or natural causes, the explosives can cut the falling cable into pieces small enough that the rockets can safely guide to the ocean (or orbit, whichever has the lowest delta-v).
The travel pods, likewise, can always have rockets on them whose sole purpose is to get the passengers to safely. Yes, it means you’re taking up more mass than you strictly need to, but the great thing about a space elevator is that the mass is no longer a hyper-critical parameter.
Presumably you could have redundant cables. But two almost adjacent cables would still be exposed to many single points of failure, especially any caused by a deliberate attack on the system.
And just a cable falling could be a significant disaster by itself.
The rails? The car will travel over a stationary structure, not be pulled up by a pulley like a conventional elevator is. So it is failure of that stationary structure that we are talking about.
You certainly should worry about the possibility of zero day attacks either when using FOSS or a proprietary solution.
If the provider of a proprietary solution stops offering it you might have no easy path of migration where as hypothetically FOSS solutions are easier to self host or find a new hoster for (and thus reducing the cost of a potential migration)
If a FOSS solution is abandoned, it's doubtful that most companies are going to take on the maintenance themselves. They are going to start an initiative to migrate.
But that goes back to the old saying "no one ever got fired for buying IBM." The same can be applied to Microsoft or AWS. Yes MS has put plenty of technologies in maintenance mode but you didn't have to rush to migrate. IBM still sells system that are compatible with what they sold in the 80s.
On the other hand, if a FOSS solution is abandoned you typically have quite a long time to migrate since you can self-host. If AWS shuts down tomorrow and you rely on it heavily, you're basically fucked.
If AWS shuts down tomorrow. There are a lot of companies that are going to be in the same boat - including Amazon and Netflix.
I would be more worried about my one colocated data center getting shut down or getting destroyed than the entire global AWS infrastructure that has data centers in 50+ availability zones.
As far as software, most AWS services are just managed versions of available software. Even if you're using lambdas for API endpoints, if you treat your lambdas like Controller actions, it shouldn't be that much of a heavy lift to concert them into standard MVC APIs equivalent.
For another perspective, listen to the podcast interview of Adrian Cockcroft, the guy who led the migration of Netflix's infrastructure from self hosted to AWS hosted.