... The service does this by keeping a log of all transactions for a set amount of time (up to 72 hours). When things go bad after you dropped the wrong table in your production database, you simply pause your application and select the point in time that you want to go back to. Aurora will then pause the database, too, close all open connections and drop anything that hasn’t been committed yet, before rolling back to its state before the error occurred...
It sounds like the old familiar point in time restore from transaction log backups, except that AWS has wrapped a user friendly process around it. Just replace the word "Aurora" with "The Grumpy DBA" and it could be a quote taken from a database operations manual back in 2000.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho