EB CLI lacks support for use of a certificate bundle to use for HTTPS certificate validation

With the AWS CLI the environment variable AWS_CA_BUNDLE specifies the path to a certificate bundle to use for HTTPS certificate validation. The EB CLI does not take this env property into consideration when running. Neither does it support the use of --ca-bundle switch which is also supported by the AWS CLI.

A couple of options are available to resolve the error (both not ideal)
SSLError - SSL validation failed for https://elasticbeanstalk.us-west-2.amazonaws.com/ [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain

1. Specify the switch --no-verify-ssl which will skip SSL certificate verification.
2. The EB CLI uses the certifi package for SSL verification. Manually overriding the cacert.pem within the package on the filesystem resolves the error.

Begin at the EB CLI entry points that create AWS HTTPS clients and inspect how certificate validation currently uses certifi. Compare the behavior with AWS_CA_BUNDLE and the AWS CLI's --ca-bundle option, then verify that the reported self-signed-certificate error is resolved without requiring --no-verify-ssl.

Written by the indexing model from the issue text.