TIL - MySQL 5.7 silently fails when handling UTF-8 characters in latin1
By now, I would assume most companies have already made the jump from Aurora 2.x to Aurora 3.x to avoid extended support costs (i.e. penalties).
If not, note that by default, Aurora 2.x will accept non-latin1
characters.
Aurora 3.x does not do this. It will return errors when a non-latin1
character is added. Depending on how your clients handle these, it could be an outage waiting to happen!