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

I joined a team already using Pulumi and am working to spin up a new resource. In spinning up an ec2 instance, it seems as though setting `associatePublicIpAddress` to false doesn't actually do anything and it assigns it anyway and tracks it as true. I'm new to Pulumi so I may be missing something, or maybe just be missing some odd default behavior in AWS. Code in thread.

```const web = new aws.ec2.Instance('my-instance', {
  ami: recentAmazonLinuxAmi().id,
  instanceType: 't4g.nano',
  associatePublicIpAddress: false,
});```

It's set to true in the state? Which subnet are you using, if the subnet is public that takes precedence 

Oh of course. I was trying small, incremental examples but I just charged forward and once I set all that the problem went away. That makes sense - shoulda thought of that.