araravicha
commented
10 months ago It is coconfirmed as an issue with Node.js not forwrding the env variable aws_ca-bundle to a sub process. If for that step we set https-proxy variable that step works but we get erros in the immediatley following steps because the proxy terminates the request before the handshake. SO remove the proxy and then the rest of the stuff works. The work around is clunky but will do fo rnow but the issue needs to be fixed within node.
pahud
github-actions[bot]
Describe the bug
executing the bootstrapping command in the provided examples npx ts-node infrastructure/src/bootstrap.tx results in unable to get local issuer certificate. I am trying this command form a windows powersheli. I am in the corporate network that uses Zscaler. IS there a way to determine what site is the command reaching out to? The eero happens after it gets the progule for the toolchain account. The error message is very cryptic and does not provide any indication of the destination it is trying to reach. Here is the error message: npx ts-node infrastructure/src/bootstrap.ts √ Select AWS profile for 'toolchain' account » toolchain Error: unable to get local issuer certificate at TLSSocket.onConnectSecure (node:_tls_wrap:1550:34) at TLSSocket.emit (node:events:514:28) at TLSSocket.emit (node:domain:489:12) at TLSSocket._finishInit (node:_tls_wrap:967:8) at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:743:12) { code: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY', '$metadata': { attempts: 1, totalRetryDelay: 0 }
Expected Behavior
It should have bootstrapped the toolchain account
Current Behavior
npx ts-node infrastructure/src/bootstrap.ts √ Select AWS profile for 'toolchain' account » toolchain Error: unable to get local issuer certificate at TLSSocket.onConnectSecure (node:_tls_wrap:1550:34) at TLSSocket.emit (node:events:514:28) at TLSSocket.emit (node:domain:489:12) at TLSSocket._finishInit (node:_tls_wrap:967:8) at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:743:12) { code: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY', '$metadata': { attempts: 1, totalRetryDelay: 0 }
Reproduction Steps
You need to be on a WIndows 10 environemnt on a corproate network using Zscaler (self signed certificates)
Possible Solution
Need to determine the destination being accessed so that the certificate for that location along with Zscaler root certificate can be provisioned and the location of the certificate provided to the software (aws-CDK?) can be specified
Additional Information/Context
Nothing else
CDK CLI Version
2.113
Framework Version
No response
Node.js Version
18.17.1
OS
Windows 10
Language
TypeScript
Language Version
10.9.2
Other information
No response