Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
a
adamant-honey-71910
07/02/2022, 5:24 PMI 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
associatePublicIpAddressconst web = new aws.ec2.Instance('my-instance', {
ami: recentAmazonLinuxAmi().id,
instanceType: 't4g.nano',
associatePublicIpAddress: false,
});b
billowy-army-68599
07/02/2022, 6:37 PMIt's set to true in the state? Which subnet are you using, if the subnet is public that takes precedence
a
adamant-honey-71910
07/04/2022, 2:47 PMOh 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.