aws / aws/aws-sam-cli

SSL proxy causing issues with deploy

Open
#1,855 9 comments 6 reactions 0 assignees View on GitHub
area/deploy maintainer/need-followup
Dominant language
Python
Stars
6.7k
Forks
1.2k
Avg merge
1d 10h
Merged PRs (30d)
52

Description

### Description

I know there are some issues already created for 'sam build' in an environment with an SSL intercept and I think I have resolved those on my local Windows machine, but I don't seem to be able to get around this error when using 'sam deploy' I am getting this error:

Botocore Exception : SSL validation failed for https://cloudformation.us-east-2.amazonaws.com/ [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1076)

I don't see any way to get boto to be aware of my cert bundle that got me around the other tools. It would be THE BEST if there was a `--verify-ssl-cert=false` that could be passed to all the subsequent tools that sam depends on.

Maybe I need to hard code a boto flag and recompile?

### Steps to reproduce

1. Have an untrusted intercepting proxy.
2. try to deploy with `sam deploy --template-file packaged.yaml --stack-name demo-stack --capabilities CAPABILITY_IAM --debug`

### Observed result

Botocore Exception : SSL validation failed for https://cloudformation.us-east-2.amazonaws.com/ [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1076)

### Expected result

Success deploying

### Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

1. OS: Windows 10
2. `sam --version`: SAM CLI, version 0.43.0

`Add --debug flag to command you are running`

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.