|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
Amazon DevPay is a billing and account management service that enables you to get paid for products you build on either Amazon EC2 or the Amazon Simple Storage Service. Amazon DevPay creates and manages the order pipeline and billing system for you. Your customers sign up for your product, and we automatically meter their usage of the underlying AWS service, bill them based on the pricing you set, and collect their payments. What else is special about DevPay?
You can charge customers for your product; the charges can include recurring charges based on the customer's usage of AWS services (Amazon EC2 or Amazon S3), a fixed one-time charge, and a recurring monthly charge.
Your customers can easily sign up and pay for your product with their trusted Amazon.com accounts; they do not need to sign up for an AWS developer account.
Your customers are authenticated, thus ensuring they have access only to what they should.
If your customers don't pay their bills, DevPay turns off their access to your product for you.
Amazon Payments handles ALL payment processing.
Basic DevPay Flow
Your customer uses an Amazon.com account to sign up and pay for your product. The sign-up page indicates that you have teamed up with Amazon Payments to make billing easy and secure.
Your customer pays the price you've defined to use your product.
DevPay subtracts a fixed transaction fee and pays you the difference.
You pay the costs of the AWS services your product consumed, and a percentage-based DevPay fee.
You can use DevPay with Amazon EC2 or Amazon S3.
The most popular way to use Amazon EC2 and Amazon DevPay together is by selling an AMI you've created to other Amazon EC2 users.
An AMI that you sell through DevPay is called a paid AMI. Essentially you register a product with DevPay, receive a DevPay product code, and associate that product code with one or more of your AMIs (making them paid AMIs). Customers who buy your product launch instances of your paid AMIs (you don't launch instances on their behalf). When they do, they're charged the rates you've set, and not the normal Amazon EC2 rates.
The other way to use Amazon EC2 and Amazon DevPay together is with a supported AMI. With a supported AMI, you charge for software or a service you provide that other Amazon EC2 users use with their own AMIs. In this case, you register a product with DevPay, receive a DevPay product code, and the customers who buy your product associate the product code with their own AMIs. The AMIs must be Amazon S3-backed and not Amazon EBS-backed. When your customers launch instances of their AMIs, they're charged the rates you've set, and not the normal Amazon EC2 rates.
With the current implementation of Amazon DevPay:
Your paid or supported AMIs must be backed by Amazon S3. Paid or supported AMIs backed by Amazon Elastic Block Store are currently not supported. Therefore, your paid AMIs cannot run Windows 2008 Server or SQL Server 2008 at this time.
You can't use Elastic Load Balancing (either by itself or in conjunction with Auto Scaling) with instances of paid or supported AMIs.
The discounts from Amazon EC2 Reserved Instances don't apply to paid or supported AMIs. That is, if you purchase Reserved Instances, you don't get the lower usage price associated with them when your customers launch your paid or supported AMIs. Also, if your customers purchase Reserved Instances, and they use your paid or supported AMIs, they continue to pay the price you specified for the use of your paid or supported AMIs.
Your customers can't make Spot Instance requests for your paid or supported AMIs; if they do, Amazon EC2 returns an error.
For more information about any of the preceding Amazon EC2 features, go to the Amazon EC2 product page.
For complete information about how paid AMIs and supported AMIs work, go to Using DevPay with Your Amazon EC2 AMI in the Amazon DevPay Developer Guide.
You can use Amazon DevPay with either a desktop product or a hosted (web) product that uses Amazon S3. To use your Amazon S3 product with DevPay:
Your product must use the REST interface when calling Amazon S3 (web products may also use pre-signed URLs that customers use directly in a browser). SOAP is not supported.
Your product must create a separate bucket in Amazon S3 for each customer who buys and uses the product. This is true even if your DevPay product is a web product. Each DevPay product can create up to 100 buckets per customer. For example, a customer who uses three different DevPay products can have up to 300 DevPay buckets, plus any other buckets created outside of DevPay (i.e., those created with a personal AWS account).
Once your product has created a bucket and put objects in it, only your product can access that bucket and the objects in it. For more information about restrictions on data access, go to the section on data access in the Amazon DevPay Developer Guide.
To use your product, your customers don't have to be signed up for Amazon S3. They don't need to obtain AWS credentials (like a Secret Access Key or Access Key ID); you obtain the credentials that DevPay requires and use them on your customers' behalf. Customers pay the rates you've set for your product, and not the normal Amazon S3 rates. It's your choice whether you let your customers know that the product uses Amazon S3.
When the customer uses the product, the product makes calls to Amazon S3 to store and manage objects on the customer's behalf. Therefore, the product must provide particular product and customer identifiers in the call so the correct customer can be billed. This guide covers what desktop and web products must do to meet those basic requirements (for more information, see Amazon S3 Example). For complete information about Amazon S3 DevPay products, go to Using DevPay with Your Amazon S3 Product in the Amazon DevPay Developer Guide.
3% of your value-add per customer
$0.30 per DevPay product for each customer bill we collect
Your value-add per customer is the amount you charge each customer on top of the cost of the AWS services they used.
When we calculate the 3% fee amount, we use the value-add amount before any $0.30 DevPay fees have been subtracted.
Complete details about the fees, how they're collected, and how you get paid are covered in the Amazon DevPay Developer Guide.