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
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.
Deploy step in pipeline build fails with access deniedasked a year ago
deploy new cdk Aurora ClusterAccepted Answerasked 6 months ago
Obtain client IP address through a network load balancer (TCP socket server, Python)asked 5 months ago
Client IP Preservation for Network Load Balancer endpoints for Global Acceleratorasked 10 months ago
FreeRTOS MQTT not connecting with Mi-Fi routerasked 10 months ago
Greengrass V2 behind Network Proxy - Failed to negotiate version with cloudAccepted Answerasked 2 years ago
CDK 2.x deploy fails with "Client network socket disconnected before secure TLS connection was established" when behind corporate networkasked 10 months ago
Network Load Balancer stickiness seems to fail sometimesasked 9 months ago
pinned lambda blocking on socket connectionasked 3 years ago
Why won't the CDK let me divide my network?Accepted Answerasked a year ago