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

Can you try `eip.id` instead of `eip.allocation_id` ?

I did that and got this failure:
```  aws:ec2:NatGateway (nat-gateway-nat-gateway):
    error: 1 error occurred:
...
        * Error waiting for NAT Gateway (nat-023838dcdab5f147b) to become available: unexpected state 'failed', wanted target 'available'. last error: %!s(&lt;nil&gt;)```

In the AWS console for the failed NAT Gateway, the Elastic IP address section is empty. The eip allocation ID (`eip.id`) provided in pulumi was `eipalloc-09fd0295904b5b6fb`, and I've confirmed that this Eip exists.