CentOS virt - Mar 2021 - Unable to Login to AWS AMI With SSH Key - aarch64

When launching CentOS Stream for aarch64 in us-east-1 using the CentOS-sponsored
AMI (ami-0a311be1169cd6581, found at https://wiki.centos.org/Cloud/AWS
<https://wiki.centos.org/Cloud/AWS>) I am able to launch the EC2 instance
using a Gravitron2 processor, as expected. However, when attempting to login to
that instance, I get a password prompt for the ec2-user, centos, and root users.

This behavior is not expected, because on the x86_64 AMIs the centos user is
configured to use the SSH key selected in the AWS EC2 Launch Wizard, and a SSH
login password is not required.

In the aarch64 AMI, the centos and root usernames all prompt for password, and
never seem to consider the provided SSH key.

This is the SSH command that I am using:

	ssh -i ssh_key_selected_at_launch.pem centos@<the_public_ip>

This command results in a password prompt.

What is the process for connecting to the CentOS Stream AMI spun for aarch64?

Thank you!

David Lemcoe Jr.

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos-virt/attachments/20210315/1237a0c6/attachment-0005.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1481 bytes
Desc: not available
URL:
<http://lists.centos.org/pipermail/centos-virt/attachments/20210315/1237a0c6/attachment-0005.p7s>

I have resolved my ?issue.? It would appear that CentOS 8 Stream for aarch64
does not support `t4g.nano` instance sizes. Once I moved to t4g.small, my SSH
login worked as expected.

Sorry to bother!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1481 bytes
Desc: not available
URL:
<http://lists.centos.org/pipermail/centos-virt/attachments/20210315/77b64c18/attachment-0005.p7s>