I've recently tried upgrading from v3.1 to v3.3, during a windows server upgrade (2012 -> 2016). I can't get the new version to work, it keeps throwing "AWS credentials invalid", even though the credentials are correct. I've updated the policy according to the new policy required by 3.3, b...