Bug#1043304: Latest Debian 12 AMI will not allocate a public IP at creation time
Control: tags -1 moreinfo
Hi Tom,
> I created an EC2 instance in us-east-1 using the command line below. The
> instance does not have a public IP, although I requested one. It is not
> possible to add a public IP after creation time, except for elastic IPs,
> which carry additional cost.
I tried to reproduce, and was not able to. Using the same AMI as you, as well
as the latest build (ami-0cb7a724e5bafff67 in us-west-2), the instance was
assigned a public IP.
The initial response to run-instances does not include a PublicIpAddress, but
it is there a describe-instances response within a few seconds. I observed the
same behavior when I laucnhed Ubuntu 22.04 from i-0f0d0cdaa7102be65 in
us-west-2.
Do you see a public ip if you describe the new instance after creation?
Thanks,
Ross
Reply to: