I wanted to create a custom AMI for use with Elastic Beanstalk. Up until now I have been logging on to my instance by using the key pair to retrieve the Windows Password.
I launched a new instance specifically for customising to use as a custom AMI. I went to the EC2 page on AWS, clicked 'Launch Instance' and chose the public image
ami-9f1c4bfa. I chose this public image because it was the default instance in my Elastic Beanstalk setup. I also chose the same key pair that I have been using with my Elastic Beanstalk instances.
After I applied the settings that I wanted to my new instance, I went back to the EC2 list to create an image of it (a custom AMI).
Once that had saved, I then entered my AMI name within Elastic Beanstalk.
My EC2 instance had been recreated, but I could no longer use the key pair to get the Windows password.
Is it something I've done when creating the instance that causes this, or are there additional steps that I need to allow a key pair to be used?