If it is as simple as a authorization problem, test placing the CA pem file to a thing fewer restrictive like so: when you have proxy added in your ec2 devices and it can be in private subnet using a S3 vpc-endpoint connected. I had been receiving the exact error. flag. However it is a negative thought, I utilized this as a temporary Alternat