-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws s3 (as opposed to s3api) not honoring --no-verify-ssl
#696
Comments
I think the issue is that because |
You're absolutely right. Running It would be really valuable to me if aws-cli also honored this option on the |
BTW, +1 for how quickly you responded to this issue. :) |
* s3-ssl-verify: Add #696 to changelog Update s3 high level commands to honor --no-verify-ssl Add customization to allow for "types" of top level args
+1 again for the responsiveness! Can't wait for the next release. :) Thanks guys! |
* release-1.3.2: Bumping version to 1.3.2 Add entry to changelog Account for list values in def->api translation Updated for the underlying multiple version support. Disable newline integ test on windows Add space in dryrundocs Update changelog Fix comment in test Add integ test for removing file with newlines URLEncode keys Split out object listing into separate object Don't compile jmespath expression in formatter Add #696 to changelog Update s3 high level commands to honor --no-verify-ssl Add customization to allow for "types" of top level args
Testing
aws-cli/1.3.1 Python/2.7.5 Windows/2008ServerR2
in an environment where a corporate security solution acts as a 'man in the middle' for all HTTPS communications. So I need to be either able to add a new trusted CA certificate or disable certificate CA validation for the AWS endpoints entirely.Running this on Windows, even when passing the
--no-verify-ssl
option the command still fails because of the 'invalid' remote certificate.Here is the full debug output:
The text was updated successfully, but these errors were encountered: