AEM clouds fail to start on Amazon

Question

AEM clouds started to fail on Amazon on 5/23/2013 with the following error message:
java.util.NoSuchElementException: could not get imageId(us-east-1/ami-2d8e4c44)
The problem is due to AMIs provided by Red Hat that had a blank root password, which lead Amazon to remove these AMIs from their public catalog.
To fix the issue, we have deployed a temporary fix as of 5/24/2013 4pm PDT, by replacing the Red Hat AMIs used by AEM clouds with the new AMIs provided by Red Hat.
With this temporary fix, AEM clouds can be started again successfully, but only when using NEW Amazon service accounts created after 5/24/2013 4pm PDT.
To create a new Amazon service account, please go to Services, click the tab 'Cloud Providers' and select Amazon.
Existing AEM clouds in Running, Paused or Stopped state are not impacted and should continue to operate as normal.
If you have existing AEM clouds running, we recommend that you follow Amazon's instructions you may have received from Amazon directly via email. See sample below.
We are also actively working on resolving the issue with a permanent fix by next week, in order to create AEM clouds successfully with all existing Amazon service accounts.
We apologize for the inconvenience and will do our best to have a permanent fix as soon as possible.
Thanks in advance for your patience and understanding.
Adobe AEM Cloud Management Team
==============================
Subject: Red Hat, Fedora, and CentOS Public AMIs Security Note [Account #*****************]
Dear Amazon EC2 Customer,
Your security is important to us.  As part of our ongoing efforts to ensure a secure computing environment, we have identified several public Third Party AMIs which had a blank root password. Specifically, certain Red Hat Enterprise Linux (RHEL) AMIs provided by Red Hat as well as some Fedora and CentOS images within the public AMI catalog and the AWS Marketplace did not lock the root password.  The EC2 best practice for AMI publishers is to lock down the root password by default.
For customers that only access their instances using the root permissions, this is not an issue. However, many customers leverage the ability to define “local” users with different passwords and different permissions within their instance in order to increase security.  Many of these customers proactively set a root password, but if you haven’t set a root password and if you’re using a RHEL AMI or another of the 3rd party AMIs configured in this way, users logged into your instance as a local user would be able to perform actions as root without additional credentials.  They would still need your EC2 credentials or local user password to log into the instance initially; however, we recommend if you’re using this functionality on Red Hat Enterprise Linux, Fedora, or CentOS AMIs, you should set a root password to prevent your local users from having root permissions.
Our records show that you have launched instances from the following AMIs in the past which may be configured in this manner.  We recommend that you validate your images are configured correctly if they are owned by you, or that you migrate to an updated version of that AMI for future launches.
us-east-1             ami-a95390c0
If your root password is not yet set or locked, you can easily do so by logging into your running instance and issuing the following command to set it:
sudo passwd
or to lock it:
sudo passwd -l root
Should you require assistance in either identifying or remediating applicable EC2 instances, please do not hesitate to contact AWS Support:
https://aws.amazon.com/support
For more information on how to use and share public AMIs in a secure manner, please see https://aws.amazon.com/articles/0155828273219400
Regards,
The Amazon Web Services Team

Answer 1

Try downloading any free app to resync your iTunes account.