What Sam means is when Eramba uses the newer PHP Cake framework major version, it’ll likely be resolved.
However, it is curious that Aurora stuffs up something that the equivalent/later plain MySQL has resolved years ago. It means that it’s not MySQL+bits = Aurora, but instead AWS must be cherry-picking from new MySQL releases into their existing Aurora codebase. That’s an expensive way of maintaining. I expect to see more incompatibilities and other problems with that in the future.