AWS Billing Conductor identity-based policy examples - AWS Billing Conductor

AWS Billing Conductor identity-based policy examples

By default, IAM users and roles don't have permission to create or modify AWS Billing Conductor resources. They also can't perform tasks using the AWS Management Console, AWS CLI, or AWS API. An IAM administrator must create IAM policies that grant users and roles permission to perform specific API operations on the specified resources they need. The administrator must then attach those policies to the IAM users or groups that require those permissions.

To learn how to create an IAM identity-based policy using these example JSON policy documents, see Creating Policies on the JSON Tab in the IAM User Guide.

Policy best practices

Identity-based policies are very powerful. They determine whether someone can create, access, or delete AWS Billing Conductor resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations:

  • Get started using AWS managed policies – To start using AWS Billing Conductor quickly, use AWS managed policies to give your employees the permissions they need. These policies are already available in your account and are maintained and updated by AWS. For more information, see Get started using permissions with AWS managed policies in the IAM User Guide.

  • Grant least privilege – When you create custom policies, grant only the permissions required to perform a task. Start with a minimum set of permissions and grant additional permissions as necessary. Doing so is more secure than starting with permissions that are too lenient and then trying to tighten them later. For more information, see Grant least privilege in the IAM User Guide.

  • Enable MFA for sensitive operations – For extra security, require IAM users to use multi-factor authentication (MFA) to access sensitive resources or API operations. For more information, see Using multi-factor authentication (MFA) in AWS in the IAM User Guide.

  • Use policy conditions for extra security – To the extent that it's practical, define the conditions under which your identity-based policies allow access to a resource. For example, you can write conditions to specify a range of allowable IP addresses that a request must come from. You can also write conditions to allow requests only within a specified date or time range, or to require the use of SSL or MFA. For more information, see IAM JSON policy elements: Condition in the IAM User Guide.

AWS Billing Conductor identity-based policy examples

This topic contains example policies that you can attach to your IAM user or group to control access to your account's information and tools.

Granting full access to the AWS Billing Conductor console

To access the AWS Billing Conductor console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the AWS Billing Conductor resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (IAM users or roles) with that policy.

To ensure that those entities can still use the AWS Billing Conductor console, also attach the following AWS managed policy to the entities. For more information, see Adding Permissions to a User in the IAM User Guide:

In addition to the billingconductor:* permissions, pricing:DescribeServices is required for pricing rule creation, and organizations:ListAccounts is required to list linked accounts that are linked to the payer account.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "billingconductor:*", "Resource": "*" }, { "Effect": "Allow", "Action": "organizations:ListAccounts", "Resource": "*" }, { "Effect": "Allow", "Action": "pricing:DescribeServices", "Resource": "*" } ] }

You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that you're trying to perform.

Granting full access to the AWS Billing Conductor API

In this example, you grant an IAM user full only access to the AWS Billing Conductor API.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "billingconductor:*", "Resource": "*" }, { "Effect": "Allow", "Action": "organizations:ListAccounts", "Resource": "*" } ] }

Granting read only access to the AWS Billing Conductor console

In this example, you grant an IAM user read only access to the AWS Billing Conductor console.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "billingconductor:List*", "Resource": "*" }, { "Effect": "Allow", "Action": "organizations:ListAccounts", "Resource": "*" }, { "Effect": "Allow", "Action": "pricing:DescribeServices", "Resource": "*" } ] }

Granting AWS Billing Conductor access through the Billing console

In this example, IAM users can toggle and view pro forma billing data through the bills page in their Billing console.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "billing:ListBillingViews", "aws-portal:ViewBilling" ] "Resource": "*" } ] }

Granting AWS Billing Conductor access through AWS Cost and Usage Reports

In this example, IAM users can toggle and view pro forma billing data through the Cost and Usage Reports page in their Billing console.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "billing:ListBillingViews", "aws-portal:ViewBilling", "cur:DescribeReportDefinitions" ], "Resource": "*" } ] }

Granting AWS Billing Conductor access to the import organizational unit (OU) feature

In this example, IAM users have read-only access to the specific AWS Organizations APIs required to import your organizational unit accounts when you're creating a billing group. The import OU feature is on the AWS Billing Conductor console.

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "organizations:ListRoots", "organizations:ListOrganizationalUnitsForParent", "organizations:ListChildren" ], "Resource": "*" } ] }