Can't SSH into DNAC after install script on Amazon AWS

[bmcgahan]

I have a test deployment of DNAC 2.3.7.7 on AWS that I launched through marketplace. When booting the AMI, I created an SSH key, and then was able to SSH in as maglev @ port 2222 using that key.

Next, I web browsed to DNAC @ port 9004 to run the install script, which eventually completed overnight.

Now I can HTTPS in and login as admin to the web UI, but I can no longer SSH in as maglev with the SSH key. It rejects SSH password authentication, and only is allowing public keys.

I have a feeling the install script deleted the SSH key that AWS inserted during the deployment...

Has anyone ever seen this problem before? Do I need to re-deploy and edit the SSH config before the install script runs to allow username and password auth?

This a problem because there is no CIMC to access when running DNAC on AWS...

[bmcgahan · Accepted solution]

I found a workaround by...

• converting the running instance to an AMI snapshot
• deleting the instance
• re-deploying from the AMI with the SSH key

Seems like there should be an easier way than this...