Configure AWS_CA_BUNDLE environment variable¶
You may encounter an insecure TLS connection error if you are running MSR behind an MITM proxy and using AWS S3 for your storage backend.
To resolve the issue:
Add the
AWS_CA_BUNDLE
environment variable to all of the MSR containers by appending the MSR Helm chartvalues.yaml
file as follows:global: extraEnv: AWS_CA_BUNDLE: "path_to_the_certificate"
Apply the new value:
helm upgrade msr msrofficial/msr --version <version-number> -f values.yaml