| « PreviousNext » | |
![]() ![]() | Did this page help you? Yes | No | Tell us about it... |
This section includes several questions commonly asked by Amazon EC2 developers about paid AMIs.
Q: | Can I sell an AMI that uses an Amazon EBS root device through Amazon DevPay? |
A: | No, the AMI must have an instance store root device (must be Amazon S3-backed). |
Q: | How can Amazon EC2 users determine if a particular AMI is a paid AMI? |
A: | By describing the image ( |
Q: | How can Amazon EC2 users determine what paid AMIs are available? |
A: | By describing images ( |
Q: | Is there anything that prevents a paid AMI from being rebundled? How can this be restricted? |
A: | For Linux/UNIX AMIs: Paid AMIs are comparable to shared AMIs with regards to rebundling and trying to restrict rebundling. If you choose to allow a user running the AMI to see all of its contents (for example, by giving root access to the AMI), then the user could easily rebundle these into their own AMI. For more information, go to Protecting a Shared AMI (Linux and UNIX) in the Amazon Elastic Compute Cloud Developer Guide. For Windows AMIs: Users can rebundle Windows paid AMIs; you can't restrict this. |
Q: | Will the product code be inherited by the rebundled AMI? |
A: | For Linux/UNIX AMIs: If your customer uses AWS tools to rebundle the AMI, the product code associated with the AMI is inherited by the rebundled AMI. When launching the rebundled AMI, the customer is still billed for usage based on your price. Note that the inheritance of the product code during rebundling is a convenience feature and not a guarantee that the product code will always be attached to rebundled AMIs. The customer's workflow could bundle the AMI outside of Amazon EC2, or the customer could use modified versions of the AWS tools, preventing the product code from being inherited. You can include software on the AMI that checks the instance's metadata to determine if the product code is associated with the instance. For more information, see Getting the Product Code from Within an Instance. For Windows AMIs: The product code associated with the AMI is always inherited by the rebundled AMI. Therefore, AWS bills any customers who use instances of the rebundled AMI based on the original product code. |
Q: | Will the kernel/RAM disk be inherited by the rebundled AMI? |
A: | If the AMI is rebundled on an instance that is running with a certain kernel/RAM disk, then the kernel/RAM disk will be inherited by the rebundled AMI. Note that this is a convenience feature, and not a guarantee that the kernel/RAM disk will always be attached to rebundled AMIs. |
Q: | Why can't I query a particular AMI's attributes to see if the AMI is paid? |
A: | Only the owner of an AMI can query the AMI attributes. However, anyone can tell if an
AMI is paid by describing images ( |
Q: | Who can use the |
A: | Only the owner of the AMI can use this command. Owners use this command with supported AMIs to determine if a supported instance with a given product code attached is up and running. |
Q: | I created my paid AMIs with one AWS developer account, but I want to sell them using a different AWS developer account. Can I transfer them? |
A: | No, you can't automatically transfer AMIs from one account to another. You would have to
upload them again using the second AWS developer account and then register them with
DevPay using that account. Alternately, you could leave the AMIs with the original account
(the AMI owner account) and register them with DevPay using another AWS developer account
(the product owner account). You could then use the AMI owner account to associate the
product code with the AMIs. However, keep in mind that only the product owner (and not the
AMI owner in this case) can use the |
Q: | Can my customers use Amazon EBS for persistent data storage with my paid AMI? |
A: | Your customers can use Amazon EBS volumes for persistent data storage with instances of your paid AMI, just like they can with any Amazon EC2 instances. Amazon EBS volumes are associated with the customer's account and not with an individual instance. Therefore you are not able to charge your customers for their use of Amazon EBS. AWS charges your customers directly for their use of Amazon EBS. Your customers use their credentials in the calls to create an Amazon EBS volume or to attach it to an instance (as they do when they launch an instance of your paid AMI). |
Q: | Do the discounts from Reserved Instances apply to my paid or supported AMIs? |
A: | No. The discounts from Amazon EC2 Reserved Instances don't apply to paid or supported AMIs. That is, if you purchase Reserved Instances, you don't get the lower usage price associated with them when your customers launch your paid or supported AMIs. Also, if your customers purchase Reserved Instances, and they use your paid or supported AMIs, they continue to pay the price you specified for the use of your paid or supported AMIs. |
Q: | Can customers use Spot Instances with my paid or supported AMIs? |
A: | No. If your customers make Spot Instance requests for your paid or supported AMI, Amazon EC2 returns an error. |