Deploying with role behind company firewall

I have installed serverless via npm globally.

My credentials file in .aws directory has multiple roles (2)

When I run
SLS_DEBUG=* serverless deploy -v

I get.

WARNING: You are running v1.7.0. v1.8.0 will include the following breaking changes:
- Will replace IamPolicyLambdaExecution resource with inline policies ->
- “sls info” will output the short function name rather than the lambda name ->

You can opt-out from these warnings by setting the “SLS_IGNORE_WARNING=*” environment variable.


Error --------------------------------------------------

 ServerlessError: ServerlessError: connect ETIMEDOUT

 For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

Stack Trace --------------------------------------------

Error: ServerlessError: ServerlessError: connect ETIMEDOUT
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] (timers.js:594:5)
From previous event:
at __dirname (/usr/local/lib/node_modules/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

Get Support --------------------------------------------

 Please report this error. We think it might be a bug.

Your Environment Information -----------------------------
OS: darwin
Node Version: 6.9.4
Serverless Version: 1.7.0

Note: I’m behind corporate firewall using SSO. My .aws is under the local user directory, my npm install -g serverless is global. My serverless.yml looks like this

name: aws
runtime: nodejs4.3
stage: dev
region: us-east-1
profile: aws_developer_role

handler: handler.hello

I’m going to guess the reason you are not getting a lot of responses is a result of what you already outline. This is a connectivity problem between your machine and AWS services via https. This will either be your machine’s firewall, anti virus or your company’s firewall. There is little we can do to help you debug this, you will need to involve your admin.

Can you manually access the AWS console from your same environment?