https://pulumi.com
Join Slack
This message was deleted.
# aws
s
This message was deleted.
t
I haven't used 
pulumi_eks
in a while (moved to 
pulumi_aws
) but shouldn't the URL above be in this format ? 
<https://oidc.eks.ap-northeast-3.amazonaws.com/id/><id>
or you redacted the value ?
p
no, this is just the pulumi output
the stack export has the right urls and ids
trying to add some debugging code
Copy code
Error [ERR_SOCKET_CONNECTION_TIMEOUT]: Socket connection timeout
        at new NodeError (node:internal/errors:399:5)
        at internalConnectMultiple (node:net:1099:20)
        at Timeout.internalConnectMultipleTimeout (node:net:1638:3)
        at listOnTimeout (node:internal/timers:575:11)
        at processTimers (node:internal/timers:514:7) {
      code: 'ERR_SOCKET_CONNECTION_TIMEOUT'
    }
t
I see, you're onto something here. Private Endpoint maybe ?
p
no, nothing, and i can curl the full url with id from my computer (403 error but no connection issue)
ok, i accidentally switched to node 20, switched to 18 and it works now
t
sorry, you mean Node js
🙂
p
😉 not sure what changed in node 20 to cause this
t
good luck! I gave 
pulumi_eks
a try last year and ended up using plain 
pulumi_aws
so in the case above I would run 
pulumi_tls
to get the fingerprint.
p
don't actually need node 20, was messign with my zsh config and my aliasses were gone
g
asdf
is your friend!
p
trying out volta now, also looks cool
42 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by