Assigning a public IP directly to an instance is simpler than using a floating IP (e.g. elastic IPs in AWS have stringent limits).
On AWS it seems like we can launch an instance with a public IP simply by setting a flag in thenetwork section of "create_instances" boto call. I'm not sure if GCP or Azure have similar flags but it would be useful to be able to pass in this flag either directly in the InstanceService.create() function or via a kwarg that's passed through by the AWS implementation (and maybe the others). This is done for e.g. the iam_instance_profile now. Is there a reason not to do this or would there be a better way to do it?
Assigning a public IP directly to an instance is simpler than using a floating IP (e.g. elastic IPs in AWS have stringent limits).
On AWS it seems like we can launch an instance with a public IP simply by setting a flag in thenetwork section of "create_instances" boto call. I'm not sure if GCP or Azure have similar flags but it would be useful to be able to pass in this flag either directly in the InstanceService.create() function or via a kwarg that's passed through by the AWS implementation (and maybe the others). This is done for e.g. the iam_instance_profile now. Is there a reason not to do this or would there be a better way to do it?