Sunday, September 9, 2012

AWS Cloud Formation error with private AMI

In working with Cloud Formation, I came across an issue that had an easy resolution that I thought would be more difficult given the error:

"CREATE_FAILED AccessDenied. User doesn't have permission to call ec2:RunInstances"

It turns out the error message is a bit deceiving as the problem was that the AMI attempting to be instantiated was private so no one but the owner could create the instance.  Just needed to make this a public AMI in order for the cloud formation template to work.

2 comments:

  1. Information and accessibility are the important factors to success in the global marketplace. Windows Cloud provides global access to business applications and lowers the environmental footprint of a business.
    Windows cloud

    ReplyDelete
  2. I have experienced the same issue with trying to deploy Oracle E-Business Suite on AWS with Cloud Formation. I was following the video at http://www.youtube.com/watch?v=J7asomw97TU, named “Deploying production-ready Oracle E-Business Suite on AWS in less than 10 minutes”, and received this error.

    I looked for the AMI's used in the video, but I can't find them available for EC2.

    What were you trying to install? And how did you choose public AMI's which enabled the cloud formation template to work? In EBS's case, I tried choosing Oracle's "Oracle E-Business Suite 12.1.3 Database 64-Bit - OVM" AMI, along with "Oracle E-Business Suite 12.1.3 Application 64-Bit - OVM" AMI, but no luck.

    Any tips or suggestions?

    ReplyDelete