The process is very straightforward and requires little to no extra steps when compared to Vercel.
It's certainly possible you just don't use any of the features they're pushing in that direction, but I mean, they literally dropped basic Request compat just to enable serverless runtimes, and you can't use an img tag without being warned to use their Image Optimization feature, which has no open implementations...
Pretty much, most of the energy being spent on Next.js development is towards serverless deploys which use a build format that has to be reverse engineered by outside parties.
https://www.reddit.com/r/nextjs/comments/1685dyr/avoid_aws_a...
https://www.reddit.com/r/nextjs/comments/160ui01/is_aws_ampl...
https://betterprogramming.pub/beware-of-next-js-on-aws-ampli...
_
To actually use the build output format, you need an implementation that Vercel does not open source.
Compare that to Remix which maintains an open reference implementation for their adapter format, which in turn makes supporting additional platforms incredibly simple.
You can use (almost) all their backend features as if it's a single server (which it is in the end) and you can also use their image tag when self-hosting and it processes the images for you.
If you're annoyed and don't want to use their image tag, then disable the linting rule. However after having used it for a large scale e-commerce store I'm gonna be honest: It works damn good and not paying for Cloudinary or something along those lines is really nice
There are SOME questionable choices like the middleware only being compatible with an edge runtime that can't be turned off, but apart from that one it really is like any other SSR framework....
Edit: added an almost because well, middleware is pretty bad-ish