Cost Posture
Introduction
Having clear visibility and solid understanding of the cloud spend across all your cloud accounts is crucial. By using cost analysis, you can better plan for optimization and cost savings. Cost Posture in CoreStack provides visibility on your overall cloud costs across all your cloud accounts.
Cost Posture Summary
Navigate using the left side menu in CoreStack to Cost > Posture in order to access the summary page view.
The Cost Posture summary section provides the consolidated spend by cloud and by currency across all accounts that match this combination. The grid view provides account-level total costs, budgeted costs, and forecasted costs for each cloud account. You can also use the toggle selection to view tenant-level costs.
The tenant-level view shows the following fields:
- Tenant Name
- Total Costs
- AWS Usage
- Azure Usage
- Cost Savings til Date
You can click on the view icon to drill down into the details and view day wise costs. You can also change the filter to view the costs for Current Month (MTD) or for Last 3 Months.
The cloud account-level view shows the following fields:
- Cloud Account Name
- Total Costs
- Cloud (AWS, Azure)
- Account Type
- Scope
- AWS Account ID / Azure Subscription Name
- Cost Savings til Date
You can click on the view icon to drill down into the details. You can also change the filter to view the costs for Current Month (MTD) or for Last 3 Months.
Note:
To ensure that CoreStack is able to define and fetch the Budgets in the native cloud services, it is required for CoreStack to have access to this cloud service. Hence this may not be available for accounts onboarded with Assessment mode enabled.
Refer this link for AWS Budgets pricing: https://aws.amazon.com/aws-cost-management/pricing/
Account-Level View
You can select the View (Eye icon) option in the grid against a specific cloud account to view more details about the costs for that account/subscription.
You will be redirected to another tab where you can see:
-
Toggle option between Cumulative Costs, Location-level Costs, Tags-level Costs, Linked Account-level Costs.
-
Based on your selection you can slice and dice the cost data – you can view the daily costs for that perspective and also the Resource Category-level spend.
Billing Frequency
When the checkbox option “Billing Frequency” is selected, it will show the cost incurred against each cloud account based on the actual billing start date and end date.
For example, If the billing start date and the end date are configured as June 7th to July 7th with the service provider, the cost displayed will be the cost incurred for those specific dates.
When the option is unchecked, the cost value displayed will be the cost incurred for the calendar month. For instance, from the 1st day of the calendar month to the current date of the month, or the 1st day of the calendar past month to the end date of the calendar past month.
Page Views
Page View is the way data is displayed for a user when they access a page in the CoreStack application. Based on the type of view the user has selected, they can view the details on the respective screen.
In the CoreStack application, navigate to Cost > Posture. The Cost Governance screen is displayed. A user can click the arrow (next to Account View) to see the list of available System Views and Custom Views.

System Views
The System Views are page views provided in the CoreStack application. The System Views are displayed in the following order:
- Account View
- Tenant View
- AWS Organization View
- Azure CSP View
- Azure EA View
- GCP Organization View
- GCP Parent Billing Account View
Account View is the default view for every user. A System View cannot be changed or edited. These are standard views and are identified with a desktop symbol.
To access a particular System View, the user can select Cost > Posture > click the arrow (next to Account View) > select the required System View > click Apply & Close. The selected view is displayed.
Custom Views
Custom Views are displayed below the System Views and are derived from the System Views. The Custom Views are identified with a lock symbol. A Custom View is a user defined view. A user can apply all the required filters to view the page as per the applied filters.
For example, a user can select AWS under Cloud filter to view only AWS accounts on their page.
Custom Views can be created in two ways, that is:
- The user can apply the required filters and save that page view.
- Alternately, the user can save a copy of an existing view, apply the required filters, and save that page view.
The filters applied in the Custom Views can be modified anytime. A Custom View that is created by a particular user cannot be accessed by another user. If a user wants to select a different Custom View they have created, then they can select Cost > Posture > click arrow (next to Account View) > select the required Custom View > click Apply & Close to access that view.
Follow these steps to create a Custom View:
-
Navigate to Cost > Posture.
-
Click the arrow.
-
To filter the page and view the screen with specific details, apply the required filter or select the required options to narrow down the search.
For example, click to select AWS to view cost details for AWS accounts only.
-
Click Save.

- In the Create New View box, type the name of the Custom View.
- Select Set as Default View to set this as the default view.
- Click Save & Close.

This Custom View is now saved. When the user navigates to Cost > Posture later again, their Custom View appears by default. All the filters applied in that particular Custom View remain unchanged.
Follow the steps given below to copy a view and mark it as Custom View:
- Navigate to Cost > Posture.
- Click the arrow.
- Click the three dots symbol.
- Click Save As.
The Create a View dialog box displays.

- In the Create a View dialog box, in the Create New View box, type the name of the new view.
- Click Set as Default View to set the selected view as default view.
- Click Save & Close.

Add Default View
A user can mark a page view as a default view. When a user accesses the CoreStack application, they can see the default view set by them. The advantage of using default view is that the user does not have to select a specific view every time they access the application.
Follow these steps to mark a view as default view:
- Navigate to Cost > Posture.
- Click the arrow.
- Click the three dots.
- Click Mark as Default.

After a Custom View is marked as default, a green tick appears.
Note:
A user can click Delete to remove a Custom View.
Updated 7 months ago