AWS Billing Conductor

Consider an organization TechCorp, with mutiple departments including Engineering, Data Centers, Marketing, and DevOps. TechCorp wants to track cloud costs for each department separately and provide them with individual bills at the end of each month for budget allocation.

The company has three billing groups:

• Engineering: SageMaker, EC2 instances, Lambda functions, S3, and other resources utilized by the Engineering department are grouped under this billing model. This department needs long-running compute instances for development and testing; therefore, TechCorp has bought a few reserved instances for compute-intensive workloads.

• Data Centers:  This department relies on RDS, Aurora, Redshift, Glue, S3, and Lambda for storage and automation. Their billing group will track and allocate costs for these resources.

• Marketing and Sales: The Marketing and Sales department mainly uses AWS services for analytics, such as Amazon Athena or QuickSight, to monitor campaign data and traffic.

At the end of the month, AWS would calculate a single bill for the three departments based on the services they’ve used. The company would have to manually calculate the costs for individual clients and apply discounts and saving plans.

The AWS Billing Conductor allows us to create custom billing models for each client to save us the hassle.