Control: tags -1 + moreinfo > The buster arm64 images in us-east-2 don't seem to come online - ping and ssh > fail. The ec2 status checks pass, but take unusually long to get there. I > tried a1 and c6g instances. There's nothing in the system log output, and no > screenshots on arm64. > > I think it's the images since: > - amd64 in the same vpc, with the same security groups works correctly > - arm64 in us-west-2 & us-east-1 work correctly > > Here's the images I tried: > ami-0a5def50f0aa9c6a3 > ami-0a67a4b56b2021f1c > ami-0b1808bb4e7ed5ff5
Those all work for me. admin@ip-172-31-20-95:~$ ec2metadata --ami-id --availability-zone --instance-type ; uptime ami-0a5def50f0aa9c6a3 us-east-2b m6g.large 14:05:39 up 3 min, 2 users, load average: 0.01, 0.04, 0.01 admin@ip-172-31-27-201:~$ ec2metadata --ami-id --availability-zone --instance-type ; uptime ami-0a67a4b56b2021f1c us-east-2b a1.4xlarge 14:12:00 up 2 min, 2 users, load average: 0.17, 0.11, 0.04 admin@ip-172-31-20-102:~$ ec2metadata --ami-id --availability-zone --instance-type ; uptime ami-0b1808bb4e7ed5ff5 us-east-2b c6g.large 14:15:15 up 0 min, 2 users, load average: 0.00, 0.00, 0.00 How long have you waited before giving up on get-console-log? It can take a few minutes for data to show up, but I was able to retrieve logs for the above instances after about 5 minutes. noah