This message was deleted.

When running

pulumi up

are you in your

venv

in the terminal?

@witty-candle-66007 I am--I think i found the root cause. When i drill into

$HOME/.pulumi/plugins/resource-eks-v0.40.0

and read the

package-lock.json

I'm seeing the reference to

node_modules/@pulumi/aws

with a

"version": "5.4.0"

🤔

That’s for the eks package which might be based on an earlier version of aws. Are you using the eks package and you’re seeing the 5.4.0 reference in the

pulumi up

for those resources? If so, that should be ok. But if you have new resources declared in your code that reference the aws package directly (e.g.

aws.s3.Bucket

), then it should use the

pulumi-aws

provider version in your environment.

@witty-candle-66007 yes and you're 100% correct. I'm actually starting from a completely clean slate for this stack.. I actually think the versioning issue was a red herring now (however I appreciate the help!). Upgrading my

awscli

on the host actually resolved the issue i was really trying to solve lol.. I do have another problem but i'm not even sure where to begin with that one. .. effectively this: https://pulumi-community.slack.com/archives/CDE799L1M/p1653590328133189

Threw a maybe helpful suggestion onto your eks issue thread in #CDE799L1M