Infracost scans for Terraform code changes and checks over 3 million prices to create a simple, understandable cost estimate before any resources are launched.

Infracost Community

One AWS service (e.g. AWS Backup) usually has many Terraform Resources, and we try to map them so where possible we don’t duplicate the same cost component across Terraform Resources. But sometimes the same TF resource can have the same cost component. So it depends on the specific case. In your case, it probably makes sense to skip them since `aws_fsx_windows_file_system` already covers those costs.

My take on this was that the costs for all the different backup types would be associated with an `aws_backup_vault`.  I suppose it makes sense that there isn’t different pricing than a ‘regular’ backup, so I would say re-use the cost components from the individual services.