If it is as simple as a authorization concern, try out environment the CA pem file to one thing significantly less restrictive like so: If you have proxy included on your ec2 equipment and it is actually in non-public subnet with a S3 vpc-endpoint attached. I used to be obtaining the exact same mistake. Issue most probably due to company prox