Security in Billing
Who may see costs, invoices and budgets and change them (IAM), what is recorded in the audit log, and which billing permissions reach into other services.
IAM actions
Every request, through the API, the CLI, Terraform or the console, is checked against your IAM
policies. Billing's resource names carry the region: an invoice is
rn:ews:de1:<organization id>:billing:invoice/<id>, and budgets (budget/<id>), payment methods
(payment-method/<id>) and saved views (cost-view/<id>) follow the same pattern.
Requests for one budget, invoice, payment method or saved view are checked against that resource.
Everything else, including lists, the cost explorer, creating a budget or a view, the billing
account and the cost report, is checked against rn:ews:de1:<organization id>:billing:*. The
console decides which buttons to show by the same wildcard.
| Action | Access | What it allows |
|---|---|---|
billing:GetBillingSummary | Read | View cost summary |
billing:GetCostAndUsage | Read | Explore cost and usage: time series by any dimension, drill-down to usage lines, forecasts, credits and CSV export |
billing:EstimateCost | Read | Price an operation before running it: per hour, per month with the monthly cap. Holding the operation’s own action is enough too |
billing:GetCostReportSettings | Read | View who receives the monthly cost report, and the reports sent |
billing:UpdateCostReportSettings | Write | Turn the monthly cost report on or off, choose its recipients and the accounting export’s cost-centre tag and accounts |
billing:SendCostReport | Write | Send a month’s cost report (and its CSVs) now, to the configured recipients; again at most every 10 minutes |
billing:CreateCostView | Write | Save a cost explorer view, optionally mailed monthly with its CSV |
billing:UpdateCostView | Write | Change a saved cost view, its sharing or its monthly mail |
billing:DeleteCostView | Write · destructive | Delete a saved cost view |
billing:DismissCostFinding | Write | Mark a waste finding (idle, oversized, stopped, unattached, unused address) as kept, with a reason, for good or until a date — or bring it back |
billing:GetInvoices | Read | View invoices |
billing:GetBudgets | Read | View budgets |
billing:CreateBudget | Write | Create cost budgets |
billing:UpdateBudget | Write · destructive | Update an existing cost budget |
billing:DeleteBudget | Write · destructive | Delete a cost budget |
billing:ApproveBudgetAction | Write · destructive | Approve or dismiss what a budget proposes to stop or scale down. Each stop also needs its own action (ec2:StopInstances, rds:StopDBInstance, autoscaling:UpdateAutoScalingGroup) on that resource |
billing:GetBillingAccount | Read | View the billing account: company name, invoice address, VAT ID, invoice e-mail |
billing:UpdateBillingAccount | Write | Change the company name, invoice address, VAT ID or invoice e-mail printed on future invoices |
billing:GetPaymentMethods | Read | View payment methods on file |
billing:ManagePaymentMethods | Write · destructive | Add, remove, or change the default payment method |
Generated from the service’s IAM descriptor. Sensitive reads hand over secret material or source code and are recorded in the audit log like writes; destructive writes delete, overwrite or revoke.
billing:GetCostAndUsagecovers the cost explorer, its exports, usage lines, credits, the comparison with other clouds, the Usage and Savings pages, saved views and the Cost cards of resources.billing:EstimateCostis not needed by whoever holds the IAM action of the operation priced.- Checking a budget's scope also needs
tags:ListTags. - Approving a budget's proposal also needs, for each resource,
ec2:StopInstances,rds:StopDBInstanceorautoscaling:UpdateAutoScalingGroup. - Grouping or filtering costs by where resources run needs
iam:UpdateOrganization. - Closing the organization needs
iam:DeleteOrganization(see Close the organization).
A policy for someone who may read costs and manage budgets, but not invoices or the billing account (replace org-id with your organization's id):
{
"Version": "2024-01-01",
"Statement": [
{
"Effect": "Allow",
"Action": [
"billing:GetBillingSummary",
"billing:GetCostAndUsage",
"billing:GetBudgets",
"billing:CreateBudget",
"billing:UpdateBudget",
"billing:DeleteBudget"
],
"Resource": "rn:ews:de1:org-id:billing:*"
}
]
}Audit
Every write (creating, changing and deleting budgets, saved views and payment methods, changing the billing account and the cost report settings, sending a report, keeping a finding, approving or dismissing a proposal) is recorded in the audit log, allowed or denied, once the request has passed its validation: a request with a malformed body, or an id that is not a UUID, is refused before the permission check and not recorded, and so is approving or dismissing a proposal that does not exist. Reads are recorded only when they are denied, at most once a minute per user and action.
The stops an approved proposal runs are recorded under the approver's name, as the services' own actions.
Who sees the numbers
The cost explorer, the budgets and the reports are scoped to your organization. A private saved view is visible to its creator only. The monthly cost report and budget alerts go only to the addresses configured for them; the report's default recipients are the owners and the invoice e-mail.