If you have overdue payments in your account, the status of your Elastic Compute Service (ECS) instances in a scaling group changes. Make sure that you have sufficient balance in your account to ensure service availability.

ECS instances that are billed on a subscription basis

By default, the ECS instances that are billed on a subscription basis are stopped on the 15th day after the payments for the instances are due. In some cases, the ECS instances may be stopped within 15 days after the payments for the instances are due. We recommend that you renew your subscription or enable the auto-renewal feature in advance to continue using your account and retain your resources. Make sure that you have sufficient balance within your account.

If you fail to renew your subscription in a timely manner, Auto Scaling immediately removes the ECS instances when the payments for the ECS instances are due. These ECS instances cannot provide services after they are stopped. For more information, see Changes in resource states after an instance expires.

Note Auto Scaling immediately removes the ECS instances from the scaling group when the ECS instances are stopped.

ECS instances that are billed on a pay-as-you-go basis

If the available credit including the balance and vouchers within your account is less than the payable amount, your account is deemed to have overdue payments.

If you have overdue payments within your account, the following rules apply to pay-as-you-go and preemptible ECS instances:

  • By default, the ECS instances that are billed on a pay-as-you-go basis are stopped on the 15th day after the payments for the ECS instances are due. In some cases, the ECS instances may be stopped within 15 days after the payments are due.
    Note For more information about the time when ECS instances are stopped, see Settlement cycle.
  • Auto Scaling cannot automatically create new ECS instances. By default, Auto Scaling immediately removes the ECS instances that are stopped from the scaling group or releases the ECS instances. The ECS instances that are stopped cannot provide services.
    Note Auto Scaling immediately removes the ECS instances that are stopped from the scaling group or releases the ECS instances.
    • Auto Scaling considers the ECS instances that are stopped unhealthy.
    • If ECS instances are automatically created by Auto Scaling, or are manually added to the scaling group and their lifecycle is managed by the scaling group, Auto Scaling removes and releases the unhealthy instances.
    • If ECS instances are manually added to the scaling group and their lifecycle is not managed by the scaling group, Auto Scaling removes the unhealthy instances from the scaling group but does not release the unhealthy instances. For information about changes to the instance status after ECS instances are removed from scaling groups, see Resource status in the event of an overdue payment.
    Note By default, Auto Scaling does not release pay-as-you-go ECS instances for which the payments are due.
  • If you top up your account in a timely manner and settle the overdue bills of the ECS instances, Auto Scaling resumes the status of the ECS instances, and the ECS instances can continue to provide services in the scaling group.

ECS instances that are billed on a mixed basis

ECS instances that are billed on a mixed basis are the subscription ECS instances that provide some pay-as-you-go services.

If you have overdue payments within your account, the following rules apply to the ECS instances that are billed on a mixed basis:

  • By default, the ECS instances that are billed on a mixed basis are stopped on the 15th day after the payments for the ECS instances are due. In some cases, the ECS instances may be stopped within 15 days after the payments are due.
  • By default, Auto Scaling immediately removes the ECS instances that are billed on a mixed basis from the scaling group when the ECS instances are stopped.
  • If you top up your account in a timely manner and settle the overdue bills of the ECS instances, Auto Scaling resumes the status of the ECS instances, and the ECS instances can continue to provide services in the scaling group.