Support assigning public IP to Amazon EC2 host
When creating a new host on an amazon compute resource and choosing for the "Managed IP" Public, no real IP is assigned to the machine.
We are using VPCs and not EC2.
We have a "nat" role that should also use some awscli commands in order to configure itself. Because no real IP is assigned, those commands timeout and fail, so we need to manually add an IP and rerun puppet.
I didn't see anything relevant in the logs, so please let me know if you want anything from our side regarding this.
#1 Updated by Dominic Cleal over 7 years ago
- Category set to Compute resources
It's worth noting that the "Managed IP" is about which IP Foreman picks to try and contact the new VM on, rather than having any impact on how the VM is created and which IP it's allocated. I'm not sure how the latter works.
#2 Updated by cristian falcas over 7 years ago
I was thinking about this feature more:
Thank you for your response, please close this issue then.