Release: Amazon DevPay on 2009-12-02

Release Notes>DevPay>Release: Amazon DevPay on 2009 12 02
Updates regarding the new US-West (Northern California) Region and Amazon EBS-backed AMIs.


Submitted By: cheriaws
Release Date: December 2, 2009 12:00 AM GMT
Created On: November 30, 2009 5:37 PM GMT
Last Updated: December 3, 2009 10:06 AM GMT

New Features

New US-West (Northern California) Region On December 2, 2009, AWS announced the new US-West (Northern California) Region. For more information about the Region, go to the Amazon EC2 product page or the Amazon S3 product page.

Effect on Existing Amazon EC2 Paid AMIs

Your existing paid or supported AMIs are not affected. They will continue to operate as usual in the existing Regions and will not automatically work in the new Northern California Region. If you want to expand your Amazon DevPay product to cover paid AMIs in the Northern California Region, 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 paid AMIs in the Northern California Region. 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 paid AMI in the Northern California Region, be aware that you need to create a separate version of your paid AMI to upload to Amazon S3 in that Region. The basic process is as follows:

  1. Create your Amazon S3 bucket in the Northern California Region if you haven't already.
  2. Copy your AMI from your Amazon S3 bucket in another Region to your bucket in the Northern California Region (using the ec2-migrate-image command, which is part of the EC2 AMI tools).
  3. Register the AMI (using the ec2-register command).
  4. Confirm that your DevPay product code is attached to the Northern California Region AMI (using the ec2-describe-images command). If it's not, associate the product code with the AMI (using ec2-modify-image-attribute command).

Effect on Existing Amazon S3 Applications

Your existing Amazon S3 applications are not affected. They will continue to operate as they have in the existing Regions. If you want to expand your application to use Amazon S3 in the Northern California Region, you should:

  • Update your application to enable interaction with Amazon S3 in the Northern California Region (for information about using different Regions in Amazon S3, refer to the Amazon S3 documentation)
  • Update your product's price to include prices for the Northern California Region (for more information, go to Changing Pricing) in the Amazon DevPay Developer Guide
  • Make the newly updated application available to customers only after your price change has taken effect; this ensures you get paid for your customers' use of the new Amazon S3 Region
Amazon Instances Backed by an Amazon EBS Volume On December 2, 2009, Amazon EC2 announced the ability to launch instances with an Amazon EBS root device. Amazon DevPay currently does not support this feature, which means you cannot sell paid AMIs backed by Amazon EBS and you will be unable to attach product codes to those AMIs.

As with any type of Linux/UNIX AMI, if you give customers root access, they could rebundle the AMI without the product code or make an Amazon EBS-backed version of it, but without the product code. For Windows AMIs, the product code can't be removed from the AMI, even if someone rebundles the AMI.

Known Issues

Failure of Sign-Up Payment If your product has a sign-up/monthly fee, and the customer's sign-up payment fails because the payment method isn't valid, the customer is not officially subscribed to your product. This can be verified with VerifyProductSubscriptionByTokens (for desktop products) or VerifyProductSubscriptionByPid (for hosted products), which returns a value of "false". The customer can't use the product, even if you've activated the customer. We recommend your product poll the customer's subscription status after activating the customer. If the status is still "false" 15 minutes after activation, then the product should display a special message when the customer tries to use the product the first time. The message should tell the customer to:
  1. Cancel the subscription by going to the Application Billing page (at
  2. Update the payment method (also at the Application Billing page).
  3. Resubscribe to the product with the valid payment method (by clicking the purchase URL).
Error in WSDL The License Service WSDL (at 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.
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. If this happens, 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.
©2017, Amazon Web Services, Inc. or its affiliates. All rights reserved.