All Products
Search
Document Center

Elastic Compute Service:Billing FAQ

Last Updated:Aug 28, 2024

This topic provides answers to frequently asked questions about Elastic Compute Service (ECS) billing.

Why am I unable to purchase pay-as-you-go instances?

You may be unable to purchase pay-as-you-go instances due to one of the following reasons:

  • You have not completed real-name verification. Before you can purchase ECS instances within a region inside the Chinese mainland, you must complete real-name verification.

  • The number of vCPUs that are required by the pay-as-you-go instances you attempting to create exceeds the remaining vCPU-based quota for the selected instance type in your account.

  • The selected instance type is unavailable for purchase in the selected region. Try again later or go to the Instance Types Available for Each Region page to view instance types available in each region.

How are invoices issued for pay-as-you-go instances?

You can request invoices for your pay-as-you-go instances. An invoice is issued based on your monthly statement. You can go to the Expenses and Costs console to request an invoice.

How is the refundable amount for an instance configuration downgrade calculated?

The refundable amount for an instance configuration downgrade is calculated based on the payment currency used in your purchase order for the instance.

  • If the payment currency is USD, the refundable amount is calculated based on the price difference.

  • If the payment currency is a currency other than USD such as Malaysian ringgit (MYR), the refundable amount is calculated based on a ratio.

Remaining value: The value of a subscription ECS instance reduces over its subscription period. If you cancel the subscription for an instance, the remaining value of the instance can be refunded to you. For example, assume that you purchased a 30-day subscription instance at the price of USD 30. If you cancel the subscription for the instance after it was in use for 10 days, the remaining value of the instance is USD 20 and USD 20 will be refunded to you.

If you used a currency other than USD to pay for the instance, the amount on the instance purchase order was converted to your payment currency at the exchange rate at the time of payment. This exchange rate will be considered during the calculation of the instance remaining value. Different from the price difference-based method, the ratio-based method ensures that refunds are made based on the exchange rate at the time of payment. This prevents the amounts refunded for instance configuration downgrades from being affected by fluctuations in the exchange rate.

Note
  • Instance configuration downgrades do not change the lifecycles of instances.

  • If you used different currencies to purchase an instance and upgrade its configurations, the configurations of the instance cannot be downgraded.

The following examples demonstrate how to calculate the refundable amount for instance configuration downgrades based on price differences:

  • Example 1: The configurations of a new instance are downgraded.

    Assume that on the first day of a calendar month, you purchased a 30-day subscription instance (Instance A) at the price of USD 1 per day and paid USD 30 in total. On the 11th day of the calendar month, you initiate a configuration downgrade for the instance. The price of the new instance configurations is USD 0.5 per day. The refundable amount for the downgrade is calculated by using the following steps:

    1. Calculate the remaining value M of Instance A.

      M = USD 30 × (30 days -10 days)/30 days = USD 20

    2. Calculate the value N of the new instance configurations.

      The instance lifecycle remains unchanged before and after the downgrade. You can use the new instance configurations only for the remaining 20 days of the instance subscription period. The following formula is used to calculate N: N = USD 0.5 per day × 20 days = USD 10.

    3. Calculate the refundable amount.

      Refundable amount = M - N = USD 20 - USD 10 = USD 10

    In this example, Alibaba Cloud will refund USD 10 for the instance configuration downgrade.

  • Example 2: The configurations of a new instance are upgraded and then downgraded.

    Assume that on the first day of a calendar month, you purchased a 30-day subscription instance (Instance B) at the price of USD 1 per day and paid USD 30 in total. On the 11th day of the calendar month, you upgraded the configurations of the instance. The price of the new instance configurations was USD 2 per day. You paid the price difference P between the original and new instance configurations. The following formula is used to calculate P: P = (USD 2 per day - USD 1 per day) × (30 days - 10 days) = USD 20. On the 21st day of the calendar month, you initiate a configuration downgrade for the instance. The price of the new instance configurations is USD 0.5 per day. The refundable amount is calculated by using the following steps:

    1. Calculate the remaining value M of Instance B.

      The configurations of the instance were upgraded. The remaining value of the instance consists of the remaining value M1 from instance purchase and the remaining value M2 from the configuration upgrade. The following formulas are used to calculate M1 and M2:

      • M1 = USD 30 × (30 days -20 days)/30 days = USD 10

      • M2 = USD 20 × (20 days -10 days)/20 days = USD 10

      M = M1 + M2 = USD 20

    2. Calculate the value N of the new instance configurations.

      The instance lifecycle remains unchanged before and after the downgrade. You can use the new instance configurations for the remaining 10 days of the instance subscription period. The following formula is used to calculate N: N = USD 0.5 per day × 10 days = USD 5.

    3. Calculate the refundable amount.

      Refundable amount = M - N = USD 20 - USD 5 = USD 15

    In this example, Alibaba Cloud will refund USD 15 for the instance configuration downgrade.

The following examples demonstrate how to calculate the refundable amount in MYR for instance configuration downgrades based on ratios:

  • Example 1: The configurations of a new instance are downgraded.

    Assume that on the first day of a calendar month, you placed an order to purchase a 30-day subscription instance (Instance A) and the order amount was USD 30. The MYR to USD exchange rate was 1:10 at the time of your purchase, and you paid MYR 300 in total. On the 11th day of the calendar month, you initiate a configuration downgrade for the instance. The price of the new instance configurations is USD 0.5 per day. The refundable amount for the downgrade is calculated by using the following steps:

    1. Calculate the remaining value M of Instance A.

      M = MYR 300 × (30 days -10 days)/30 days = MYR 200

    2. Calculate the refund ratio R.

      R = (USD 1 per day - USD 0.5 per day)/USD 1 per day = 1/2

    3. Calculate the refundable amount.

      Refundable amount = M × R = MYR 200 × 1/2 = MYR 100

    In this example, Alibaba Cloud will refund MYR 100 for the instance configuration downgrade.

  • Example 2: The configurations of a new instance are upgraded and then downgraded.

    Assume that on the first day of a calendar month, you placed an order to purchase a 30-day subscription instance (Instance B) and the order amount was USD 30. The MYR to USD exchange rate was 1:10 at the time of your purchase. You paid MYR 300 in total. On the 11th day of the calendar month, you upgraded the configurations of instance. The price of the new instance configurations was USD 2 per day. The MYR to USD exchange rate was 1:11 at the time of upgrade. You paid the price difference P between the original and new instance configurations. The following formula is used to calculate P: P = (USD 2 per day - USD 1 per day) × (30 days - 10 days) × 11 = MYR 220. On the 21st day of the calendar month, you initiate a configuration downgrade for the instance. The price of the new instance configurations is USD 0.5 per day. The refundable amount is calculated by using the following steps:

    1. Calculate the remaining value M of Instance B.

      The configurations of the instance were upgraded. The remaining value of the instance consists of the remaining value M1 from instance purchase and the remaining value M2 from the configuration upgrade. The following formulas are used to calculate M1 and M2:

      • M1 = USD 30 × (30 days -20 days)/30 days × 10 = MYR 100

      • M2 = USD 20 × (20 days -10 days)/20 days × 11 = MYR 110

      M = M1 + M2 = MYR 210

    2. Calculate the refund ratio R.

      R = (USD 2 per day - USD 0.5 per day)/USD 2 per day = 3/4

    3. Calculate the refundable amount.

      Refundable amount = M × R = M1 × R + M2 × R = MYR 100 × 3/4 + MYR 110 × 3/4 = MYR 157.5

    In this example, Alibaba Cloud will refund MYR 157.5 for the instance configuration downgrade.

Why is the refundable amount for an instance configuration downgrade less than that I expected?

If you purchased the instance at a discounted rate or if the instance price changed before the downgrade, the refundable amount may be less than that you expected.

For example, assume that you purchased a 30-day subscription instance at the price of USD 1 per day, and that the MYR to USD exchange rate was 1:10 at the time of your purchase. You paid MYR 300 for the instance. 10 days later, you initiate a configuration downgrade for the instance, and the price of the new instance configurations is USD 0.5 per day. The refundable amount is MYR 100 as calculated based on the original price of USD 1 per day. However, if you purchased the instance at a discounted rate or if the instance price changed before the downgrade, the refundable amount is calculated based on the non-discounted or new instance price. For example, if the instance price changed to USD 0.7 per day before the downgrade, the refundable amount is calculated by using the following steps:

  1. Calculate the remaining value M of Instance A.

    M = MYR 300 × (30 days -10 days)/30 days = MYR 200

  2. Calculate the refund ratio R.

    R = (USD 0.7 per day - USD 0.5 per day)/USD 1 per day = 1/5

  3. Calculate the refundable amount.

    Refundable amount = M × R = MYR 200 × 1/5 = MYR 40

In this example, the actual refundable amount is MYR 40 instead of MYR 100.

What is a savings plan?

A savings plan is a plan that provides discounts over pay-as-you-go pricing in exchange for a commitment to use a consistent amount (measured in USD per hour) of resources over a one-year or three-year period. After you purchase a savings plan, the hourly bills of your pay-as-you-go instances are covered up to the amount of the plan. For more information, see Overview.

What are the benefits of savings plans?

  • Flexible in price and payment: Savings plans are available for purchase for as little as one cent and have no price limits. Savings plans can be paid in installments to minimize the impact on your cash flow.

  • Cost-effective: Savings plans can significantly reduce costs and provide discounts for pay-as-you-go resources as great as 76% off.

  • Easy to manage: A single savings plan can be applied to pay-as-you-go ECS instances or elastic container instances across different regions, instance types, and accounts.

What is the hourly commitment of a savings plan?

When you purchase a savings plan, you commit to a usage duration and an amount of spend. The hourly commitment is the minimum number of resources (measured in USD) that you commit to use per hour. In the hourly bills that are generated, the charges for the number of resources that you committed to in the savings plan are discounted. If you select the Partial Upfront payment option for your savings plan, you pay 50% of your hourly commitment when your hourly bill is less than your hourly commitment. If you select the No Upfront payment option for your savings plan, you pay 100% of your hourly commitment when your hourly bill is less than your hourly commitment. For information about how to select an appropriate hourly commitment, see Purchase and apply savings plans.

Each savings plan can be applied to offset discounted hourly pay-as-you-go charges up to the hourly commitment that you made to purchase the plan. Within the hourly commitment, the price of a pay-as-you-go bill is discounted and then offset. Example:

Note

The following prices are for reference only. The actual prices are displayed on the buy page.

The unit price of pay-as-you-go ecs.c5.large instances for the China (Hangzhou) region is USD 0.106/hour. A discount of 57.8% off is provided for the instances after you purchase a three-year, All Upfront general-purpose savings plan. If you make an hourly commitment of USD 1, the number of ecs.c5.large instances to which the savings plan can be applied per hour is calculated based on the following formula: 1/(0.106 × 0.422) = 22.35.

When the number of instances to which a savings plan can be applied is not an integer, how does the savings plan work?

If your savings plan can be applied to 38.22 instances per hour and you have 39 instances running, the hourly fees for 38 of your instances are fully covered by your savings plan. For one of your instances, 22% of the hourly fees are covered by your savings plan, and the remaining 78% of the hourly fees are paid at regular pay-as-you-go rates. If you have 38 instances running, the coverage for 0.22 instance per hour is wasted in this savings plan.

Which types of savings plans are available?

Savings plans come in two types:

  • General-purpose savings plans

    General-purpose savings plans can be applied to pay-as-you-go ECS instances and elastic container instances. General-purpose savings plans are automatically applied to eligible pay-as-you-go instances regardless of region, instance family, instance size, and operating system.

  • ECS compute savings plans

    ECS compute savings plans can be applied only to pay-as-you-go ECS instances. ECS compute savings plans can be applied only to a specific instance family in a single region regardless of instance size and operating system.

General-purpose savings plans can be used more flexibly than ECS compute savings plans, but ECS compute savings plans offer higher discounts and cost savings. For more information, see Overview.

Which payment options do savings plans support?

Savings plans support three payment options: All Upfront, Partial Upfront, and No Upfront. The discounts that you receive varies based on the durations and payment options of savings plans. You can receive larger discounts when you purchase a three-year all upfront savings plan. The following combinations of different durations and payment options are ranked based on their discounts from largest to smallest: three-year Partial Upfront > three-year No Upfront > one-year All Upfront > one-year Partial Upfront > one-year No Upfront. For more information, see Savings plans.

Where do I view the recommendation and buy pages for savings plans?

  • Method 1:

    You can directly access the savings plan buy page to purchase a savings plan. Alternatively, you can access the Recommended page in the Expenses and Costs console to obtain purchase recommendations. Savings plans are recommended based on your specified conditions, such as historical consumption of a specified period of time, savings plan type, and payment option.

  • Method 2:

    Go to the ECS console. In the left-side navigation pane, choose Instances & Images > Savings Plans.

How do I query the discount offered in a savings plan?

You can go to the Discount Details page in the Expenses and Costs console to query the discount offered by a savings plan on pay-as-you-go pricing.

How do I query the cost savings provided by a savings plan?

You can go to the Overview tab on the Savings Plan page to view the cost savings provided by a savings plan, including the total, annual, and monthly savings.

Can I have multiple savings plans in effect at the same time?

Yes, you can purchase multiple savings plans and use them together. The system automatically selects the optimal savings plan to apply.

Can I purchase reserved instances after I purchase savings plans?

Yes, you can. However, reserved instances take precedence over savings plans to be applied to pay-as-you-go instances.

Can I purchase SCUs after I purchase savings plans?

Yes, you can. However, SCUs take precedence over savings plans to be applied to pay-as-you-go instances.

After I purchase savings plans, can I upgrade the instance types of the instances to which the savings plans are applied?

No, you cannot upgrade the instance types of the instances to which the savings plans you purchase are applied. You can purchase additional savings plans for the instance types to which you want to upgrade.

Do savings plans provide reserved resources?

No, savings plans do not provide reserved resources. You cannot specify resources to reserve when you purchase savings plans.

Can savings plans be applied to preemptible instances?

No, savings plans cannot be applied to preemptible instances.

What happens if my savings plans expire?

When your savings plans expire, the discounts provided by your savings plans are no longer available. Eligible pay-as-you-go instances are billed at their regular prices. The pay-as-you-go instances to which your savings plans have already been applied are not released. The expiration of savings plans does not affect your business.

What do I do if the billing method of an instance cannot be changed from subscription to pay-as-you-go?

You may be unable to change the billing method of an instance from subscription to pay-as-you-go due to one of the following reasons:

  • The instance is in a state that does not support billing method changes. For example, you have an unpaid order for the instance.

  • The instance is in the Expired state.

  • Billing method changes are not allowed because instance information has been changed. For example, the bandwidth of the instance has been temporarily upgraded.

If one of the preceding errors is reported, adjust the instance accordingly. If the issue persists, submit a ticket.

Why am I prompted with an overdue payment when my subscription instances have not expired?

After you purchase subscription instances, if you use resources that are billed on a per-use basis, such as snapshots and pay-by-traffic public bandwidth, you are charged for the resources separately from the instances. When your account balance is insufficient to pay for the due pay-as-you-go charges, the payment becomes overdue. You can view your consumption details to check whether you have outstanding pay-as-you-go bills. For more information, see View billing details.

How is the billable time of a pay-as-you-go instance calculated? For example, if I created a pay-as-you-go ECS instance at 01:30:00 and released it at 02:00:00, was the instance billed for a 30-minute or 1-hour period?

Pay-as-you-go instances are billed in 1-second increments. Payments are made every hour on the hour. The billable time of pay-as-you-go instances is automatically calculated. For example, if you created a pay-as-you-go instance at 01:30:00 and released it at 02:00:00, the hour from 01:00:00 to 02:00:00 is a billing cycle. The billable time is 1,800 seconds, which is calculated based on the following formula: (30 minutes) × 60 = 1800 seconds.

After a pay-as-you-go instance is stopped manually or automatically due to an overdue payment, am I still charged for the instance?

Instance stop due to an overdue payment: When your account has overdue payments, your pay-as-you-go instances automatically stop and billing for the instances stops. Instances do not always remain in the Stopped state after they are stopped due to overdue payments. For more information, see Pay-as-you-go.

Manual instance stop: You can use the ECS console or call the StopInstance operation to stop a running pay-as-you-go instance. When the instance is stopped, it enters the Stopped state. How stopped pay-as-you-go instances are billed depends on their network types.

  • VPC: You can enable economical mode for pay-as-you-go instances that reside in VPCs.

    • If economical mode is enabled, billing for pay-as-you-go instances begins when the instances are created, and billing for some instance resources stops when the instances enter the Stopped state and resumes when the instances are restarted. When a pay-as-you-go instance is stopped in economical mode, billing stops only for the computing resources (vCPUs and memory) and static public IP address of the instance and continues for other resources, such as the disks and EIP. For more information, see Economical mode.

    • If economical mode is disabled, billing for pay-as-you-go instances continues when they enter the Stopped state.

  • Classic network: Pay-as-you-go instances in the classic network are billed regardless of whether they are in the Stopped state.

What do I do if an order cannot be placed to change the billing method of an instance from pay-as-you-go to subscription?

You may be unable to place the order due to one of the following reasons:

  • The instance is in a state that does not support billing method changes. For example, you have an unpaid order for the instance.

  • Billing method changes are not allowed due to an upcoming scheduled automatic release.

  • Billing method changes are not allowed because instance information has been changed.

  • A previous order to change the billing method of the instance has not been paid.

If one of the preceding errors is reported, adjust the instance accordingly.

How long after an order is paid does it take to change the billing method of an instance from pay-as-you-go to subscription?

The billing method of your instance is changed after the order is paid. It can take up to 4 seconds to change the billing method of up to 20 instances. After the change is complete, you can see that the billing method of your instance is changed to Subscription in the ECS console.

What do I do if the billing method of an instance cannot be changed from pay-as-you-go to subscription?

To resolve this issue, submit a ticket.

When I change the billing method of an instance from pay-as-you-go to subscription, does the billing method for network usage of the instance also change?

No, the billing method for network usage of the instance does not change. Only the billing method of instances and disks can be changed from pay-as-you-go to subscription. For information about how to change the billing method for network usage, see Overview of instance configuration changes.

I have an unpaid order to change the billing method of an instance from pay-as-you-go to subscription. If I upgrade the configurations of the instance, is the order still valid?

An order is created when you change the billing method of your instance from pay-as-you-go to subscription. You must pay for the order to complete the change. If you upgrade the configurations of the instance before the order is paid, the order payment cannot be completed because the instance components are different and the original order no longer matches the instance components. If you still want to change the billing method of your instance, you must cancel the unpaid order and place a new order.

Why am I unable to change a pay-as-you-go instance into a subscription instance?

The pay-as-you-go instance that you want to change must meet the following requirements:

  • The instance type of the instance is not retired. For more information, see Retired instance types.

  • The instance is not a preemptible instance.

  • You do not have unpaid orders for the instance.

    If you have unpaid orders for the instance, you must pay for the orders or cancel the orders before you can change the billing method of the instance.

  • The automatic release time is not set for the instance.

    If the automatic release time is set for the instance, you must cancel the automatic release of the instance before you change its billing method. For more information, see Release an instance.

  • The instance is in the Running or Stopped state.

    If you placed an order to change the billing method of an instance in the Running or Stopped state and then the instance entered a different state before the payment is completed, the payment fails and the billing method does not change. You can go to the Billing Management console and pay for the order when the instance is in the Running or Stopped state again.

What ECS instances support the economical mode?

The ECS instances that meet all of the following requirements support the economical mode:

  • The instances reside in virtual private clouds (VPCs).

  • The instances are pay-as-you-go or preemptible instances.

  • The instance families are not equipped with local storage.

  • The instance families are not equipped with persistent memory.

For more information, see Economical mode.

Can I retain the computing and network resources of a stopped pay-as-you-go instance after I enable the default economical mode?

After you enable the default economical mode, you still can specify whether to trigger the economical mode for a pay-as-you-go instance when you stop the instance. If the economical mode is not triggered for a pay-as-you-go instance when the instance is stopped, the computing and network resources of the instance are not released.

If you need to stop and then restart a pay-as-you-go instance within a short period of time, we recommend that you perform one of the following operations to prevent the economical mode from being triggered: Call the StopInstance operation with StoppedMode set to KeepCharging, or set Stop Mode to Standard Mode when you stop the instance in the ECS console.

Can the economical mode be enabled for ECS instances that are stopped from within their operating systems?

If you stop an instance from within its operating system, the economical mode cannot be triggered for the instance. After the default economical mode is enabled, the mode can be triggered only for pay-as-you-go or preemptible instances that are stopped due to one of the following reasons:

  • Operations in the ECS console. For more information, see Stop an instance.

  • API requests initiated by Alibaba Cloud CLI or SDKs. For more information, see StopInstance.

  • Overdue payments.

Do instances that are equipped with local storage support triggering the economical mode?

No, instances that are equipped with local storage do not support triggering the economical mode.

When I attempted to restart an instance immediately after it is stopped in economical mode, an OperationConflict error was reported. Why?

When the economical mode is triggered for an instance, the computing resources (CPUs and memory) and auto-assigned public IP address of the instance are recycled.

If you need to stop and then restart a pay-as-you-go instance within a short period of time, we recommend that you perform one of the following operations to prevent economical mode from being triggered: Call the StopInstance operation with StoppedMode set to KeepCharging, or set Stop Mode to Standard Mode when you stop the instance from the ECS console.

When I called the StartInstance operation to restart an instance that was stopped in economical mode, an OperationDenied.NoStock error was reported. Why?

When an instance is stopped in economical mode, the computing resources of the instance are recycled. If available resources are insufficient, an OperationDenied.NoStock error is reported when you attempt to start the instance. We recommend that you try again later.

When I restart an instance that was stopped in economical mode, the public IP address of the instance changes. How do I prevent the IP address from changing?

When an instance is stopped in economical mode, its auto-assigned public IP address is recycled. When the instance is restarted, it is automatically assigned a new public IP address.

To retain the original auto-assigned public IP address, you can convert the auto-assigned public IP address into an elastic IP address (EIP) before you stop the instance. The EIP is not released when the instance is stopped in economical mode, which ensures that the public IP address of the instance remains unchanged. For more information, see Convert the public IP address of an instance in a VPC to an EIP and ConvertNatPublicIpToEip.

Important

After an auto-assigned public IP address is converted to an EIP, you are charged for the outbound bandwidth, EIP configuration (free of charge in specific conditions), and EIP association (free of charge in specific conditions) when you use the EIP to access the Internet. For more information, see Billing overview.

Can I release ECS instances on my own?

Yes, you can manually release or schedule the automatic release of pay-as-you-go instances. However, you cannot release subscription instances on your own.

If the issue persists, submit a ticket.

Why is a pay-as-you-go bill generated for my instance? What are the charges on the bill?

You can copy your instance ID or instance name and perform the following steps to view the bill details:

  1. Log on to the ECS console.

  2. In the top navigation bar, choose Expenses > Expenses and Costs.

  3. In the left-side navigation pane, choose Bills > Bill Details.

  4. Click the Billing Details tab.

  5. Set the Instance ID or Instance Name and click Search.

Why am I unable to change the billing method of an instance from subscription to pay-as-you-go?

Your ECS usage determines whether the billing method of your subscription instances can be changed to pay-as-you-go. Before you change the billing method of a subscription instance, make sure that the instance is in the Running or Stopped state.

Do I need to pay for Red Hat images when I use them to create ECS instances?

Yes, you must pay for Red Hat images when you use them to create ECS instances. Red Hat images are paid images. You can view the Red Hat image prices on the ECS instance buy page.

How are ESSDs billed?

ESSDs support the subscription and pay-as-you-go billing methods. For more information, visit the Pricing tab of the Elastic Compute Service product page.

How do I purchase a standard SSD? What are the pricing options for I/O optimized instances and standard SSDs?

For more information about pricing, visit the Pricing tab of the Elastic Compute Service product page.

How is a separately created pay-as-you-go data disk billed?

Pay-as-you-go data disks are billed on an hourly basis. If your account balance is insufficient, the services provided by the data disks are suspended.

How am I billed for the network usage of ECS instances?

For information about billing for the network usage of ECS instances, see Public bandwidth.

How is the inbound and outbound traffic of pay-as-you-go instances billed?

Traffic between ECS instances or between ECS instances and other Alibaba Cloud services in the same VPC is free of charge. Traffic between ECS instances and the Internet is billed based on the following rules:

  • Inbound Internet traffic is free of charge. Inbound Internet traffic refers to traffic from the Internet to ECS instances, such as traffic generated when you download resources from the Internet to your ECS instances or when your users upload resources to your ECS instances by using an FTP client.

  • Outbound Internet traffic is billed. Outbound Internet traffic refers to traffic from ECS instances to the Internet, such as traffic generated when your ECS instances provide external access or when your users download internal resources from your ECS instances by using an FTP client.

For more information about bandwidth billing, see Public bandwidth.

What is the difference between the pay-by-bandwidth and pay-by-traffic billing methods for network usage?

If you select pay-by-bandwidth as the billing method for network usage, you are charged based on the specified bandwidth. Your actual outbound bandwidth is capped at the specified bandwidth.

If you select pay-by-traffic as the billing method for network usage, you are charged based on actual data transfers. To prevent out-of-control fees caused by traffic bursts, you can specify a bandwidth limit for outbound Internet traffic.

For more information, see Public bandwidth.

An instance has an auto-assigned public IP address that uses the pay-by-bandwidth metering method. After I change the metering method of the auto-assigned public IP address to pay-by-traffic, convert the auto-assigned public IP address into an EIP, and then change the billing method of the EIP to subscription, a price difference occurs. Why?

After you change the metering method of the auto-assigned public IP address that is associated with an instance from pay-by-bandwidth to pay-by-traffic, the auto-assigned public IP address uses the pay-as-you-go billing method. If you convert the auto-assigned public IP address into an EIP by performing the operations described in Convert the public IP address of an instance in a VPC to an EIP and then change the billing method of the EIP from pay-as-you-go to subscription by performing the operations described in Switch metering methods, the payable amount for changing the billing method of the EIP is different from the refundable amount for changing the metering method of the auto-assigned public IP address. This is because you purchased the instance at a discounted rate and does not receive any discount when you change the billing method of the EIP from pay-as-you-go to subscription.

Can I adjust the maximum bandwidth that I specified?

Yes, after you create an instance, you can adjust the maximum bandwidth that you specified for the instance. For more information, see Overview of instance configuration changes.

Will I be charged for the traffic generated by ECS instances under attacks?

You will not be charged for the inbound Internet traffic generated by ECS instances under attacks, but will be charged for the outbound Internet traffic.

We recommend that you use Security Center to reinforce the security of ECS instances.

Can I select the pay-by-traffic billing method for network usage when I purchase a subscription instance?

Yes, you can select the pay-by-traffic billing method for network usage when you purchase a subscription instance. For more information, see Create an instance on the Custom Launch tab.

For more information about the pay-by-traffic billing method, visit the Pricing tab of the Elastic Compute Service product page.

How am I charged when I select the pay-by-traffic billing method for network usage?

Pay-by-traffic is a pay-as-you-go billing method in which you are charged based on the actual amount of data transferred. Payments are settled every hour on the hour. To keep services running properly, make sure that your account balance is sufficient. To prevent out-of-control fees caused by traffic bursts, you can specify a bandwidth limit for traffic.

Can I change the billing method for network usage of a subscription instance from pay-by-bandwidth to pay-by-traffic?

Yes, you can change the billing method for network usage of a subscription instance from pay-by-bandwidth to pay-by-traffic by using the bandwidth downgrade feature. However, you can make this change only a limited number of times. For more information, see Modify the bandwidth configurations of subscription instances.

You can also use the renewal and configuration downgrade feature to change the billing method for network usage. The new configurations do not take effect until the next billing cycle starts. For more information, see Downgrade the configurations of an instance during renewal.

Can I adjust the maximum bandwidth for an ECS instance at any time?

Yes, you can use the bandwidth downgrade feature to adjust the maximum bandwidth for an ECS instance at any time. After you set the maximum bandwidth to a smaller value, the new value takes effect immediately. A maximum of three refunds can be made for each instance. Exercise caution when you downgrade the configurations of an instance.

If you downgraded the configurations of a subscription instance when you renewed it, you cannot upgrade or downgrade the instance configurations again until the new billing cycle starts.

If the pay-by-traffic billing method for network usage is used for a subscription instance, can the instance continue to use the public bandwidth service when a payment becomes overdue due to insufficient account balance?

Overdue payments do not affect the running of subscription instances, but do cause the pay-by-traffic public bandwidth service to suspend. After the public bandwidth service suspends, the instances lose Internet connectivity. You can continue to use the public bandwidth service only after you settle the overdue payments. To keep services running properly, make sure that your account balance is sufficient.

If the pay-by-traffic billing method for network usage is used for a subscription instance, will I be notified when a payment becomes overdue in my account?

Yes, you will be notified by SMS. To keep services running properly, make sure that your account balance is sufficient.

If the pay-by-traffic billing method for network usage is used for a subscription instance, can I upgrade the instance type after a payment becomes overdue in my account?

No, you can upgrade the instance type only after you settle the overdue payment.

If the pay-by-traffic billing method for network usage is used for a subscription instance, does the public bandwidth service of the instance automatically resume after I settle overdue payments?

If the public bandwidth service suspended due to an overdue payment, the service automatically resumes when the overdue payment is settled.

How am I billed for network usage after I change the billing method for network usage of a subscription instance from pay-by-bandwidth to pay-by-traffic?

When you change the billing method for network usage of a subscription instance from pay-by-bandwidth to pay-by-traffic, you are billed for network usage based on actual data transfers. Payments are settled every hour on the hour. For pricing details, visit the of the Elastic Compute Service product page.