Making money with Amazon DevPay: Getting Started

One thing that differentiates AWS is how money is figured out neatly. Recently I was getting my hands dirty with AWS DevPay to learn how the premium EC2 AMIs really work. Before that, if you wish to use DevPay, you need an invitation to the limited beta. You also need a US bank account to make use of the service.

Once you have signed up for DevPay, You will be able to register your offering( Called Product) through the ‘Your Web Services Account’ drop down at

DevPay Sign up

After collecting basic details about the Product, you will be allowed to set pricing. Once you confirm all the details, the product will be given a Product Code( 9E6D5AB5 in my Product’s case) and a purchase URL( It takes 2-3 biz days to get the manual approval of the product. If there are DevPay signup issues like Bank account and such, it will get delayed further.

Now this product code is to be incorporated into the EC2 AMI to make it a premium AMI. Just build your AMI with your offering the usual way you build an ordinary AMI. Incorporate the Product Code from DevPay product registration using

ec2-describe-image-attribute <ami-id> -p <product-code>

Now verify the product code associated with the AMI using:

ec2-describe-images <ami-id>

Now if the product code is set, the AMI has become premium AMI. It can be run only by EC2 account holders that has signed up for the product code.

In the next blog post, I’ll describe the small app I cooked up using opensource software. The pain point I’m solving is keeping up with rapidly changing opensource project. Opensim being the case in point.


About labsji

I blog, Therefore I exist ! Funny things are funny to me. Cool things are cool to me. Innovations tick me. I attempt spirituality religiously :)
This entry was posted in amazon ec2 and friends, Amazon Web Service, Entrepreneurship, Idea Factory, micropayment and tagged , , . Bookmark the permalink.

5 Responses to Making money with Amazon DevPay: Getting Started

  1. Patricia Gallery says:

    since DevPay does not collect taxes, is it a viable solution for large scale applications? we can’t see how it scales given the responsbility is on the partner to collect taxes.

    what are other large ISV’s doing?

  2. labsji says:

    Tax collection is just one of many issues with DevPay. But the biggest advantage brought in be DevPay is metering and Trust – which are most useful for small timers.

    An interesting alternative to DevPay is AWS Consolidated Billing – It essentially metering by AWS and billing by your regular AR process. Works well if you have trust relationship with the customers( in other words you know how to collect money from them!)

    Given the complexity of Taxes and the Global nature, it is a good idea to segregate the metering and billing. [ And use industrial strength billing, invoicing, AR software/service to do it] Let me know if you have any recommendations for such billing integration.

    -Balaji S.

  3. Pyrameda says:

    Do you know if DevPay now allows users from other countries?

    And does it have to be AMI based, or can we also use it to bill our clients for services such as migration?

  4. labsji says:

    Dear @Pyrameda, DevPay is AMI based. Check if you can load the migration fee as part of the one-time initial payment.

  5. Pep says:

    When a customer deploys a DevPay AIM, can he have root access to all it internals, or can it be set to let him only start it? I’m concerned that the customer might just copy anything that’s inside the DevPay AMI.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s