CDK 2.x deploy fails with "Client network socket disconnected before secure TLS connection was established" when behind corporate network

0

CDK version 2.x deploy fails with "Client network socket disconnected before secure TLS connection was established" when behind corporate network. Even if it works properly behind my network that has direct access to the internet, when using CDK via the corporate network I'm consistently getting the above error and deployment doesn't continue. I can try raising a case to our corporate IT but want to understand first why is this happening.

asked 10 months ago239 views
1 Answer
0

Unfortunately it's going to be very difficult to tell at a glance what is going on here. All the error really tells us is that CDK was unable to connect to a server.

The good news is that your CDK environment seems to be configured okay, since you have success with it outside of your corporate network.

The corporate network could be requiring connections to go through a proxy server, or may otherwise have security rules in place that are preventing this connection. If you are aware of a proxy server that needs to be used for outbound connections, you may need to set the http_proxy and/or https_proxy environment variables so that CLI tools (such as CDK) will connect through that proxy instead of directly.

You may also want to try adding the --verbose flag to your CDK commands in order to get more output leading up to the error, such as what hostname CDK is trying to connect to when it encounters this issue, and this detail may be useful to your corporate IT if you need their assistance.

SUPPORT ENGINEER
Wayne_G
answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions