This message was deleted Pulumi Community #aws

Join Slack

This message was deleted.

# aws

sparse-intern-71089

01/21/2022, 12:56 AM

This message was deleted.

little-cartoon-10569

01/21/2022, 1:12 AM

Yes. The property you're looking at is on the EC2 instance. It's not derived from ENIs or similar. Just set the

associatePublicIpAddress

property and EC2 will look after it for you. https://www.pulumi.com/registry/packages/aws/api-docs/ec2/instance/#associatepublicipaddress_nodejs

little-cartoon-10569

01/21/2022, 1:13 AM

Aside: are you sure you need two manually-configured ENIs like that? Normally, an EC2 instance doesn't need to specify any ENIs, and the one that EC2 creates automatically can be used for all traffic.

little-cartoon-10569

01/21/2022, 1:14 AM

If I understand what you're trying to do, you should end up with simpler code if you leave out the ENI code, and add the appropriate routes in you public subnet to allow your instances talk to the private subnet.

little-cartoon-10569

01/21/2022, 1:16 AM

Aside-aside:

associatePublicIpAddress

will create a DHCP-style public IP address (that will change when you destroy/recreate the instance). If you want a fixed public IP address, you'll want to add an elastic IP on top of the instance.

high-grass-3103

01/21/2022, 1:30 AM

Thanks for your answer. The idea is that my other nodes have ssh port open only in that private subnet. the use case is that I connect to bastion over ssh and then, using the private subnet, I connect to other hosts I couldn't use

associatePublicIpAddress

in this scenario, with two NICs attached. How do I route traffic between subnets?

high-grass-3103

01/21/2022, 9:03 PM

OK, I've figured it out. I only need one subnet and the

assignIpv6AddressOnCreation

is just a default for the option in Instance. Thank you for your help @little-cartoon-10569

👍 1

4 Views

Open in Slack

Previous Next