This was caused by an internal issue on AWS. The giveaway was when searching this error nothing was coming up at all. I went onto the AWS Service Health Page and found an issue registered with AWS IAM:
Once this issue was resolved, my stack was deployed as expected.