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.

Pulumi Community

<@U03P0GFU38A>
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, <@U01FHMA71BK>.  Yeah, I found the root cause, there is `id`  and also `vpc_id`  in the output, the description of `id` is:
&gt; The provider-assigned unique ID for this managed resource.
What is that?

I’m looking at <https://www.pulumi.com/registry/packages/awsx/api-docs/ec2/vpc/#vpc_id_python>

<@U03P0GFU38A> 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?

e.g. is there a way to print the raw http request body?

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

another suggestion, is maybe you can use AWS Native than AWS Classic or another provider for AWS. Native providers can give you full coverage for your infrastructure as code but keep in mind that it is in the preview version: <https://www.pulumi.com/registry/packages/aws-native/>