Release: Amazon DevPay on 2009-05-18

Release Notes>DevPay>Release: Amazon DevPay on 2009 05 18
Updates regarding new Amazon EC2 features.

Details

Submitted By: cheriaws
Release Date: May 18, 2009 12:00 AM GMT
Created On: May 18, 2009 12:03 AM GMT
Last Updated: May 20, 2009 8:23 PM GMT

New Features

FeatureDescription
Elastic Load Balancing, Auto Scaling, and Amazon CloudWatch On May 18, 2009, AWS announced the release of new features for Amazon EC2: Elastic Load Balancing, Auto Scaling, and Amazon CloudWatch.

Currently, Elastic Load Balancing (by itself or in conjunction with Auto Scaling) is not available for use with instances of paid or supported AMIs. Auto Scaling and Amazon CloudWatch are available for use; however, you can't charge your customers for their use of the new features. Why not?

Like with Elastic IP addresses and Amazon EBS, use of Auto Scaling or Amazon CloudWatch is associated with the account of the user who launches the instances, not the instance itself or the owner of the AMI. Users can use Auto Scaling or Amazon CloudWatch with any instance they launch (Auto Scaling itself launches instances on behalf of the user). The instance can be of your paid AMI, someone else's paid AMI, or their own AMIs. Because of this, AWS always bills the Amazon EC2 users directly for Auto Scaling or Amazon CloudWatch. You are also not able to include charges for the features in the pricing for your paid or supported AMIs.

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. 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.
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.