# Security in AWS Billing Conductor Cloud security at AWS is the highest priority. As an AWS customer, you benefit from data centers and network architectures that are built to meet the requirements of the most security-sensitive organizations. Security is a shared responsibility between AWS and you. The [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) describes this as security *of* the cloud and security *in* the cloud: + **Security of the cloud** – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud. AWS also provides you with services that you can use securely. Third-party auditors regularly test and verify the effectiveness of our security as part of the [AWS Compliance Programs](https://aws.amazon.com/compliance/programs/). To learn about the compliance programs that apply to AWS Billing Conductor, see [AWS Services in Scope by Compliance Program](https://aws.amazon.com/compliance/services-in-scope/). + **Security in the cloud** – Your responsibility is determined by the AWS service that you use. You are also responsible for other factors including the sensitivity of your data, your company’s requirements, and applicable laws and regulations. This documentation helps you understand how to apply the shared responsibility model when using AWS Billing Conductor. The following topics show you how to configure AWS Billing Conductor to meet your security and compliance objectives. You also learn how to use other AWS services that help you to monitor and secure your AWS Billing Conductor resources. **Topics** + [Data protection in AWS Billing Conductor](data-protection.md) + [Identity and access management for AWS Billing Conductor](security-iam.md) + [Logging and monitoring in AWS Billing Conductor](billing-security-logging.md) + [Compliance validation for AWS Billing Conductor](compliance-validation.md) + [Resilience in AWS Billing Conductor](disaster-recovery-resiliency.md) + [Infrastructure Security in AWS Billing Conductor](infrastructure-security.md) # Data protection in AWS Billing Conductor The AWS [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) applies to data protection in . As described in this model, AWS is responsible for protecting the global infrastructure that runs all of the AWS Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. You are also responsible for the security configuration and management tasks for the AWS services that you use. For more information about data privacy, see the [Data Privacy FAQ](https://aws.amazon.com/compliance/data-privacy-faq/). For information about data protection in Europe, see the [AWS Shared Responsibility Model and GDPR](https://aws.amazon.com/blogs/security/the-aws-shared-responsibility-model-and-gdpr/) blog post on the *AWS Security Blog*. For data protection purposes, we recommend that you protect AWS account credentials and set up individual users with AWS IAM Identity Center or AWS Identity and Access Management (IAM). That way, each user is given only the permissions necessary to fulfill their job duties. We also recommend that you secure your data in the following ways: + Use multi-factor authentication (MFA) with each account. + Use SSL/TLS to communicate with AWS resources. We require TLS 1.2 and recommend TLS 1.3. + Set up API and user activity logging with AWS CloudTrail. For information about using CloudTrail trails to capture AWS activities, see [Working with CloudTrail trails](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-trails.html) in the *AWS CloudTrail User Guide*. + Use AWS encryption solutions, along with all default security controls within AWS services. + Use advanced managed security services such as Amazon Macie, which assists in discovering and securing sensitive data that is stored in Amazon S3. + If you require FIPS 140-3 validated cryptographic modules when accessing AWS through a command line interface or an API, use a FIPS endpoint. For more information about the available FIPS endpoints, see [Federal Information Processing Standard (FIPS) 140-3](https://aws.amazon.com/compliance/fips/). We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into tags or free-form text fields such as a **Name** field. This includes when you work with or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into tags or free-form text fields used for names may be used for billing or diagnostic logs. If you provide a URL to an external server, we strongly recommend that you do not include credentials information in the URL to validate your request to that server. # Identity and access management for AWS Billing Conductor AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be *authenticated* (signed in) and *authorized* (have permissions) to use Billing Conductor resources. IAM is an AWS service that you can use with no additional charge. **Topics** + [Audience](#security_iam_audience) + [Authenticating with identities](#security_iam_authentication) + [Managing access using policies](#security_iam_access-manage) + [How AWS Billing Conductor works with IAM](security_iam_service-with-iam.md) + [AWS Billing Conductor identity-based policy examples](security_iam_id-based-policy-examples.md) ## Audience How you use AWS Identity and Access Management (IAM) differs based on your role: + **Service user** - request permissions from your administrator if you cannot access features (see [Troubleshooting AWS Billing Conductor identity and access](security_iam_troubleshoot.md)) + **Service administrator** - determine user access and submit permission requests (see [How AWS Billing Conductor works with IAM](security_iam_service-with-iam.md)) + **IAM administrator** - write policies to manage access (see [AWS Billing Conductor identity-based policy examples](security_iam_id-based-policy-examples.md)) ## Authenticating with identities Authentication is how you sign in to AWS using your identity credentials. You must be authenticated as the AWS account root user, an IAM user, or by assuming an IAM role. You can sign in as a federated identity using credentials from an identity source like AWS IAM Identity Center (IAM Identity Center), single sign-on authentication, or Google/Facebook credentials. For more information about signing in, see [How to sign in to your AWS account](https://docs.aws.amazon.com/signin/latest/userguide/how-to-sign-in.html) in the *AWS Sign-In User Guide*. For programmatic access, AWS provides an SDK and CLI to cryptographically sign requests. For more information, see [AWS Signature Version 4 for API requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html) in the *IAM User Guide*. ### AWS account root user When you create an AWS account, you begin with one sign-in identity called the AWS account *root user* that has complete access to all AWS services and resources. We strongly recommend that you don't use the root user for everyday tasks. For tasks that require root user credentials, see [Tasks that require root user credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks) in the *IAM User Guide*. ### IAM users and groups An *[IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html)* is an identity with specific permissions for a single person or application. We recommend using temporary credentials instead of IAM users with long-term credentials. For more information, see [Require human users to use federation with an identity provider to access AWS using temporary credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp) in the *IAM User Guide*. An [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html) specifies a collection of IAM users and makes permissions easier to manage for large sets of users. For more information, see [Use cases for IAM users](https://docs.aws.amazon.com/IAM/latest/UserGuide/gs-identities-iam-users.html) in the *IAM User Guide*. ### IAM roles An *[IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)* is an identity with specific permissions that provides temporary credentials. You can assume a role by [switching from a user to an IAM role (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) or by calling an AWS CLI or AWS API operation. For more information, see [Methods to assume a role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*. IAM roles are useful for federated user access, temporary IAM user permissions, cross-account access, cross-service access, and applications running on Amazon EC2. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*. ## Managing access using policies You control access in AWS by creating policies and attaching them to AWS identities or resources. A policy defines permissions when associated with an identity or resource. AWS evaluates these policies when a principal makes a request. Most policies are stored in AWS as JSON documents. For more information about JSON policy documents, see [Overview of JSON policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#access_policies-json) in the *IAM User Guide*. Using policies, administrators specify who has access to what by defining which **principal** can perform **actions** on what **resources**, and under what **conditions**. By default, users and roles have no permissions. An IAM administrator creates IAM policies and adds them to roles, which users can then assume. IAM policies define permissions regardless of the method used to perform the operation. ### Identity-based policies Identity-based policies are JSON permissions policy documents that you attach to an identity (user, group, or role). These policies control what actions identities can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*. Identity-based policies can be *inline policies* (embedded directly into a single identity) or *managed policies* (standalone policies attached to multiple identities). To learn how to choose between managed and inline policies, see [Choose between managed policies and inline policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-choosing-managed-or-inline.html) in the *IAM User Guide*. ### Resource-based policies Resource-based policies are JSON policy documents that you attach to a resource. Examples include IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Resource-based policies are inline policies that are located in that service. You can't use AWS managed policies from IAM in a resource-based policy. ### Access control lists (ACLs) Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format. Amazon S3, AWS WAF, and Amazon VPC are examples of services that support ACLs. To learn more about ACLs, see [Access control list (ACL) overview](https://docs.aws.amazon.com/AmazonS3/latest/userguide/acl-overview.html) in the *Amazon Simple Storage Service Developer Guide*. ### Other policy types AWS supports additional policy types that can set the maximum permissions granted by more common policy types: + **Permissions boundaries** – Set the maximum permissions that an identity-based policy can grant to an IAM entity. For more information, see [Permissions boundaries for IAM entities](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) in the *IAM User Guide*. + **Service control policies (SCPs)** – Specify the maximum permissions for an organization or organizational unit in AWS Organizations. For more information, see [Service control policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) in the *AWS Organizations User Guide*. + **Resource control policies (RCPs)** – Set the maximum available permissions for resources in your accounts. For more information, see [Resource control policies (RCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html) in the *AWS Organizations User Guide*. + **Session policies** – Advanced policies passed as a parameter when creating a temporary session for a role or federated user. For more information, see [Session policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session) in the *IAM User Guide*. ### Multiple policy types When multiple types of policies apply to a request, the resulting permissions are more complicated to understand. To learn how AWS determines whether to allow a request when multiple policy types are involved, see [Policy evaluation logic](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html) in the *IAM User Guide*. # How AWS Billing Conductor works with IAM Before you use IAM to manage access to Billing Conductor, you should understand what IAM features are available to use with Billing Conductor. To get a high-level view of how Billing Conductor and other AWS services work with IAM, see [AWS Services That Work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*. **Topics** + [Billing Conductor identity-based policies](#security_iam_service-with-iam-id-based-policies) + [Billing Conductor resource-based policies](#security_iam_service-with-iam-resource-based-policies) + [Access control lists (ACLs)](#security_iam_service-with-iam-acls) + [Authorization based on Billing Conductor tags](#security_iam_service-with-iam-tags) + [Billing Conductor IAM roles](#security_iam_service-with-iam-roles) ## Billing Conductor identity-based policies With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. Billing Conductor supports specific actions, resources, and condition keys. To learn about all of the elements that you use in a JSON policy, see [IAM JSON Policy Elements Reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) in the *IAM User Guide*. ### Actions Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Action` element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Include actions in a policy to grant permissions to perform the associated operation. Policy actions in Billing Conductor use the following prefix before the action: `Billing Conductor:`. For example, to grant someone permission to run an Amazon EC2 instance with the Amazon EC2 `RunInstances` API operation, you include the `ec2:RunInstances` action in their policy. Policy statements must include either an `Action` or `NotAction` element. Billing Conductor defines its own set of actions that describe tasks that you can perform with this service. To specify multiple actions in a single statement, separate them with commas as follows: ``` "Action": [ "ec2:action1", "ec2:action2" ``` You can specify multiple actions using wildcards (\$1). For example, to specify all actions that begin with the word `Describe`, include the following action: ``` "Action": "ec2:Describe*" ``` To see a list of Billing Conductor actions, see [Actions Defined by AWS Billing Conductor](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsbillingconductor.html#awsbillingconductor-actions-as-permissions) in the *IAM User Guide*. ### Resources Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Resource` JSON policy element specifies the object or objects to which the action applies. As a best practice, specify a resource using its [Amazon Resource Name (ARN)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (\$1) to indicate that the statement applies to all resources. ``` "Resource": "*" ``` The Amazon EC2 instance resource has the following ARN: ``` arn:${Partition}:ec2:${Region}:${Account}:instance/${InstanceId} ``` For more information about the format of ARNs, see [Amazon Resource Names (ARNs) and AWS Service Namespaces](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html). For example, to specify the `i-1234567890abcdef0` instance in your statement, use the following ARN: ``` "Resource": "arn:aws:ec2:us-east-1:123456789012:instance/i-1234567890abcdef0" ``` To specify all instances that belong to a specific account, use the wildcard (\$1): ``` "Resource": "arn:aws:ec2:us-east-1:123456789012:instance/*" ``` Some Billing Conductor actions, such as those for creating resources, cannot be performed on a specific resource. In those cases, you must use the wildcard (\$1). ``` "Resource": "*" ``` Many Amazon EC2 API actions involve multiple resources. For example, `AttachVolume` attaches an Amazon EBS volume to an instance, so an IAM user must have permissions to use the volume and the instance. To specify multiple resources in a single statement, separate the ARNs with commas. ``` "Resource": [ "resource1", "resource2" ``` To see a list of Billing Conductor resource types and their ARNs, see [Resources Defined by AWS Billing Conductor](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsbillingconductor.html#awsbillingconductor-resources-for-iam-policies) in the *IAM User Guide*. To learn with which actions you can specify the ARN of each resource, see [Actions Defined by AWS Billing Conductor](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsbillingconductor.html#awsbillingconductor-actions-as-permissions). ### Condition keys Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**. The `Condition` element specifies when statements execute based on defined criteria. You can create conditional expressions that use [condition operators](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), such as equals or less than, to match the condition in the policy with values in the request. To see all AWS global condition keys, see [AWS global condition context keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*. Billing Conductor defines its own set of condition keys and also supports using some global condition keys. To see all AWS global condition keys, see [AWS Global Condition Context Keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*. All Amazon EC2 actions support the `aws:RequestedRegion` and `ec2:Region` condition keys. For more information, see [Example: Restricting Access to a Specific Region](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ExamplePolicies_EC2.html#iam-example-region). To see a list of Billing Conductor condition keys, see [Condition Keys for AWS Billing Conductor](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsbillingconductor.html#awsbillingconductor-policy-keys) in the *IAM User Guide*. To learn with which actions and resources you can use a condition key, see [Actions Defined by AWS Billing Conductor](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awsbillingconductor.html#awsbillingconductor-actions-as-permissions). ### Examples To view examples of Billing Conductor identity-based policies, see [AWS Billing Conductor identity-based policy examples](security_iam_id-based-policy-examples.md). ## Billing Conductor resource-based policies Resource-based policies are JSON policy documents that specify what actions a specified principal can perform on the Billing Conductor resource and under what conditions. Amazon S3 supports resource-based permissions policies for Amazon S3 *buckets*. Resource-based policies let you grant usage permission to other accounts on a per-resource basis. You can also use a resource-based policy to allow an AWS service to access your Amazon S3 *buckets*. To enable cross-account access, you can specify an entire account or IAM entities in another account as the [principal in a resource-based policy](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html). Adding a cross-account principal to a resource-based policy is only half of establishing the trust relationship. When the principal and the resource are in different AWS accounts, you must also grant the principal entity permission to access the resource. Grant permission by attaching an identity-based policy to the entity. However, if a resource-based policy grants access to a principal in the same account, no additional identity-based policy is required. For more information, see [How IAM Roles Differ from Resource-based Policies ](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_compare-resource-policies.html)in the *IAM User Guide*. The Amazon S3 service supports only one type of resource-based policy called a **bucket* policy*, which is attached to a *bucket*. This policy defines which principal entities (accounts, users, roles, and federated users) can perform actions on the *Billing Conductor*. ### Examples To view examples of Billing Conductor resource-based policies, see [AWS Billing Conductor resource-based policy examples](security_iam_resource-based-policy-examples.md), ## Access control lists (ACLs) Access control lists (ACLs) are lists of grantees that you can attach to resources. They grant accounts permissions to access the resource to which they are attached. You can attach ACLs to an Amazon S3 *bucket* resource. With Amazon S3 access control lists (ACLs), you can manage access to *bucket* resources. Each *bucket* has an ACL attached to it as a subresource. It defines which AWS accounts, IAM users or groups of users, or IAM roles are granted access and the type of access. When a request is received for a resource, AWS checks the corresponding ACL to verify that the requester has the necessary access permissions. When you create a *bucket* resource, Amazon S3 creates a default ACL that grants the resource owner full control over the resource. In the following example *bucket* ACL, John Doe is listed as the owner of the *bucket* and is granted full control over that *bucket*. An ACL can have up to 100 grantees. ``` c1daexampleaaf850ea79cf0430f33d72579fd1611c97f7ded193374c0b163b6 john-doe c1daexampleaaf850ea79cf0430f33d72579fd1611c97f7ded193374c0b163b6 john-doe FULL_CONTROL ``` The ID field in the ACL is the AWS account canonical user ID. To learn how to view this ID in an account that you own, see [Finding an AWS Account Canonical User ID](https://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html#FindingCanonicalId). ## Authorization based on Billing Conductor tags You can attach tags to Billing Conductor resources or pass tags in a request to Billing Conductor. To control access based on tags, you provide tag information in the [condition element](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) of a policy using the `Billing Conductor:ResourceTag/key-name`, `aws:RequestTag/key-name`, or `aws:TagKeys` condition keys. ## Billing Conductor IAM roles An [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) is an entity within your AWS account that has specific permissions. ### Using temporary credentials with Billing Conductor You can use temporary credentials to sign in with federation, assume an IAM role, or to assume a cross-account role. You obtain temporary security credentials by calling AWS STS API operations such as [AssumeRole](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html) or [GetFederationToken](https://docs.aws.amazon.com/STS/latest/APIReference/API_GetFederationToken.html). Billing Conductor supports using temporary credentials. ### Service-linked roles [Service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role) allow AWS services to access resources in other services to complete an action on your behalf. Service-linked roles appear in your IAM account and are owned by the service. An IAM administrator can view but not edit the permissions for service-linked roles. ### Service roles This feature allows a service to assume a [service role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-role) on your behalf. This role allows the service to access resources in other services to complete an action on your behalf. Service roles appear in your IAM account and are owned by the account. This means that an IAM administrator can change the permissions for this role. However, doing so might break the functionality of the service. Billing Conductor supports service roles. ### Choosing an IAM role in Billing Conductor When you create a resource in Billing Conductor, you must choose a role to allow Billing Conductor to access Amazon EC2 on your behalf. If you have previously created a service role or service-linked role, then Billing Conductor provides you with a list of roles to choose from. It's important to choose a role that allows access to start and stop Amazon EC2 instances. # AWS Billing Conductor identity-based policy examples By default, IAM users and roles don't have permission to create or modify 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html#access_policies_create-json-editor) in the *IAM User Guide*. **Topics** + [Policy best practices](#security_iam_service-with-iam-policy-best-practices) + [Billing Conductor identity-based policy examples](#security_policy-examples) + [AWS managed policies for AWS Billing Conductor](security-iam-awsmanpol.md) + [AWS Billing Conductor resource-based policy examples](security_iam_resource-based-policy-examples.md) + [Troubleshooting AWS Billing Conductor identity and access](security_iam_troubleshoot.md) ## Policy best practices Identity-based policies determine whether someone can create, access, or delete 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 with AWS managed policies and move toward least-privilege permissions** – To get started granting permissions to your users and workloads, use the *AWS managed policies* that grant permissions for many common use cases. They are available in your AWS account. We recommend that you reduce permissions further by defining AWS customer managed policies that are specific to your use cases. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) or [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*. + **Apply least-privilege permissions** – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by defining the actions that can be taken on specific resources under specific conditions, also known as *least-privilege permissions*. For more information about using IAM to apply permissions, see [ Policies and permissions in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*. + **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*. + **Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions** – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see [Validate policies with IAM Access Analyzer](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-policy-validation.html) in the *IAM User Guide*. + **Require multi-factor authentication (MFA)** – If you have a scenario that requires IAM users or a root user in your AWS account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see [ Secure API access with MFA](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_configure-api-require.html) in the *IAM User Guide*. For more information about best practices in IAM, see [Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*. ## 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. **Topics** + [Granting full access to the Billing Conductor console](#security_iam_id-based-policy-examples-console) + [Granting full access to the Billing Conductor API](#security_iam_id-based-policy-examples-fullAPI) + [Granting read-only access to the Billing Conductor console](#security_iam_id-based-policy-examples-readonly) + [Granting Billing Conductor access through the AWS Billing console](#security_iam_id-based-policy-examples-ABCthroughbilling) + [Granting Billing Conductor access through AWS Cost and Usage Reports](#security_iam_id-based-policy-examples-ABCthroughCUR) + [Granting Billing Conductor access to the import organizational unit feature](#security_iam_id-based-policy-examples-ABCaccessOU) + [Denying AWS Billing and Cost Explorer access to services and features that don't support pro forma costs](#deny-access-proforma-costs) + [Creating a pro forma CUR by billing group](#allow-legacy-cur) ### Granting full access to the Billing Conductor console To access the Billing Conductor console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the 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 Billing Conductor console, also attach the following AWS managed policy to the entities. For more information, see [Adding Permissions to a user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) 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. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "billingconductor:*", "Resource": "*" }, { "Effect": "Allow", "Action": [ "organizations:ListAccounts", "organizations:DescribeAccount" ], "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 Billing Conductor API In this example, you grant an IAM entity full access to the Billing Conductor API. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "billingconductor:*", "Resource": "*" }, { "Effect": "Allow", "Action": "organizations:ListAccounts", "Resource": "*" } ] } ``` ------ ### Granting read-only access to the Billing Conductor console In this example, you grant an IAM entity read-only access to the Billing Conductor console. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "billingconductor:List*", "Resource": "*" }, { "Effect": "Allow", "Action": "organizations:ListAccounts", "Resource": "*" }, { "Effect": "Allow", "Action": "pricing:DescribeServices", "Resource": "*" } ] } ``` ------ ### Granting Billing Conductor access through the AWS Billing console In this example, IAM entities can toggle and view pro forma billing data through the bills page in their AWS Billing console. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "billing:ListBillingViews", "aws-portal:ViewBilling" ], "Resource": "*" } ] } ``` ------ ### Granting Billing Conductor access through AWS Cost and Usage Reports In this example, IAM entities can toggle and view pro forma billing data through the Cost and Usage Reports page in their AWS Billing console. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "billing:ListBillingViews", "aws-portal:ViewBilling", "cur:DescribeReportDefinitions" ], "Resource": "*" } ] } ``` ------ ### Granting Billing Conductor access to the import organizational unit feature In this example, IAM entities have read-only access to the specific AWS Organizations API operations that are required to import your organizational unit (OU) accounts when you're creating a billing group. The import OU feature is on the AWS Billing Conductor console. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "organizations:ListRoots", "organizations:ListOrganizationalUnitsForParent", "organizations:ListChildren" ], "Resource": "*" } ] } ``` ------ ### Denying AWS Billing and Cost Explorer access to services and features that don't support pro forma costs In this example, IAM entities are denied access to services and features that don't support pro forma costs. This policy includes a list of actions that are possible within the management account and individual member accounts. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [{ "Effect": "Deny", "Action": [ "aws-portal:ModifyAccount", "aws-portal:ModifyBilling", "aws-portal:ModifyPaymentMethods", "aws-portal:ViewPaymentMethods", "aws-portal:ViewAccount", "cur:GetClassic*", "cur:Validate*", "tax:List*", "tax:Get*", "tax:Put*", "tax:ListTaxRegistrations", "tax:BatchPut*", "tax:UpdateExemptions", "freetier:Get*", "payments:Get*", "payments:List*", "payments:Update*", "payments:GetPaymentInstrument", "payments:GetPaymentStatus", "purchase-orders:ListPurchaseOrders", "purchase-orders:ListPurchaseOrderInvoices", "consolidatedbilling:GetAccountBillingRole", "consolidatedbilling:Get*", "consolidatedbilling:List*", "invoicing:List*", "invoicing:Get*", "account:Get*", "account:List*", "account:CloseAccount", "account:DisableRegion", "account:EnableRegion", "account:GetContactInformation", "account:GetAccountInformation", "account:PutContactInformation", "billing:GetBillingPreferences", "billing:GetContractInformation", "billing:GetCredits", "billing:RedeemCredits", "billing:Update*", "ce:GetPreferences", "ce:UpdatePreferences", "ce:GetReservationCoverage", "ce:GetReservationPurchaseRecommendation", "ce:GetReservationUtilization", "ce:GetSavingsPlansCoverage", "ce:GetSavingsPlansPurchaseRecommendation", "ce:GetSavingsPlansUtilization", "ce:GetSavingsPlansUtilizationDetails", "ce:ListSavingsPlansPurchaseRecommendationGeneration", "ce:StartSavingsPlansPurchaseRecommendationGeneration", "ce:UpdateNotificationSubscription" ], "Resource": "*" }] } ``` ------ For more information, see [AWS services that support pro forma-based billing view costs](service-integrations-support-proforma.md). ### Creating a pro forma CUR by billing group Step 1: Allow IAM users to have full access to legacy CUR and billing group billing view. ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "CurDataAccess", "Effect": "Allow", "Action": "cur:PutReportDefinition", "Resource": [ "arn:*:cur:*:*:definition/*", "arn:aws:billing::*:billingview/*" ] } ] } ``` Step 2: To assign IAM roles to have access to specific billing groups, add the billing view ARN the user can access. ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "CurDataAccess", "Effect": "Allow", "Action": "cur:PutReportDefinition", "Resource":[ "arn:aws:cur:us-east-1:123456789012:definition/*", "arn:aws:billing::AWS-account-ID:billingview/billing-group-$billinggroup-primary-account-ID" ] } ] } ``` For more information, see [Configuring Cost and Usage Reports by billing group](configuring-abc.md). # AWS managed policies for AWS Billing Conductor To add permissions to users, groups, and roles, it is easier to use AWS managed policies than to write policies yourself. It takes time and expertise to [create IAM customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html) that provide your team with only the permissions they need. To get started quickly, you can use our AWS managed policies. These policies cover common use cases and are available in your AWS account. For more information about AWS managed policies, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) in the *IAM User Guide*. AWS services maintain and update AWS managed policies. You can't change the permissions in AWS managed policies. Services occasionally add additional permissions to an AWS managed policy to support new features. This type of update affects all identities (users, groups, and roles) where the policy is attached. Services are most likely to update an AWS managed policy when a new feature is launched or when new operations become available. Services do not remove permissions from an AWS managed policy, so policy updates won't break your existing permissions. Additionally, AWS supports managed policies for job functions that span multiple services. For example, the **ReadOnlyAccess** AWS managed policy provides read-only access to all AWS services and resources. When a service launches a new feature, AWS adds read-only permissions for new operations and resources. For a list and descriptions of job function policies, see [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*. ## AWS managed policy: AWSBillingConductorFullAccess The AWSBillingConductorFullAccess managed policy grants complete access to AWS Billing Conductor console and APIs. Users can list, create, and delete AWS Billing Conductor resources. To view the permissions for this policy, see [AWSBillingConductorFullAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSBillingConductorFullAccess.html) in the *AWS Managed Policy Reference*. ## AWS managed policy: AWSBillingConductorReadOnlyAccess The AWSBillingConductorReadOnlyAccess managed policy grants read-only access to AWS Billing Conductor console and APIs. Users can view and list all AWS Billing Conductor resources. Users can't create or delete resources. To view the permissions for this policy, see [AWSBillingConductorReadOnlyAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSBillingConductorReadOnlyAccess.html) in the *AWS Managed Policy Reference*. ## AWS Billing Conductor updates to AWS managed policies View details about updates to AWS managed policies for AWS Billing Conductor since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the AWS Billing Conductor Document history page. | Change | Description | Date | | --- | --- | --- | | [AWSBillingConductorFullAccess](#security-iam-awsmanpol-fullaccess) - Update to existing policies | We added the `organizations:DescribeResponsibilityTransfer` and `organizations:ListInboundResponsibilityTransfers` actions to the `AWSBillingConductorFullAccess` policy. | November 19, 2025 | | [AWSBillingConductorFullAccess](#security-iam-awsmanpol-fullaccess) - Update to existing policies | We added the following actions to the `AWSBillingConductorFullAccess` policy: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/billingconductor/latest/userguide/security-iam-awsmanpol.html) | September 9, 2025 | | [AWSBillingConductorReadOnlyAccess](#security-iam-awsmanpol-readonly) - Update to existing policies | We added the following actions to the `AWSBillingConductorReadOnlyAccess` policy: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/billingconductor/latest/userguide/security-iam-awsmanpol.html) | September 9, 2025 | | AWSBillingConductorReadOnlyAccess | Added `GetBillingGroupCostReport` to the `AWSBillingConductorReadOnlyAccess` policy. | February 8, 2024 | | AWSBillingConductorFullAccess | Created policy | March 29, 2022 | | AWSBillingConductorReadOnlyAccess | Created policy | March 29, 2022 | | AWS Billing Conductor change log published | AWS Billing Conductor started tracking changes for its AWS managed policies. | March 29, 2022 | # AWS Billing Conductor resource-based policy examples **Topics** + [Restricting Amazon S3 bucket access to specific IP addresses](#security_iam_resource-based-policy-examples-restrict-bucket-by-ip) ## Restricting Amazon S3 bucket access to specific IP addresses The following example grants permissions to any user to perform any Amazon S3 operations on objects in the specified bucket. However, the request must originate from the range of IP addresses specified in the condition. The condition in this statement identifies the 54.240.143.\$1 range of allowed Internet Protocol version 4 (IPv4) IP addresses, with one exception: 54.240.143.188. The `Condition` block uses the `IpAddress` and `NotIpAddress` conditions and the `aws:SourceIp` condition key, which is an AWS wide condition key. For more information about these condition keys, see [Specifying Conditions in a Policy](https://docs.aws.amazon.com/AmazonS3/latest/userguide/amazon-s3-policy-keys.html). The`aws:sourceIp` IPv4 values use the standard CIDR notation. For more information, see [IP Address Condition Operators](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html#Conditions_IPAddress) in the *IAM User Guide*. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Id": "S3PolicyId1", "Statement": [ { "Sid": "IPAllow", "Effect": "Allow", "Principal": "*", "Action": "s3:*", "Resource": "arn:aws:s3:::amzn-s3-demo-bucket1/*", "Condition": { "IpAddress": {"aws:SourceIp": "54.240.143.0/24"}, "NotIpAddress": {"aws:SourceIp": "54.240.143.188/32"} } } ] } ``` ------ # Troubleshooting AWS Billing Conductor identity and access Use the following information to help you diagnose and fix common issues that you might encounter when working with Billing Conductor and IAM. **Topics** + [I am not authorized to perform an action in Billing Conductor](#security_iam_troubleshoot-no-permissions) + [I am not authorized to perform iam:PassRole](#security_iam_troubleshoot-passrole) + [I want to allow people outside of my AWS account to access my Billing Conductor resources](#security_iam_troubleshoot-cross-account-access) ## I am not authorized to perform an action in Billing Conductor If the AWS Management Console tells you that you're not authorized to perform an action, then you must contact your administrator for assistance. Your administrator is the person that provided you with your user name and password. The following example error occurs when the `mateojackson` IAM user tries to use the console to view details about a *Billing Conductor* but does not have `Billing Conductor:GetWidget` permissions. ``` User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: Billing Conductor:GetWidget on resource: my-example-Billing Conductor ``` In this case, Mateo asks his administrator to update his policies to allow him to access the `my-example-Billing Conductor` resource using the `Billing Conductor:GetWidget` action. ## I am not authorized to perform iam:PassRole If you receive an error that you're not authorized to perform the `iam:PassRole` action, your policies must be updated to allow you to pass a role to Billing Conductor. Some AWS services allow you to pass an existing role to that service instead of creating a new service role or service-linked role. To do this, you must have permissions to pass the role to the service. The following example error occurs when an IAM user named `marymajor` tries to use the console to perform an action in Billing Conductor. However, the action requires the service to have permissions that are granted by a service role. Mary does not have permissions to pass the role to the service. ``` User: arn:aws:iam::123456789012:user/marymajor is not authorized to perform: iam:PassRole ``` In this case, Mary's policies must be updated to allow her to perform the `iam:PassRole` action. If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials. ## I want to allow people outside of my AWS account to access my Billing Conductor resources You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources. To learn more, consult the following: + To learn whether Billing Conductor supports these features, see [How AWS Billing Conductor works with IAM](security_iam_service-with-iam.md). + To learn how to provide access to your resources across AWS accounts that you own, see [Providing access to an IAM user in another AWS account that you own](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_aws-accounts.html) in the *IAM User Guide*. + To learn how to provide access to your resources to third-party AWS accounts, see [Providing access to AWS accounts owned by third parties](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html) in the *IAM User Guide*. + To learn how to provide access through identity federation, see [Providing access to externally authenticated users (identity federation)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_federated-users.html) in the *IAM User Guide*. + To learn the difference between using roles and resource-based policies for cross-account access, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*. # Logging and monitoring in AWS Billing Conductor Monitoring is an important part of maintaining the reliability, availability, and performance of your AWS account. There are several tools available to monitor your AWS Billing Conductor usage. ## AWS Cost and Usage Reports AWS Cost and Usage Reports tracks your AWS usage and provides estimated charges associated with your account. Each report contains line items for each unique combination of AWS products, usage type, and operation that you use in your AWS account. You can customize the AWS Cost and Usage Reports to aggregate the information either by the hour or by the day. For more information about AWS Cost and Usage Reports, see the [https://docs.aws.amazon.com/cur/latest/userguide/what-is-cur.html](https://docs.aws.amazon.com/cur/latest/userguide/what-is-cur.html). # Logging AWS Billing Conductor API calls using AWS CloudTrail AWS Billing Conductor is integrated with AWS CloudTrail, a service that provides a record of actions taken by a user, role, or an AWS service in AWS Billing Conductor. CloudTrail captures all API calls for AWS Billing Conductor as events. The calls captured include calls from the AWS Billing Conductor console and code calls to the AWS Billing Conductor API operations. If you create a trail, you can enable continuous delivery of CloudTrail events to an Amazon S3 bucket, including events for AWS Billing Conductor. If you don't configure a trail, you can still view the most recent events in the CloudTrail console in **Event history**. Using the information collected by CloudTrail, you can determine the request that was made to AWS Billing Conductor, the IP address from which the request was made, who made the request, when it was made, and additional details. To learn more about CloudTrail, see the [AWS CloudTrail User Guide](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-user-guide.html). ## AWS Billing Conductor CloudTrail events This section shows a full list of the CloudTrail events related to Billing and Cost Management. **** | Event name | Definition | | --- | --- | | `AssociateAccounts` | Logs the association of accounts to a billing group. | | `AssociatePricingRules` | Logs the association of pricing rules to a pricing plan. | | `AutoAssociateAccount` | Logs the automatic association of an account to a billing group. | | `AutoDisassociateAccount` | Logs the automatic disassociation of an account from a billing group in the next billing period. | | `BatchAssociateResourcesToCustomLineItem` | Logs the batch association of resources to a percentage custom line item. | | `BatchDisassociateResourcesFromCustomLineItem` | Logs the batch disassociation of resources from a percentage custom line item. | | `CreateBillingGroup` | Logs the creation of a billing group. | | `CreateCustomLineItem` | Logs the creation of a custom line item. | | `CreatePricingPlan` | Logs the creation of a pricing plan. | | `CreatePricingRule` | Logs the creation of a pricing rule. | | `DeleteBillingGroup` | Logs the deletion of a billing group. | | `DeleteCustomLineItem` | Logs the deletion of a custom line item. | | `DeletePricingPlan` | Logs the deletion of a pricing plan. | | `DeletePricingRule` | Logs the deletion of a pricing rule. | | `DisassociateAccounts` | Logs the disassociation of accounts from a billing group. | | `DisassociatePricingRules` | Logs the disassociation of pricing rules from a pricing plan. | | `ListAccountAssociations` | Logs the access to the account ids in the billing group. | | `ListBillingGroupCostReports` | Logs the access to the actual AWS charges for the billing group. | | `ListBillingGroups` | Logs the access to the billing groups in a billing period. | | `ListCustomLineItems` | Logs the access to the custom line items in a billing period. | | `ListCustomLineItemVersions` | Logs the access to the versions of a custom line item. | | `ListPricingPlans` | Logs the access to the pricing plans in a billing period. | | `ListPricingPlansAssociatedWithPricingRule` | Logs the access to the pricing plans associated to a pricing rule. | | `ListPricingRules` | Logs the access to the pricing rules in a billing period. | | `ListPricingRulesAssociatedToPricingPlan` | Logs the access to the pricing rules associated to a pricing plan. | | `ListResourcesAssociatedToCustomLineItem` | Logs the access to the resources associated to a custom line item. | | `ListTagsForResource` | Logs the access to the tags on a resource. | | `TagResource` | Logs the association of tags on a resource. | | `UpdateBillingGroup` | Logs the update of a billing group. | | `UpdateCustomLineItem` | Logs the update of a custom line item. | | `UpdatePricingPlan` | Logs the update of a pricing plan. | | `UpdatePricingRule` | Logs the update of a pricing rule. | ## AWS Billing Conductor information in CloudTrail CloudTrail is enabled on your AWS account when you create the account. When activity occurs in AWS Billing Conductor, that activity is recorded in a CloudTrail event along with other AWS service events in **Event history**. You can view, search, and download recent events in your AWS account. For more information, see [Viewing events with CloudTrail Event history](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/view-cloudtrail-events.html). For an ongoing record of events in your AWS account, including events for AWS Billing Conductor, create a trail. A *trail* enables CloudTrail to deliver log files to an Amazon S3 bucket. By default, when you create a trail in the console, the trail applies to all AWS Regions. The trail logs events from all Regions in the AWS partition and delivers the log files to the Amazon S3 bucket that you specify. Additionally, you can configure other AWS services to further analyze and act upon the event data collected in CloudTrail logs. For more information, see the following: + [Overview for creating a trail](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-create-and-update-a-trail.html) + [CloudTrail supported services and integrations](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-aws-service-specific-topics.html) + [Configuring Amazon SNS notifications for CloudTrail](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/configure-sns-notifications-for-cloudtrail.html) + [Receiving CloudTrail log files from multiple regions](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html) and [Receiving CloudTrail log files from multiple accounts](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-receive-logs-from-multiple-accounts.html) All AWS Billing Conductor actions are logged by CloudTrail and are documented in the [AWS Billing Conductor API Reference](https://docs.aws.amazon.com/billingconductor/latest/APIReference). Every event or log entry contains information about who generated the request. The identity information helps you determine the following: + Whether the request was made with root or AWS Identity and Access Management (IAM) user credentials. + Whether the request was made with temporary security credentials for a role or federated user. + Whether the request was made by another AWS service. For more information, see the [CloudTrail userIdentity element](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-event-reference-user-identity.html). ## Understanding AWS Billing Conductor log file entries A trail is a configuration that enables delivery of events as log files to an Amazon S3 bucket that you specify. CloudTrail log files contain one or more log entries. An event represents a single request from any source and includes information about the requested action, the date and time of the action, request parameters, and so on. CloudTrail log files aren't an ordered stack trace of the public API calls, so they don't appear in any specific order. **Topics** + [AutoAssociateAccount](#CT-example-auto) + [CreateBillingGroup](#CT-example-create) ### AutoAssociateAccount The following example shows a CloudTrail log entry that demonstrates the `AutoAssociateAccount` action. ``` { "eventVersion": "1.09", "userIdentity": { "accountId": "111122223333", "invokedBy": "billingconductor.amazonaws.com" }, "eventTime": "2024-02-23T00:22:08Z", "eventSource": "billingconductor.amazonaws.com", "eventName": "AutoAssociateAccount", "awsRegion": "us-east-1", "sourceIPAddress": "billingconductor.amazonaws.com", "userAgent": "billingconductor.amazonaws.com", "requestParameters": null, "responseElements": null, "requestID": "1v14d239-fe63-4d2b-b3cd-450905b6c33", "eventID": "14536982-geff-4fe8-bh18-f18jde35218d0", "readOnly": false, "eventType": "AwsServiceEvent", "managementEvent": true, "recipientAccountId": "111122223333", "serviceEventDetails": { "requestParameters": { "Arn": "arn:aws:billingconductor::111122223333:billinggroup/444455556666", "AccountIds": [ "333333333333" ] }, "responseElements": { "Arn": "arn:aws:billingconductor::111122223333:billinggroup/444455556666" } }, "eventCategory": "Management" } ``` ### CreateBillingGroup The following example shows a CloudTrail log entry that demonstrates the `CreateBillingGroup` action. ``` { "eventVersion": "1.08", "userIdentity": { "accountId":"111122223333", "accessKeyId":"ASIAIOSFODNN7EXAMPLE" }, "eventTime": "2024-01-24T20:30:03Z", "eventSource": "billingconductor.amazonaws.com", "eventName": "CreateBillingGroup", "awsRegion": "us-east-1", "sourceIPAddress": "100.100.10.10", "userAgent": "aws-internal/3 aws-sdk-java/1.11.465 Linux/4.9.124-0.1.ac.198.73.329.metal1.x86_64 OpenJDK_64-Bit_Server_VM/25.192-b12 java/1.8.0_192", "requestParameters": { "PrimaryAccountId": "444455556666", "ComputationPreference": { "PricingPlanArn": "arn:aws:billingconductor::111122223333:pricingplan/TqeITi5Bgh" }, "X-Amzn-Client-Token": "32aafb5s-e5b6-47f5-9795-3a69935e9da4", "AccountGrouping": { "LinkedAccountIds": [ "444455556666", "111122223333" ] }, "Name": "***" }, "responseElements": { "Access-Control-Expose-Headers": "x-amzn-RequestId,x-amzn-ErrorType,x-amzn-ErrorMessage,Date", "Arn": "arn:aws:billingconductor::111122223333:billinggroup/444455556666" }, "requestID": "fb26ae47-3510-a833-98fe-3dc0f602gb49", "eventID": "3ab70d86-c63e-46fd8d-a33s-ce2970441a8", "readOnly": false, "eventType": "AwsApiCall", "managementEvent": true, "recipientAccountId": "111122223333", "eventCategory": "Management" } ``` # Using Amazon EventBridge with AWS Billing Conductor AWS Billing Conductor is integrated with Amazon EventBridge, an event bus service that you can use to connect your applications with data from a variety of sources. For more information, see the [https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.html). You can use Amazon EventBridge to receive AWS Billing Conductor events. Then, based on rules that you create, Amazon EventBridge invokes one or more target actions when an event matches the values that you specify in a rule. Depending on the type of event, you can capture event information, send notifications, or perform other actions. To set up an Amazon EventBridge rule for AWS Billing Conductor events, see [Create a rule in Amazon EventBridge](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-get-started.html#eb-gs-create-rule) in the *Amazon EventBridge User Guide*. ## Example: Amazon EventBridge event for AWS Billing Conductor AWS Billing Conductor emits a daily summary event with the `Billing Group Configuration Recommended for Billing Transfer` detail type when a billing transfer is accepted but no corresponding billing group is configured, or when a billing group associated with an active billing transfer is deleted. When a billing transfer is accepted, we recommend configuring a billing group for the bill source account's organization, which enables accounts in that organization to access pro forma cost data in Billing and Cost Management tools. Without a billing group, usage data remains available through CloudWatch, but configuring a billing group makes it easier for bill source account administrators to monitor costs, such as through budgets configuration. **Note** This event type is currently only supported in the US East (N. Virginia) Region (`us-east-1`). The following is a generalized example of this event. You can subscribe to Amazon EventBridge events (such as this one) using AWS User Notifications. ``` { "account": "", // 12-digit account ID "region": "us-east-1", // Currently only us-east-1 is supported "detail-type": "Billing Group Configuration Recommended for Billing Transfer", "source": "aws.billingconductor", "version": "0", "time": "", // Format: yyyy-MM-dd'T'HH:mm:ssZ "id": "", // alphanumeric string "resources": [], "detail": { "targetDate": "", // Format: yyyy-MM-dd "recipientId": "", // 12-digit recipient account ID "eventBridgeEventId": "", // unique event identifier "directTransfersAccepted": [ { "transferArn": "", // ARN of the one-level billing transfer "billSourceAccountId": "", // 12-digit bill source account ID "effectiveTimestamp": "", // Format: yyyy-MM-dd'T'HH:mm:ssZ "acceptedTimestamp": "" // Format: yyyy-MM-dd'T'HH:mm:ssZ } ], "indirectTransfersAccepted": [ { "receiverTransferTransferArn": "", // ARN of the receiver's transfer "transferBillSourceTransferArn": "", // ARN of the bill source's transfer "billTransferAccountId": "", // 12-digit bill transfer account ID "billSourceAccountId": "", // 12-digit bill source account ID "effectiveTimestamp": "", // Format: yyyy-MM-dd'T'HH:mm:ssZ "acceptedTimestamp": "" // Format: yyyy-MM-dd'T'HH:mm:ssZ } ], "directBillingGroupsDeleted": [ { "billingGroupArn": "", // ARN of the deleted billing group "billSourceAccountId": "", // 12-digit bill source account ID "transferId": "", // associated transfer ID "deletedTimestamp": "" // Format: yyyy-MM-dd'T'HH:mm:ssZ } ], "indirectBillingGroupsDeleted": [ { "billingGroupArn": "", // ARN of the deleted billing group "billTransferAccountId": "", // 12-digit bill transfer account ID "billSourceAccountId": "", // 12-digit bill source account ID "receiverTransferTransferId": "", // receiver's transfer ID "transferBillSourceTransferId": "", // bill source's transfer ID "deletedTimestamp": "" // Format: yyyy-MM-dd'T'HH:mm:ssZ } ] } } ``` # Using AWS User Notifications with AWS Billing Conductor You can use [AWS User Notifications](https://docs.aws.amazon.com/notifications/latest/userguide/what-is-service.html) to set up delivery channels that notify you about AWS Billing Conductor events. You will receive a notification when an event matches a specified rule. You can receive notifications for events through multiple channels, including email, [Amazon Q Developer in chat applications](https://docs.aws.amazon.com/chatbot/latest/adminguide/what-is.html) such as Amazon Chime, Microsoft Teams, and Slack, or [AWS Console Mobile Application](https://docs.aws.amazon.com/consolemobileapp/latest/userguide/what-is-consolemobileapp.html) push notifications. You can also see notifications using the [Console Notifications Center](https://console.aws.amazon.com/notifications/) in the AWS User Notifications console. AWS User Notifications also supports aggregation, which can reduce the number of notifications you receive during specific events. For more information, see the [AWS User Notifications User Guide](https://docs.aws.amazon.com/notifications/latest/userguide/what-is-service.html). To use AWS User Notifications, you must have the correct AWS Identity and Access Management (IAM) permissions. For more information about configuring your IAM permissions, see [Creating a notification configuration](https://docs.aws.amazon.com/notifications/latest/userguide/getting-started.html#getting-started-step1) in the *AWS User Notifications User Guide*. The following table lists the AWS Billing Conductor event types supported by AWS User Notifications. **AWS Billing Conductor event types** | Event type | Description | | --- | --- | | Billing Group Configuration Recommended for Billing Transfer | A daily summary of billing transfer events where accepted transfers don't have a corresponding billing group configured, or where billing groups associated with active billing transfers were deleted. When a billing transfer is accepted, we recommend configuring a billing group for the bill source account's organization, which enables accounts in that organization to access pro forma cost data in Billing and Cost Management tools. Without a billing group, usage data remains available through CloudWatch, but configuring a billing group makes it easier for bill source account administrators to monitor costs, such as through budgets configuration. This event type is currently only supported in the US East (N. Virginia) Region (us-east-1). | ## Example event The following is an example of a `Billing Group Configuration Recommended for Billing Transfer` event from AWS Billing Conductor. This event is emitted to Amazon EventBridge with the source `aws.billingconductor`. ``` { "account": "", // 12-digit account ID "region": "us-east-1", // Currently only us-east-1 is supported "detail-type": "Billing Group Configuration Recommended for Billing Transfer", "source": "aws.billingconductor", "version": "0", "time": "", // Format: yyyy-MM-dd'T'HH:mm:ssZ "id": "", // alphanumeric string "resources": [], "detail": { "targetDate": "", // Format: yyyy-MM-dd "recipientId": "", // 12-digit recipient account ID "eventBridgeEventId": "", // unique event identifier "directTransfersAccepted": [ { "transferArn": "", // ARN of the one-level billing transfer "billSourceAccountId": "", // 12-digit bill source account ID "effectiveTimestamp": "", // Format: yyyy-MM-dd'T'HH:mm:ssZ "acceptedTimestamp": "" // Format: yyyy-MM-dd'T'HH:mm:ssZ } ], "indirectTransfersAccepted": [ { "receiverTransferTransferArn": "", // ARN of the receiver's transfer "transferBillSourceTransferArn": "", // ARN of the bill source's transfer "billTransferAccountId": "", // 12-digit bill transfer account ID "billSourceAccountId": "", // 12-digit bill source account ID "effectiveTimestamp": "", // Format: yyyy-MM-dd'T'HH:mm:ssZ "acceptedTimestamp": "" // Format: yyyy-MM-dd'T'HH:mm:ssZ } ], "directBillingGroupsDeleted": [ { "billingGroupArn": "", // ARN of the deleted billing group "billSourceAccountId": "", // 12-digit bill source account ID "transferId": "", // associated transfer ID "deletedTimestamp": "" // Format: yyyy-MM-dd'T'HH:mm:ssZ } ], "indirectBillingGroupsDeleted": [ { "billingGroupArn": "", // ARN of the deleted billing group "billTransferAccountId": "", // 12-digit bill transfer account ID "billSourceAccountId": "", // 12-digit bill source account ID "receiverTransferTransferId": "", // receiver's transfer ID "transferBillSourceTransferId": "", // bill source's transfer ID "deletedTimestamp": "" // Format: yyyy-MM-dd'T'HH:mm:ssZ } ] } } ``` # Compliance validation for AWS Billing Conductor Third-party auditors assess the security and compliance of AWS services as part of multiple AWS compliance programs. AWS Billing Conductor is not in scope of any AWS compliance programs. For a list of AWS services in scope of specific compliance programs, see [AWS Services in Scope by Compliance Program](https://aws.amazon.com/compliance/services-in-scope/). For general information, see [AWS Compliance Programs](https://aws.amazon.com/compliance/programs/). You can download third-party audit reports using AWS Artifact. For more information, see [Downloading Reports in AWS Artifact](https://docs.aws.amazon.com/artifact/latest/ug/downloading-documents.html). Your compliance responsibility when using AWS Billing Conductor is determined by the sensitivity of your data, your company's compliance objectives, and applicable laws and regulations. AWS provides the following resources to help with compliance: + [Security and Compliance Quick Start Guides](https://aws.amazon.com/quickstart/?awsf.quickstart-homepage-filter=categories%23security-identity-compliance) – These deployment guides discuss architectural considerations and provide steps for deploying security- and compliance-focused baseline environments on AWS. + [AWS Compliance Resources](https://aws.amazon.com/compliance/resources/) – This collection of workbooks and guides might apply to your industry and location. + [Evaluating Resources with Rules](https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html) in the *AWS Config Developer Guide* – The AWS Config service assesses how well your resource configurations comply with internal practices, industry guidelines, and regulations. + [AWS Security Hub CSPM](https://docs.aws.amazon.com/securityhub/latest/userguide/what-is-securityhub.html) – This AWS service provides a comprehensive view of your security state within AWS that helps you check your compliance with security industry standards and best practices. # Resilience in AWS Billing Conductor The AWS global infrastructure is built around AWS Regions and Availability Zones. AWS Regions provide multiple physically separated and isolated Availability Zones, which are connected with low-latency, high-throughput, and highly redundant networking. With Availability Zones, you can design and operate applications and databases that automatically fail over between zones without interruption. Availability Zones are more highly available, fault tolerant, and scalable than traditional single or multiple data center infrastructures. For more information about AWS Regions and Availability Zones, see [AWS Global Infrastructure](https://aws.amazon.com/about-aws/global-infrastructure/). # Infrastructure Security in AWS Billing Conductor As a managed service, is protected by AWS global network security. For information about AWS security services and how AWS protects infrastructure, see [AWS Cloud Security](https://aws.amazon.com/security/). To design your AWS environment using the best practices for infrastructure security, see [Infrastructure Protection](https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/infrastructure-protection.html) in *Security Pillar AWS Well‐Architected Framework*. You use AWS published API calls to access through the network. Clients must support the following: + Transport Layer Security (TLS). We require TLS 1.2 and recommend TLS 1.3. + Cipher suites with perfect forward secrecy (PFS) such as DHE (Ephemeral Diffie-Hellman) or ECDHE (Elliptic Curve Ephemeral Diffie-Hellman). Most modern systems such as Java 7 and later support these modes. # Access AWS Billing Conductor using an interface endpoint (AWS PrivateLink) You can use AWS PrivateLink to create a private connection between your VPC and AWS Billing Conductor. You can access Billing Conductor as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC don't need public IP addresses to access Billing Conductor. You establish this private connection by creating an *interface endpoint*, powered by AWS PrivateLink. We create an endpoint network interface in each subnet that you enable for the interface endpoint. These are requester-managed network interfaces that serve as the entry point for traffic destined for Billing Conductor. For more information, see [Access AWS services through AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/privatelink-access-aws-services.html) in the *AWS PrivateLink Guide*. ## Considerations for Billing Conductor Before you set up an interface endpoint for Billing Conductor, review [Considerations](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#considerations-interface-endpoints) in the *AWS PrivateLink Guide*. Billing Conductor supports making calls to all of its API actions through the interface endpoint. VPC endpoint policies are not supported for Billing Conductor. By default, full access to Billing Conductor is allowed through the interface endpoint. Alternatively, you can associate a security group with the endpoint network interfaces to control traffic to Billing Conductor through the interface endpoint. ## Create an interface endpoint for Billing Conductor You can create an interface endpoint for Billing Conductor using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see [Create an interface endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#create-interface-endpoint-aws) in the *AWS PrivateLink Guide*. Create an interface endpoint for Billing Conductor using the following service name: ``` com.amazonaws.region.service-name ``` If you enable private DNS for the interface endpoint, you can make API requests to Billing Conductor using its default Regional DNS name. For example, `service-name.us-east-1.amazonaws.com`. ## Create an endpoint policy for your interface endpoint An endpoint policy is an IAM resource that you can attach to an interface endpoint. The default endpoint policy allows full access to Billing Conductor through the interface endpoint. To control the access allowed to Billing Conductor from your VPC, attach a custom endpoint policy to the interface endpoint. An endpoint policy specifies the following information: + The principals that can perform actions (AWS accounts, IAM users, and IAM roles). + The actions that can be performed. + The resources on which the actions can be performed. For more information, see [Control access to services using endpoint policies](https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-access.html) in the *AWS PrivateLink Guide*. **Example: VPC endpoint policy for Billing Conductor actions** The following is an example of a custom endpoint policy. When you attach this policy to your interface endpoint, it grants access to the listed Billing Conductor actions for all principals on all resources. ``` { "Statement": [ { "Principal": "*", "Effect": "Allow", "Action": "billingconductor:*", "Resource":"*" } ] } ```