The median tenure is 1 year at Amazon. Lots of people cycle through there. Though plenty of people stay for a while. They pay alright and it's not too difficult to get hired.
Also, when I was working there I had a difficult time reconciling myself to how bad it was to work there. On paper it doesn't seem so bad. You get to work on pretty interesting stuff sometimes, you make good money, typically you only have to work 40 hour work weeks, etc. I convinced myself to walk away from a good chunk of money just in bonuses to get out of there, some people might be able to stick it out longer or find the money harder to leave behind.
The problem is that having such a huge portion of the economy being involved in knowledge work is a relatively new thing, and we don't understand the differences between knowledge work and physical work. And especially we don't have thoroughly established standards on what constitute good and bad conditions for knowledge work. We tend to think that sitting in a chair for 8 hours a day is "easy", but it very much is not. A stressful working environment for a knowledge worker is just as bad if not worse than a physical stressful job working extended hours. I only spent a year at Amazon, and most of the time I probably didn't even put in full 40 hour weeks, but I hated it there. In comparison I view the time I spent years ago doing data entry at sometimes up to 70 or 80 hours a week during peak times as comparatively inconsequential. Depending on the team you're on and so forth, working at Amazon can be a painful and stressful experience.
Take being on call for example. In theory this isn't so bad, it's good to give devs exposure to how the ops side of things works, and it's in theory good to give them ownership of their own mistakes so that they have incentive to write good code. The problem is, you're not in charge. You're never going to get permission to dump the resources into making everything run well, ever. Most teams have other priorities and they don't have enough resources to spare to allow you to properly fix the code you're responsible for. Worse, it's not even your code, it's code that was written by someone else years ago who also left years ago. And the next person is just going to get whatever mess you leave behind when you leave. So in the average case you can't actually work to improve things, so being on call is going to always be an extra pain, and a significant intrusion into your theoretically off-work life. Worse, it'll push you behind on all the other stuff you need to deliver.
Meanwhile, you have all the typical office BS of politics, ranking, bad corporate culture, reorgs, etc. that you have to deal with day to day. Some people manage to find good teams in that mess, and others manage to just turn off whatever makes people care about work and just suffer through it for the paycheck. But for a lot of people, more so the more you care, it'll be a stressful nightmare. And the easiest way to avoid dealing with all those problems is to just leave, which lots of people do.