Cost Management
Last updated: Nov 3, 2026
Rationale
Fluid Attacks uses Cost Management to control and optimize its costs in AWS. These are the primary reasons why Fluid Attacks selected it and not other alternatives:
- It is a core AWS service. When Fluid Attacks makes infrastructure, Cost Management starts to make cost reports.
- It integrates easily with all AWS services, and it gives fully accurate and granular reports.
- It gives very customizable charts. With them, Fluid Attacks can group costs by attributes, for example, service, region, tag, linked account, and many more. Fluid Attacks can also combine attributes.
- The charts support many time ranges, from hourly to monthly granularity.
- The charts support many styles for readability.
- You can export all the data of the charts for external use.
- It supports cost forecasting. Thus, Fluid Attacks can predict future costs from the consumption during a time span that it sets.
- It supports report generation. Thus, Fluid Attacks can make and save customized charts, for example, "Monthly costs by linked account."
- It supports cost allocation tags. Thus, Fluid Attacks can group costs by the tags of the resources.
Alternatives
- GCP Cost Management: It is only for GCP. Thus, Fluid Attacks would have to move to GCP to use it.
- Azure Cloud Cost Management: It is only for Azure. Thus, Fluid Attacks would have to move to Azure to use it.
Usage
Fluid Attacks uses Cost Management for these tasks:
- To monitor its AWS consumption continuously
- To group costs by product tags
- To send alerts when the monthly costs get near the budgets
Fluid Attacks does not use Cost Management for these tasks:
- To monitor costs with Cost Anomaly Detection. Its review is pending.