Billing Center
IAM provides system-defined identity policies to define common actions supported by cloud services. You can also create custom identity policies using the actions supported by cloud services for more refined access control.
In addition to IAM, the Organizations service also provides service control policies (SCPs) to set access control policies.
SCPs do not actually grant any permissions to a principal. They only set the permissions boundary for the principal. When SCPs are attached to a member account or an organizational unit (OU), they do not directly grant permissions to that member account or OU. Instead, the SCPs just determine what permissions are available for that member account or the member accounts under that OU. The granted permissions can be applied only if they are allowed by the SCPs.
To learn more about how IAM policies are different from Organizations SCPs, see What Are the Differences in Access Control Between IAM and Organizations?
This section describes the elements used by IAM custom identity policies and Organizations SCPs. The elements include actions, resources, and conditions.
- For details about how to use these elements to create an IAM custom identity policy, see Creating a Custom Identity Policy.
- For details about how to use these elements to create a custom SCP, see Creating an SCP.
Actions
Actions are specific operations that are allowed or denied in an identity policy.
- The Access Level column describes how the action is classified (such as list, read, or write). This classification helps you understand the level of access that an action grants when you use it in an identity policy.
- The Resource Type column indicates whether the action supports resource-level permissions.
- You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions and you must specify all resources ("*") in your identity policy statements.
- If this column includes a resource type, you must specify the URN in the Resource element of your statements.
- Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.
For details about the resources types defined by Billing Center, see Resources.
- The Condition Key column contains keys that you can specify in the Condition element of an identity policy statement.
- If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
- If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
- If the Condition Key column is empty (-) for an action, the action does not support any condition keys.
For details about the condition keys defined by Billing Center, see Conditions.
- The Alias column lists the policy actions that are configured in identity policies. With these actions, you can use APIs for policy-based authorization. For details, see Policies and Identity Policies.
The following table lists the actions that you can define in identity policy statements for Billing Center.
|
Action |
Permissions |
Access Level |
Resource Type (*: required) |
Condition Key |
Alias |
|---|---|---|---|---|---|
|
billing:balance:update |
Grants permission to withdraw money, top up the account, make payments, and enable balance alerting. |
write |
- |
- |
- |
|
billing:balance:view |
Grants permission to view account statements, payment records, expenditure quotas, account adjustment records, and arrears. |
list |
- |
- |
|
|
billing:balance:export |
Grants permission to export transaction and payment records. |
read |
- |
- |
- |
|
billing:bill:update |
Grants permission to update bills. |
write |
- |
- |
- |
|
billing:bill:view |
Grants permission to view bills, expenditures of the current month, and expenditure trends. |
list |
- |
- |
|
|
billing:bill:export |
Grants permission to export the bill summary. |
read |
- |
- |
|
|
billing:billDetail:update |
Grants permission to update bill details. |
write |
- |
- |
|
|
billing:billDetail:view |
Grants permission to view bill details. |
read |
- |
- |
|
|
billing:billDetail:export |
Grants permission to export bill details. |
read |
- |
- |
|
|
billing:resourcePackages:view |
Grants permission to view resource packages, remaining usage, and usage details, and to export resource usage details. |
list |
- |
- |
- |
|
billing:resourcePackages:update |
Grants permission to set alerts for remaining usage of resource packages. |
write |
- |
- |
- |
|
billing:contract:update |
Grants permission to view offline contracts. |
write |
- |
- |
- |
|
billing:coupon:view |
Grants permission to view and activate coupons. |
read |
- |
- |
- |
|
billing:contract:viewDiscount |
Grants permission to view commercial discounts. |
read |
- |
- |
- |
|
billing:invoice:manage |
Grants permission to manage invoices. |
write |
- |
- |
- |
|
billing:invoice:view |
Grants permission to view invoice history and details. |
read |
- |
- |
- |
|
billing:invoice:export |
Grants permission to export invoice information and download invoices. |
read |
- |
- |
- |
|
billing:order:pay |
Grants permission to pay for orders. |
write |
- |
- |
|
|
billing:order:view |
Grants permission to view order information and pay-per-usage resource packages. |
list |
- |
- |
|
|
billing:subscription:renew |
Grants permission to renew resources, enable auto-renewal, set expiration policies, and change the billing mode from pay-per-use to yearly/monthly. |
write |
- |
- |
|
|
billing:subscription:view |
Grants permission to view renewals and query resources that can be changed from pay-per-use to yearly/monthly. |
list |
- |
- |
|
|
billing:subscription:unsubscribe |
Grants permission to view resources that can be unsubscribed from and have been unsubscribed from. |
write |
- |
- |
|
|
billing:consumption:view |
Grants permission to view expenditure breakdowns by enterprise project. |
read |
- |
- |
- |
|
billing::activeEPFinance |
Grants permission to enable or disable Enterprise Project Management Service (EPS). |
write |
- |
- |
- |
|
billing::activeEPFundQuota |
Grants permission to enable or disable the fund quota function for enterprise projects. |
write |
- |
- |
- |
|
billing::viewEPFundQuota |
Grants permission to query the fund quota of an enterprise project. |
read |
- |
- |
- |
|
billing::updateEPFundQuota |
Grants permission to modify the fund quota of an enterprise project. |
write |
- |
- |
- |
|
billing::listEPFundQuotaHistory |
Grants permission to view the fund quota adjustment records of enterprise projects. |
read |
- |
- |
- |
|
billing::updateEPGroup |
Grants permission to modify enterprise project groups. |
write |
- |
- |
- |
|
billing::viewEPGroup |
Grants permission to view enterprise project groups. |
read |
- |
- |
- |
Resources
Billing Center does not support resource-level authorization. To allow access to Billing Center, use a wildcard (*) in the Resource element of the identity policy, indicating that the identify policy will be applied to all resources.
Conditions
Condition Key
A Condition element lets you specify conditions for when an identity policy is in effect. It contains condition keys and operators.
- The condition key that you specify can be a global condition key or a service-specific condition key.
- Global condition keys (with the g: prefix) apply to all actions. Cloud services do not need to provide user identity information. Instead, the system automatically obtains such information and authenticates users. For details, see Global Condition Keys.
- Service-specific condition keys (with the abbreviation of a service name plus a colon as the prefix, for example, BILLING:) only apply to operations of the specified service. For details, see Table 2.
- The number of values associated with a condition key in the request context of an API call makes the condition key single-valued or multivalued. Single-valued condition keys have at most one value in the request context of an API call. Multivalued condition keys can have multiple values in the request context of an API call. For example, a request can originate from at most one VPC endpoint, so g:SourceVpce is a single-valued condition key. You can tag resources and include multiple tag key-value pairs in a request, so g:TagKeys is a multivalued condition key.
- A condition operator, a condition key, and a condition value together constitute a complete condition statement. An identity policy can be applied only when its request conditions are met. For supported condition operators, see Operators.
Service-specific Condition Keys Supported by Billing Center
The following table lists the condition keys that you can define in identity policies for Billing Center. You can include these condition keys to specify conditions for when your identity policy is in effect.
|
Service-specific Condition Key |
Type |
Single-valued/Multivalued |
Description |
|---|---|---|---|
|
billing:cloudServiceType |
string |
Multivalued |
Filter access based on the cloud service type specified in the request parameter. |
Condition Key Examples
billing:cloudServiceType
Example: Only cloud service resources of the hws.service.type.ebs type can be unsubscribed from.
{
"Version": "5.0",
"Statement": [{
"Effect": "Allow",
"Action": [
"billing:subscription:unsubscribe"
],
"Condition": {
"ForAnyValue:StringEquals": {
"billing:cloudServiceType": [
"hws.service.type.ebs"
]
}
}
}]
}
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot