我的工作站是公司代理的后面，我设置了环境变量，我可以使用除了aws-sdk和NodeJS之外的所有内容。这里是TCP连接的转储：
No. Time Source Destination Protocol Length Info
2 1.834143 105.103.15.106 105.103.82.47 TCP 74 54952 → 8080 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=497254718 TSecr=0 WS=128
3 1.836141 105.103.82.47 105.103.15.106 TCP 74 8080 → 54952 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460 SACK_PERM=1 TSval=3399116010 TSecr=497254718 WS=128
4 1.836165 105.103.15.106 105.103.82.47 TCP 66 54952 → 8080 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=497254719 TSecr=3399116010
5 1.836779 105.103.15.106 105.103.82.47 TCP 310 54952 → 8080 [PSH, ACK] Seq=1 Ack=1 Win=29312 Len=244 TSval=497254719 TSecr=3399116010
6 1.838250 105.103.82.47 105.103.15.106 TCP 66 8080 → 54952 [ACK] Seq=1 Ack=245 Win=15616 Len=0 TSval=3399116012 TSecr=497254719
20 123.670911 105.103.82.47 105.103.15.106 TCP 66 8080 → 54952 [FIN, ACK] Seq=1 Ack=245 Win=15616 Len=0 TSval=3399237839 TSecr=497254719
21 123.674168 105.103.15.106 105.103.82.47 TCP 66 54952 → 8080 [FIN, ACK] Seq=245 Ack=2 Win=29312 Len=0 TSval=497285178 TSecr=3399237839
22 123.676592 105.103.82.47 105.103.15.106 TCP 66 8080 → 54952 [ACK] Seq=2 Ack=246 Win=15616 Len=0 TSval=3399237843 TSecr=497285178
请注意，三次握手没问题，比客户端（ip结束于106）在包号5上发送一些数据（psh，ack），立即发送，接收代理的ACK（包号6）。然后长时间没有通信（7到19之间的包不是来自这个tcp对话），数据包20是FIN（由于没有发送包的代理超时？）。此对话由example provided by Amazon生成。
节点版本：在6.10.0,6.11.0和8.1.3上测试 今天安装的SDK（2.82.0）
作为比较，我在同一台Ubuntu机器上运行aws cloudformatin describe-stack-resources --stack-name my-stack。众所周知，aws CLI是python，命令运行正常，会话就像：
No. Time Source Destination Protocol Length Info
1 0.000000 105.103.15.106 105.103.82.47 TCP 74 54940 → 8080 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=496906305 TSecr=0 WS=128
2 0.001987 105.103.82.47 105.103.15.106 TCP 74 8080 → 54940 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460 SACK_PERM=1 TSval=3397722434 TSecr=496906305 WS=128
3 0.002008 105.103.15.106 105.103.82.47 TCP 66 54940 → 8080 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=496906305 TSecr=3397722434
4 0.002100 105.103.15.106 105.103.82.47 TCP 127 [TCP segment of a reassembled PDU]
5 0.003967 105.103.82.47 105.103.15.106 TCP 66 8080 → 54940 [ACK] Seq=1 Ack=62 Win=14592 Len=0 TSval=3397722436 TSecr=496906306
6 0.003974 105.103.15.106 105.103.82.47 HTTP 68 CONNECT cloudformation.us-east-1.amazonaws.com:443 HTTP/1.0
7 0.006035 105.103.82.47 105.103.15.106 TCP 66 8080 → 54940 [ACK] Seq=1 Ack=64 Win=14592 Len=0 TSval=3397722438 TSecr=496906306
8 0.247802 105.103.82.47 105.103.15.106 HTTP 185 HTTP/1.0 200 Connection established
9 0.247810 105.103.15.106 105.103.82.47 TCP 66 54940 → 8080 [ACK] Seq=64 Ack=120 Win=29312 Len=0 TSval=496906367 TSecr=3397722681
10 0.248938 105.103.15.106 105.103.82.47 TLSv1.2 583 Client Hello
11 0.250985 105.103.82.47 105.103.15.106 TCP 66 8080 → 54940 [ACK] Seq=120 Ack=581 Win=15616 Len=0 TSval=3397722683 TSecr=496906367
12 0.684003 105.103.82.47 105.103.15.106 TLSv1.2 1995 Server Hello
13 0.684011 105.103.15.106 105.103.82.47 TCP 66 54940 → 8080 [ACK] Seq=581 Ack=2049 Win=33152 Len=0 TSval=496906476 TSecr=3397723117
14 0.690001 105.103.82.47 105.103.15.106 TLSv1.2 1488 CertificateServer Key Exchange, Server Hello Done
15 0.690866 105.103.15.106 105.103.82.47 TLSv1.2 216 Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message
16 0.692974 105.103.82.47 105.103.15.106 TCP 66 8080 → 54940 [ACK] Seq=3471 Ack=731 Win=16640 Len=0 TSval=3397723125 TSecr=496906478
17 0.968807 105.103.82.47 105.103.15.106 TLSv1.2 141 Change Cipher Spec, Encrypted Handshake Message
18 0.969476 105.103.15.106 105.103.82.47 TLSv1.2 679 Application Data
19 0.970992 105.103.82.47 105.103.15.106 TCP 66 8080 → 54940 [ACK] Seq=3546 Ack=1344 Win=17920 Len=0 TSval=3397723403 TSecr=496906547
20 1.319977 105.103.82.47 105.103.15.106 TLSv1.2 617 Application Data
21 1.324998 105.103.82.47 105.103.15.106 TCP 2114 [TCP segment of a reassembled PDU]
22 1.325003 105.103.15.106 105.103.82.47 TCP 66 54940 → 8080 [ACK] Seq=1344 Ack=6145 Win=43008 Len=0 TSval=496906636 TSecr=3397723753
23 1.329979 105.103.82.47 105.103.15.106 TLSv1.2 133 Application Data
24 1.332987 105.103.15.106 105.103.82.47 TCP 66 54940 → 8080 [FIN, ACK] Seq=1344 Ack=6212 Win=43008 Len=0 TSval=496906638 TSecr=3397723763
25 1.373825 105.103.82.47 105.103.15.106 TCP 66 8080 → 54940 [ACK] Seq=6212 Ack=1345 Win=17920 Len=0 TSval=3397723807 TSecr=496906638
26 1.606041 105.103.82.47 105.103.15.106 TLSv1.2 119 Encrypted Alert
27 1.606063 105.103.15.106 105.103.82.47 TCP 54 54940 → 8080 [RST] Seq=1345 Win=0 Len=0
请注意，1到3的数据包是三次握手，与JS SDK完全相同，数据包4类似于JS SDK的数据包5，它没有在摘要中显示，但它也有PSH标志和ACK，差异是内容（预期）和数据包5是该数据的代理ACK。从这一点来看，事情是不同的，aws CLI一旦ACK到达数据包6就发送下一个数据包。收到数据后，aws CLI发送FIN，接收ACK，加密警报并发送RST（这是由于加密警报没有预料到。）
我无法找到为什么JS SDK在上次服务器确认后停止发送数据。但由于代理超时并在一段时间后发送FIN ACK，我的节点脚本似乎会挂起很长时间，直到中止，错误如下：
{ NetworkingError: socket hang up
at TLSSocket.onHangUp (_tls_wrap.js:1124:19)
at TLSSocket.g (events.js:292:16)
at emitNone (events.js:91:20)
at TLSSocket.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)
消息：'socket hang up'， 代码：'NetworkingError'， 地区：'us-west-2'， 主机名：'bucket.s3-us-west-2.amazonaws.com'， 可重试的：是的， 时间：2017-07-07T19：31：29.494Z} null
有任何线索吗？
答案 0 :(得分：3)
查看输出，CLI连接使用CONNECT（HTTP隧道），如here所述，而NodeJS SDK调用似乎没有这样做。似乎带有CONNECT类型代理的NodeJS SDK有点奇怪。我建议查看使用bug on it提及的node-tunnel给出类似的内容：
var AWS = require('aws-sdk');
var tunnel = require('tunnel');
var tunnelingAgent = tunnel.httpsOverHttp({
proxy: { // Proxy settings
host: 'proxyhost',
port: 8080,
proxyAuth: "user:pass",
}
});
AWS.config.update({
httpOptions: {
agent: tunnelingAgent
}
});
var s3 = new AWS.S3({region: 'us-west-2'});
s3.getObject({Bucket: 'bucket', Key: 'key'}, function (err, data) {
console.log(err, data);
});
虽然我遗憾的是没有环境设置来测试这个，但我希望它至少可以帮助您开始解决问题。