If someone already has aws-elasticbeanstalk-ec2-role role and still facing the issue, recreating the role correctly did the trick for me.