This topic describes how Elastic Compute Service (ECS) resources are billed when you deploy ECS instances on a dedicated host.

For ECS instances running on a dedicated host, you do not need to pay for the vCPUs, memories, and local disks of the instances. However, you must pay for the images, disks, public bandwidth, snapshots, and other resources of the ECS instances. For more information, see Subscription, Billing of Internet bandwidth, Billing of snapshots, and Billing method.

When the subscription of a dedicated host is active, how the related resources of the instance are billed is dependent on the status of the instance.

Running instances

All instances that are in the Running state, regardless of their billing methods, are billed as expected.

Stopped instances

For stopped instances, the related resources are billed based on the billing methods of the instances.
  • Subscription instances

    After a subscription ECS instance is stopped, all related resources are billed as expected.

  • Pay-as-you-go instances
    The No fees for stopped VPC instances feature is not fully applicable to pay-as-you-go instances that are running on a dedicated host. This differs from pay-as-you-go ECS instances that are running on a shared host. After the instance is stopped, the changes to the billing for related resources are as follows:
    • Image: The image is retained. If the image is a paid image, the billing continues.
    • Public bandwidth:
      • If the instance is assigned a public IP address, the IP address will be released and you will not be charged for the public bandwidth.
      • If the instance is bound with an EIP and is not unbound before the instance is stopped, the EIP remains unchanged and the billing continues.
        Note After the instance is stopped, the private IP address remains unchanged.
    • Disks: The disks are retained, and the billing continues.