Writing to EFS however means that you can just treat your EC2 instance as a stateless front-end server that can be swapped out whenever needed.
Couple that with an autoscaling group and when the instance inevitably dies, it'll automatically come back up on a new host.
I don't have an ops team so I prefer AWS to be responsible for stuff like this wherever possible.
It is powered by a Linode. I have literally never needed to manage the server unless I was actively working on something, like changing the theme.
People overcomplicate things these days. You could spend X hours creating some autoscaling, autorecovering setup; but for 99% of projects, it'd maybe encounter an outage that requires your intervention, once a decade.
Too many people are getting hung up on it being WP. AMZN doesn't care what the application is and has no vested interest (that I'm aware of) in WP.
EDIT: clarity
Where a long enough timeline is 700 years (before you're more likely than not to have suffered a full or partial failure).
Taking regular snapshots decreases the chance of an EBS drive failing.