Release: Amazon DevPay on 2010-02-22

Release Notes>DevPay>Release: Amazon DevPay on 2010 02 22
Updates for the new Amazon EC2 High-Memory Extra Large instance type.

Details

Submitted By: cheriaws
Release Date: February 22, 2010 12:00 AM GMT
Created On: February 22, 2010 4:36 PM GMT
Last Updated: February 23, 2010 5:09 AM GMT

New Features

FeatureDescription
New Amazon EC2 High-Memory Extra Large Instance Type On February 22, 2010, Amazon EC2 added an extra large instance to the family of High-Memory instance types (m2.xlarge). For more information about the new instance type, see the Amazon EC2 product page.

You can enable your customers to use this new instance type by changing your product's configuration and setting a price for the new instance type. For more information about product configuration, go to Your Product's Configuration and Price in the Amazon DevPay Developer Guide. Depending on the type of price change you do for your product (passive or active), you may be required to give your customers at least 14 calendar days' notice. For more information about changing your product's price, go to Changing Pricing.

Known Issues

IssueDescription
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 http://www.amazon.com/dp-applications).
  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 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.
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.
©2014, Amazon Web Services, Inc. or its affiliates. All rights reserved.