artilleryio / artilleryio/chaos-lambda
Error: connect ETIMEDOUT
- Dominant language
- JavaScript
- Stars
- 290
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Hi - trying to deploy this to my aws account; have everything setup on the AWS side and I am behind a corporate proxy; but I have set my HTTP-PROXY & HTTPS-PROXY env vars in my shell and can run the aws cli w/ out a problem, yet still receiving this error...any suggestions to get around this? thanks.
LIBP45P-16600WL:.aws n0224265$ llama deploy -r $LAMBDA_ROLE_ARN
Something went wrong:
{ Error: connect ETIMEDOUT 54.236.138.8:443
at Object.exports._errnoException (util.js:1022:11)
at exports._exceptionWithHostPort (util.js:1045:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
message: 'connect ETIMEDOUT 54.236.138.8:443',
code: 'NetworkingError',
errno: 'ETIMEDOUT',
syscall: 'connect',
address: '54.236.138.8',
port: 443,
region: 'us-east-1',
hostname: 'lambda.us-east-1.amazonaws.com',
retryable: true,
time: 2017-03-16T18:55:39.380Z }
Contributor guide
Research direction
Start with the `llama deploy -r $LAMBDA_ROLE_ARN` entry point and trace how it connects to `lambda.us-east-1.amazonaws.com` when HTTP-PROXY and HTTPS-PROXY are set. Reproduce the timeout if possible and determine whether deployment succeeds through the corporate proxy or needs a documented configuration change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100