You can use the consolidated billing feature in AWS Organizations to consolidate payment for multiple AWS accounts or multiple AISPL accounts. Each organization in AWS Organizations has a master account that pays the charges of all the member accounts. If you have access to the master account, you can see a combined view of the AWS charges that are incurred by the member accounts. You also can get a cost report for each member account.
Consolidated billing has the following benefits:
One bill – You get one bill for multiple accounts.
Easy tracking – You can track each account’s charges, and download the cost data in .csv format.
Combined usage – If you have multiple standalone accounts, your charges might decrease if you add the accounts to an organization. AWS combines usage from all accounts in the organization to qualify you for volume pricing discounts.
No extra fee – Consolidated billing is offered at no additional cost.
Consolidated Billing Process
AWS Organizations provides consolidated billing so that you can track the combined costs of all the member accounts in your organization. The following steps provide an overview of the process of creating an organization and viewing your consolidated bill:
Open the AWS Organizations console or the AWS Billing and Cost Management console. If you open the AWS Billing and Cost Management console, choose Consolidated Billing, and then choose Get started. You are redirected to the AWS Organizations console.
Choose Create organization on the AWS Organizations console.
Create an organization from the account that you want to be the master account of your new organization. For details, see Creating an Organization. The master account is responsible for paying the charges of all the member accounts.
(Optional) Create accounts that are automatically members of the organization. For details, see Creating an AWS Account in Your Organization.
(Optional) Invite existing accounts to join your organization. For details, see Inviting an AWS Account to Join Your Organization.
Each month AWS charges your master account for all the member accounts in a consolidated bill. The following illustration shows an example of a consolidated bill.
Detailed Billing Report
Detailed billing reports are similar to AWS Cost and Usage reports. They contain similar information about your charges but calculate the individual line items differently. If you sign up for both the detailed billing report and the AWS Cost and Usage reports, the line items will not match. When the reports are finalized at the end of the month, the total cost should align.
AWS stores the detailed billing reports in Amazon S3 as CSV files using the following naming convention:
AWS recreates the detailed billing report multiple times a day, overwriting the report. When AWS overwrites a report, the line items might be in a different order than they were in the previous report. At the end of the month, AWS creates a final report. For the next month, AWS creates a new report file instead of overwriting the final report from the previous month. Reports for previous months remain in your S3 bucket until you delete them.
Enabling detailed billing
Navigate your billing dashboard.
Select the preference menu on the left side and use the options as selected on the screen. You can enter a valid, existing S3 bucket name in the section “Receive Billing Reports” and click verify.
Note: If you have not yet created the S3 bucket for storing Programmatic Billing data, create and configure the same using instructions in AWS.
You’ll see a number of options related to Billing Reports. Enable all billing report options.
Receive Billing Reports
Detailed Billing Report
Cost Allocation Report
Detailed Billing Report with Resources and Tags.
Project Setup in nOps
To set up the project in nOps, follow the steps below.
Setting up the AWS account in nOps is really simple. Enter the project name that you want to use for nOps and a valid AWS S3 bucket name in nOps and then go to AWS Management Console to set up the project in one click. The account that you will use to log in must have the below-mentioned permissions to set up the account properly.
The following are the minimum set of permissions the AWS user needs in order to set up the AWS project successfully.
Log in to nOps.io.
If your are logging into nOps for the first time, then on the “Welcome to nOps” pop-up, click “Add AWS Account” button. Otherwise, go to “Settings → AWS Accounts” from the top right user avatar dropdown.
Once you click on the “AWS Accounts” tab it will open “AWS Accounts” list.
In “AWS Accounts” page, click on “Add New AWS Account”.
Select “nOps Wizard Setup” method from the “Setup Method” selection page.
It will open “Account Details” page with a simple form. Enter the “Project Name” (Name for your AWS workload in nOps) and “Bucket Name” (AWS S3 System bucket which will be used for system logs and billing data.)
Note: Make sure you enter a correct and valid AWS S3 billing bucket. Otherwise, you will not get the required view of data.
Click the “Setup” button and you will be redirected to the AWS Management Console login page to complete the setup.
On the AWS Management Console, the user will be asked to log in using user credentials that have rights defined in the prerequisite section.
Once logged in, the user will be redirected to the “Create Stack” screen. All the fields on this page will be pre-populated.
Mark the checkbox for “I acknowledge that AWS CloudFormation might create IAM resources” and click on the “Create” button.
If you have all required permissions as noted in the prerequisites section then it will start creating the stack with status “CREATE_IN_PROGRESS”. Once the stack is created, then the “Status” will be “CREATE_COMPLETE”. You can refresh your browser to check progress. Normally, it takes 1 to 2 minutes to complete the process.
If you don’t have proper permissions then you will get display errors (see screenshot below) and the stack will not be created. You can assign the necessary permissions and rerun the setup.
Note: It will take a couple of hours before you start seeing different dashboards and compliances within nOps.