Billing Rules
This document mainly introduces information about the billing items and billing logic for Private Connections.
Note
- PrivateLink is in the public beta stage. During the beta period, your instance fees and traffic handling fees will be waived. The end of the beta period will be announced on the official website, so please pay attention to announcements.
Billing Items
The billing items for private connections are divided into instance fees and traffic handling fees.
| Billing Item | Billing Method | Billing Cycle | Billing Item Description | Unit Price |
|---|---|---|---|---|
| Endpoint Instance | Postpaid | Hourly Basis | Endpoint instance fee | 0.07 yuan/h |
| Endpoint Traffic | Postpaid | Hourly Basis | Bidirectional traffic through the endpoint NIC, generates a traffic order every hour | 0.07 yuan/GB |
Billing Logic
Endpoints and endpoint services can belong to different accounts, so when creating an endpoint service, you can choose whether the cost incurred by endpoints related to this service is borne by the service provider or the service user.
| Payer | Description |
|---|---|
| Service User (default) | The account that creates the endpoint bears all costs incurred by the endpoint, including instance fees and traffic fees |
| Service Provider | The account that creates the endpoint service bears all costs incurred by all endpoints associated with this service, including instance fees and traffic fees |
Note:
- The minimum billing granularity for instance fees is 1 hour; periods less than 1 hour will be billed as 1 hour.
- Changes within a billing cycle, such as disconnecting, replacing service resources, or deleting endpoint services, will not affect endpoint payment.
- Regardless of which account is the payer, the billing object remains the endpoint.
- Once the payer is chosen when creating an endpoint service, it cannot be updated.
Billing Cycle
A billing cycle begins once the connection from the endpoint to the endpoint service is successfully established.
Note:
- Disconnected endpoints are considered idle endpoints. The maximum number of idle endpoints per account cannot exceed 10; otherwise, new endpoints cannot be created.