Amazon DevPay
Developer Guide (API Version 2007-12-01)
« PreviousNext »
View the PDF for this guide.Go to the AWS Discussion Forum for this product.Did this page help you?  Yes | No |  Tell us about it...

Changing a Product's Configuration

You might want to change an existing DevPay product's configuration. Changing the configuration simply means you change which regions, environments, or instance types the DevPay product covers (for more information about configuration, see Set Up Your Product's Configuration and Price). Essentially when you change a product's configuration, you go through the process of changing the product's price (for more information, see Changing Pricing).

For example, let's say you have a product that covers one or more Linux/UNIX AMIs, and you also want to sell some Windows AMIs under the same product code. You can change the product's configuration to cover your new Windows AMIs, and as part of that process, you specify the price you want to charge for the Windows AMIs. We recommend you understand the implications of selling multiple AMIs under a single or multiple product codes. For more information, see Selling Multiple AMIs.

Important

We recommend you warn your customers at least 14 days in advance of any change to your product, especially if you plan to remove items from the configuration. When you change your product's configuration, you simply walk through the price change wizard, which includes a step for specifying the product's configuration (see Changing Pricing). As part of the price change wizard, you can specify a message to include in the price change notification e-mail your customers get. In that message you can summarize what's changed about the product.

The following table describes how to change your product's configuration.

Process to Change Your Product's Configuration

1

You start the price change wizard.

For more information, see Changing Pricing. You can do either an active or a passive price change.

To add new instance types to the configuration, we recommend you do a passive price change with at least a 14-day notice.

To remove instance types from the configuration, we recommend you do an active price change with at least a 14-day notice.

2

In the price change interface, you add or remove the desired items from the configuration.

Specifically, you select or clear the check boxes for the items you want to add or remove from the configuration (to see what this looks like, see Set Up Your Product's Configuration and Price). If you add new items, you also specify their prices.

3

You write a brief summary of how the product has changed.

When you set up the price change, you have the option to include your own message as part of the notification e-mail Amazon Payments sends to your customers. We recommend you include a brief summary of the change.

For example, "As of [effective date of price change], your $20 monthly fee will also cover several Windows AMIs that we now offer, in addition to the existing Linux/UNIX AMIs. If you launch an instance of one of these new Windows AMIs, you will pay the usage prices shown here. Thank you for using our product!".

4

You complete the price change wizard.

5

After preparing any new AMIs you want to sell, you associate the product code with them.

For more information, see Associating a Product Code with an AMI and Inheriting the Product Code of your Paid AMI.

6

Your customers receive the e-mail about the price change.

Up until the price change takes effect, new customers who sign up see both the old and new pricing, and the date when the new pricing goes into effect.

7

The price change goes into effect on the date you specified.

Existing and new customers can begin to launch instances of any new AMIs that the product covers.


Important

If your product configuration change discontinues any instance types, you're not responsible for any charges your customers accrue for the discontinued instance types after the price change takes effect.