Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS CDK CDk-application-pipeline (module name): (short issue description) #28511

Closed
araravicha opened this issue Dec 28, 2023 · 6 comments
Closed
Labels
@aws-cdk/custom-resources Related to AWS CDK Custom Resources bug This issue is a bug. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. effort/medium Medium work item – several days of effort p2 response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.

Comments

@araravicha
Copy link

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

@araravicha araravicha added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Dec 28, 2023
@github-actions github-actions bot added the @aws-cdk/custom-resources Related to AWS CDK Custom Resources label Dec 28, 2023
@araravicha
Copy link
Author

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
Copy link
Contributor

pahud commented Jan 2, 2024

I am not sure if this issue still exists. If it does, please provide a minimal code snippets that reproduces this issue. Thanks.

@pahud pahud added p2 response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. effort/medium Medium work item – several days of effort and removed needs-triage This issue or PR still needs to be triaged. labels Jan 2, 2024
Copy link

github-actions bot commented Jan 4, 2024

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

@github-actions github-actions bot added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Jan 4, 2024
@araravicha
Copy link
Author

araravicha commented Jan 6, 2024 via email

@github-actions github-actions bot removed closing-soon This issue will automatically close in 4 days unless further comments are made. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Jan 6, 2024
@pahud
Copy link
Contributor

pahud commented Jun 3, 2024

As mentioned, please provide a minimal code snippets that reproduces this issue so we can look into this problem. Thanks.

@pahud pahud added the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Jun 3, 2024
Copy link

github-actions bot commented Jun 6, 2024

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/custom-resources Related to AWS CDK Custom Resources bug This issue is a bug. closed-for-staleness This issue was automatically closed because it hadn't received any attention in a while. effort/medium Medium work item – several days of effort p2 response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
Projects
None yet
Development

No branches or pull requests

2 participants