I'd the exact same concern on Windows ten. It occurs to generally be a result of the aws cli not studying the web proxy location through the Windows registry. Fastened identical mistake by environment the ecosystem variables HTTP_PROXY and HTTPS_PROXY to the corporate internet proxy. Hope it helps somebody!In my scenario, it happened the S3 company