Release: Amazon DevPay on 2009-03-03
New Features
| Feature | Description |
|---|---|
| Support for Windows paid AMIs in Europe | On March 3, 2009, Amazon EC2 announced the release of Amazon EC2 instances with Microsoft Windows Server in Europe. Correspondingly, Amazon DevPay now supports Windows paid AMIs in Europe. Keep in mind that to sell paid AMIs through Amazon DevPay, you must be based in the United States. What does this new Amazon EC2 release mean for your existing paid or supported AMIs and DevPay products? Your existing paid or supported AMIs are not affected. They will continue to operate as usual. If you want to expand your Amazon DevPay product to cover Windows paid AMIs in Europe, then you need to update the product's configuration and set prices for those instance types. Until you do that, your customers will not be able to launch instances of your Windows paid AMIs in Europe. For more information, go to Your Product's Configuration and Price and Changing a Product's Configuration in the Amazon DevPay Developer Guide. We also recommend you understand the implications of selling multiple AMI types under the same product code versus different product codes. For more information, go to Selling Multiple AMIs. If you decide to use Amazon DevPay to sell a Windows paid AMI in Europe, be aware that you need to create a separate version of your Windows AMI to upload to Amazon S3 in Europe. The basic process is as follows:
For more information about setting up AMIs in different regions, go to Feature Guide: Amazon EC2 Regions. Regarding Windows AMIs in general, keep in mind that the association of the product code with a Windows AMI is permanent. Therefore, we recommend you keep a separate, base copy of the AMI that has no product code associated with it. Also, anyone who purchases a Windows paid AMI can rebundle it, and the product code is automatically transferred to the rebundled AMI. When Amazon EC2 users launch instances of the rebundled AMI, they pay the rates you set when you registered your DevPay product. In turn, you're charged for the Amazon EC2 costs they incur. For more information about how to create and bundle Windows AMIs, go to Feature Guide: Amazon EC2 Running Windows. |
Known Issues
| Issue | Description |
|---|---|
| Error in WSDL | The License Service WSDL (at https://ls.amazonaws.com/doc/2008-04-28/AmazonLS.wsdl) incorrectly lists a child element called RequestId in the ErrorResponse element. The correct name of the element is RequestID (with a capital D). Our plan is to update the WSDL to match what the service actually returns (RequestID). |
| Limitation on AWS services used | You can build an application that monetizes Amazon EC2 or Amazon Simple Storage Service, but not both. |
| Limitation on decimal places for prices | You can set prices with a maximum of only two decimal places. |
| Throttling of License Service requests per developer | Requests to the License Service are throttled as necessary. They are throttled per developer instead of per DevPay product. Therefore, if you have multiple DevPay products, the sum of the requests from all your DevPay products is used to determine whether your requests need to be throttled. |
| Information not available on the first of the month | If you visit your DevPay Activity page on the first of the month, your revenue statement for the previous month might not yet be available. We instead recommend that you view the page after you've received the e-mail from AWS that indicates the revenue statement is available. Also, the page might display zeros for all the values because the page has not yet been updated with the information for the first day of the month. We recommend that you return to the page on the second day of the month. |
| Withdrawal limit | When you withdraw money from your Amazon Payments account, the withdrawal amount must be at least $10.00. |
| No sandbox for testing | DevPay does not have a sandbox for testing. All testing you perform involves movement of real money. |
