I got the same error on the AWS Role Creator flow and I found that turning off the "multi-session support" feature solved it.