This message was deleted.

Only thing I can think of is that you are somehow in a different account? Are you passing explicit provider information to either of the calls? Have you passed the same configuration into both stacks for the AWS role/account to use?

I'm just using the account setup from the shell. When I do

sts get-caller-identity

it is set up properly.

You can do something like:

aws.getCallerIdentity().then(console.log)

the logged ID looks exactly right, and the vpcId I'm using looks right. Here's the code:

const vpcId = tentacleConfig.require("vpcId");
console.log("vpcId: "+vpcId);
export const vpc = awsx.ec2.Vpc.fromExistingIds("tentacle-vpc", {
  vpcId: vpcId,
});

Pretty hard to tell for sure - seems it almost has to be that somehow you are using a different account. To debug further - you could run

TF_LOG=TRACE pulumi up --debug

(and may need to pipe that output to a file as it will be quite verbose). You can then see the exact calls being made to AWS.

I see the

DescribeVpcsResponse

and it has the exact same

vpcId

that I'm using in the config... 😕