Release: Amazon DevPay on 2009-02-09

Release Notes>Release: Amazon DevPay on 2009 02 09
Updates for support of Amazon EC2 Windows AMIs in the U.S. and Linux/UNIX AMIs in Europe.

Details

Submitted By: T. Johnson
Release Date: February 9, 2009 12:00 AM GMT
Created On: February 6, 2009 9:49 PM GMT
Last Updated: February 9, 2009 11:34 PM GMT

New Features

FeatureDescription
Support for Windows AMIs in the U.S. and Linux/UNIX AMIs in Europe

With this release, Amazon DevPay now supports Windows paid AMIs in the U.S. and Linux/UNIX paid AMIs in Europe.

What does this mean for your existing paid or supported AMIs and DevPay products?

Your existing Linux/UNIX paid or supported AMIs are not affected. They will continue to operate as usual on Linux/UNIX in the United States. If you want to expand your Amazon DevPay product to cover Windows paid AMIs in the U.S. or Linux/UNIX 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 the U.S. or Linux/UNIX AMIs in Europe. For more information, see the next item in this table.

If you decide to use Amazon DevPay to sell a Windows paid AMI, be aware 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. Note that Amazon EC2 currently does not support Windows AMIs in Europe.

If you decide to use Amazon DevPay to sell an AMI in a region other than the U.S. (e.g., Europe), be aware that you need to create a separate version of your AMI to upload to Amazon S3 in that region. The basic process is as follows:

  1. Create your Amazon S3 bucket in Europe if you haven't already.
  2. Copy your AMI from your Amazon S3 bucket in the U.S. to your bucket in Europe using the ec2-migrate-bundle command (part of the Amazon EC2 AMI tools).
  3. Register the AMI using the Amazon EC2 RegisterImage API.
  4. If the DevPay product code is not bundled into the manifest of your AMI, reassociate the product code with the AMI in Europe using the Amazon EC2 ModifyImageAttribute API.

For more information about setting up AMIs in different regions, go to Feature Guide: Amazon EC2 Regions.

DevPay Product Configuration (for Amazon EC2 AMIs)

With this release, you can now select which Amazon EC2 regions, environments (Linux/UNIX, Windows), or instance types your product supports. For example, you could configure a DevPay product to work only with specific types of Windows instances, or Europe AMI instances. AWS allows your customers to launch only the instance types the product is configured for. The details are discussed in Your Product's Configuration and Price in the Amazon DevPay Developer Guide.

When you configure a new product (as part of product registration or as part of a price change), you select which regions, environments, etc., you want the product to support. You also provide prices for those supported regions, environments, etc. In the paid AMI scenario, you then associate the product code with AMIs that match the product's configuration, and you make those AMIs available for sale. When you associate the product code with the AMI, we do a preliminary check to confirm the AMI matches the product's configuration. At launch time, we do a complete check to confirm the instance matches the product's configuration. As the product owner, you're allowed to associate the product code with an AMI that doesn't match the product's configuration, but no one (including you) can launch an instance that doesn't match a product's configuration.

In the supported AMI scenario (where you let your customers associate your product code with their AMIs), this new product configuration feature prevents your customers from using your product code with AMIs or instance types the product doesn't support. For example, if your product is designed only for Windows AMIs, then you only want your customers to associate your product code with Windows AMIs. We do a preliminary check when the your customer associates the product code with the AMI, and then a complete check when anyone launches an instance of the AMI.

At any time, you can update a product's configuration to either add or remove support for different AMI types or instance types. For example, any DevPay product you registered before this release is automatically configured only for Linux/UNIX AMIs in the United States. However, you could update the product to also support Windows AMIs in the U.S. or Linux/UNIX AMIs in Europe, or to no longer support certain instance types. For more information, go to 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 in the Amazon DevPay Developer Guide.

Known Issues

IssueDescription
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.
©2014, Amazon Web Services, Inc. or its affiliates. All rights reserved.