If it is as simple as a permission problem, try placing the CA pem file to anything fewer restrictive like so:If you have proxy included towards your ec2 equipment and it is in non-public subnet which has a S3 vpc-endpoint hooked up. I had been receiving the similar mistake.flag. While it is a poor idea, I applied this as A brief solution to find t