If it is so simple as a permission issue, attempt location the CA pem file to anything less restrictive like so: when you have proxy added to your ec2 machines and it is in non-public subnet which has a S3 vpc-endpoint hooked up. I was getting the same error. Dilemma https://iam99742963.blogpixi.com/29456658/iam997-an-overview