- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Service Provisioning
- Allowing or Disallowing Access to Cloud Assets
- Asset Map
- Asset Management
- Sensitive Data Identification
- Data Asset Protection
- Data Security Operations
- Alarm Notifications
- Permissions Management
- Key DSC Operations
- Best Practices
-
API Reference
- Before You Start
- Calling APIs
-
API Description
- Data Watermarking
- Resource Management
- Dynamic Data Masking
- Alarm Notifications
-
Image Watermarking
- Injecting Invisible Watermarks into Images
- Extracting Invisible Text Watermarks
- Extracting Invisible Watermarks from Images
- Injecting Invisible Watermarks into Images (Image Addresses)
- Extracting Dark Watermarks from Images (Image Addresses)
- Extracting Invisible Image Watermarks from Images (Image Addresses)
- Asset Management
- Document Watermarking
-
Sensitive Data Discovery
- Querying the Identification Task List
- Querying the Result of an Identification Task
- Viewing the Rule List
- Creating a Sensitive Data Scanning Rule
- Modifying a Sensitive Data Scanning Rule
- Deleting a Sensitive Data Scanning Rule
- Querying Sensitive Data Scanning Rule Groups
- Creating a Sensitive Data Scanning Rule Group
- Deleting a Sensitive Data Scanning Rule Group
- Creating a Sensitive Data Scanning Task
- Deleting a Sensitive Data Scanning Task
- Static Data Masking
- API Call Records
- Appendixes
- Change History
- SDK Reference
-
FAQs
- Product Consulting
- Regions and AZs
- Asset Authorization
-
Sensitive Data Identification and Masking
- What Services Can Use DSC to Scan for Sensitive Data?
- How Long Does It Take for DSC to Identify and Mask Sensitive Data?
- What Are the Identification Templates Supported by DSC?
- Does Data Masking Affect My Raw Data?
- Does DSC Have Specific Requirements on the Character Set for Which Sensitive Data Is to Be Identified and Masked?
- Data Watermarking
- Data Usage Audit
Show all
Overview of Billing Modes
DSC provides two billing modes: yearly/monthly and pay-per-use.
- Yearly/Monthly billing: A prepaid mode in which you pay for the service before using it. Your bill is settled based on the required period. The longer you use the service, the more discounts you get. This mode is applicable to mature services that have long-term and stable device requirements.
- Pay-per-use billing: a postpaid mode in which you pay for what you used. You are billed by second based on the actual usage. Your bill is settled by the hour. With the pay-per-use billing mode, you can easily adapt to resource requirement changes, reducing the risk of overprovisioning of resources or lacking capacity. In this mode, there are no upfront commitments required.
Table 1 describes the differences between the billing modes.
Billing Mode |
Yearly/Monthly Billing |
Pay-Per-Use |
Payment Method |
Prepaid Billed by the purchase period specified in your order |
Postpaid You are charged based on the actual number of API calls. Each month, you can make 1 million API calls. Note that the unused API calls for the previous month will become invalid. |
Billing Period |
Billed by the purchase period specified in the order |
API calls |
Billing Item |
Version specifications, database extension package, and OBS extension package. |
API calls (data masking and watermarking) |
Changing Specifications |
Version specifications can be changed. |
Version specifications cannot be changed. |
Application Scenario |
This billing mode is cost-effective and suitable when the duration of resource usage is predictable. The yearly/monthly mode is recommended for long-term users. |
This mode is ideal when you want more flexibility and control on ECS usage. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.