|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
During product registration (see Registering Your Product), you set up the product and its price. Specifically, you designate which regions, environments, and instance types the product covers. We call this configuring your DevPay product (don't confuse this with configuring your AMI, which is different and covered in the Amazon EC2 documentation).
You configure the product by simply selecting check boxes for the regions, environments, and instance types that you want the product to support (see the following image, which shows the interface you use to register and configure the product). In this image, the product is configured for Linux/UNIX AMIs only, in all available instance types (small, etc.). If you wanted to also sell Windows AMIs under this product (for example), you would select the corresponding check boxes and provide prices for the specific instance types you selected. For more information about changing a product's configuration, see Changing a Product's Configuration.
Associating your product code with an AMI turns it into a paid AMI that you can sell through DevPay. Letting other EC2 users associate your product code with their AMIs turns those AMIs into supported AMIs (for more information, see Supported AMIs). Only product owners can associate their product code with AMIs that don't match the product's configuration. For example, if your product is configured only for Linux/UNIX AMIs, you can still associate the product code with Windows AMIs, but other EC2 users can't.
You might associate your product code with an AMI that doesn't match the product's configuration in expectation that you will then update the product's configuration to cover that AMI.
AWS also prevents all EC2 users (including you) from launching instance types that don't match the product's configuration. For example, if you configure the product only for small instance types, no one can launch other instance sizes of the AMI. If they try, Amazon EC2 returns an error.
When you set your product's price, you can include a one-time sign-up charge, a monthly charge, data transfer charges, and hourly instance charges for the specific instance types the product is configured for. For information about setting your product's price, see How Do You Set Your Product's Price?. Remember that you're responsible for paying the Amazon EC2 costs (bandwidth and instance-hours) your customers incur when using an instance of your paid AMI, just as if you were using the AMI yourself.
You are not responsible for any costs related to your customers' use of elastic IP addresses, Amazon Elastic Block Store, Auto Scaling, or Amazon CloudWatch with your paid AMIs. For more information, see Costs You're Not Responsible For.
If you configure your product for a particular instance type, your customers can launch that instance type regardless of the price you set. You can set the price to any value, including $0.00. Setting the price to $0.00 does not prevent customers from launching that instance type; however, it prevents that instance type from appearing in your product's price. Customers could still launch that instance type and incur EC2 costs that you would be responsible for. But, because you set the price to $0.00, the customers would pay no hourly instance charges. Keep this in mind when you set the price for your product.