If it is so simple as a permission situation, try out setting the CA pem file to some thing less restrictive like so: When you've got proxy extra for your ec2 equipment and it is in private subnet having a S3 vpc-endpoint attached. I was getting the identical error. For those who don’t wish to use an setting variable, You can even configure