This message was deleted.

@jolly-plumber-1488 I’m not sure exactly but looks like your ‘vpc.id’ is empty or is not the same VPC used by your ‘*_subnets_ids’. I suggest you create the VPC in another function before, collect ids from this process and add in your function to create the EKS. Using this approach your infrastructure will create not only the EKS but everything that is necessary to create EKS. If you want to delete this stack you will delete not only EKS but the VPC that EKS was created. for example: https://github.com/pulumi/examples/blob/master/aws-py-eks/__main__.py#L15

Thanks for your reply, @mammoth-electrician-64525. Yeah, I found the root cause, there is

id

and also

vpc_id

in the output, the description of

id

is:

The provider-assigned unique ID for this managed resource.

What is that?

@jolly-plumber-1488 this is the description about id output, as a default description(https://www.pulumi.com/registry/packages/aws-iam/api-docs/provider/)

BTW, is there any suggestion about how to debug issues like this, besides printing logs?

I believe that verbose logging can help you a bit: https://www.pulumi.com/docs/support/troubleshooting/#verbose-logging

Thanks a lot, @mammoth-electrician-64525