Greetings,
I have an aws project, and I’m trying to get sls deploy to work behind a corporate firewall, which requires a certificate.
by setting AWS_CA_BUNDLE to a specific .pem, I’m able to access aws through the aws cli (aws s3 ls, etc.) but I’m not sure how to make this work for Serverless. is there an environment variable that I can pass in the .pem file needed? I’m stuck with this serverless error:
ServerlessError: self signed certificate in certificate chain
***I used to get the same error with aws before setting the AWS_CA_BUNDLE***
Any help would be very appreciated!
1 Like
ant1
March 20, 2018, 11:37am
2
Same issue here. Did you find a solution? Are we so few people behind a corporate proxy?
I am still facing the same issue still. Any idea how to run this command behind proxy?
I have HTTPS_PROXY and HTTP_PROXY set in environment and NPM.
Serverless: Recoverable error occurred (read ECONNRESET), sleeping for ~7 seconds. Try 4 of 4
Same issue here… who has a solution?
Setting NODE_TLS_REJECT_UNAUTHORIZED to 0 is the key to success
Source:
opened 10:36PM - 15 Feb 17 UTC
closed 01:04PM - 15 Jan 19 UTC
help wanted
<!--
1. If you have a question and not a bug/feature request please ask it at h… ttp://forum.serverless.com
2. Please check if an issue already exists so there are no duplicates
3. Check out and follow our Guidelines: https://github.com/serverless/serverless/blob/master/CONTRIBUTING.md
4. Fill out the whole template so we have a good overview on the issue
5. Do not remove any section of the template. If something is not applicable leave it empty but leave it in the Issue
6. Please follow the template, otherwise we'll have to ask you to update it
-->
# This is a (Bug Report / Feature Proposal)
## Description
For bug reports:
* What went wrong? serverless deploy failed
* What did you expect should have happened? a new lambda function gets pushed to AWS Lambda
* What was the config you used?
```yaml
service: my-lambda-function
provider:
name: aws
runtime: nodejs4.3
stage: dev
region: us-east-1
profile: developer
functions:
hello:
handler: handler.hello
```
* What stacktrace or error message from your provider did you see?
For feature proposals:
* Deploying from behind corporate firewall with multiple IAM roles (dev/prod/etc)
Similar or dependent issues:
http://forum.serverless.com/t/deploying-with-role-behind-company-firewall/1335
## Additional Data
* ***Serverless Framework Version you're using***: v1.7.0
* ***Operating System***: mac os x (Darwin)
* ***Stack Trace***:
```trace
Error: ServerlessError: ServerlessError: connect ETIMEDOUT 54.239.28.247:443
at module.exports.logError.errorHandlingError (/usr/local/lib/node_modules/serverless/lib/classes/Error.js:90:11)
at BbPromise.resolve.then.catch.e (/usr/local/lib/node_modules/serverless/bin/serverless:26:3)
at runCallback (timers.js:649:20)
at tryOnImmediate (timers.js:622:5)
at processImmediate as _immediateCallback
From previous event:
at _dirname (/usr/local/lib/nodemodules/serverless/bin/serverless:24:9)
at Object. (/usr/local/lib/node_modules/serverless/bin/serverless:27:4)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3
```
* ***Provider Error messages***:
ServerlessError: ServerlessError: connect ETIMEDOUT
54.239.28.247:443
For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
