Pricing bug in AWS Cloudwatch and hardcoded zero cost in some of the aws products

[srikar-jilugu]

Describe the bug

Inaccurate Cost information for various aws products:

I was testing komiser on an aws account by setting it up in an ec2-instance using komiser cli and attached the necessary polices provided in policy.json to the corresponding iam role.

• Inaccurate Cloudwatch cost:

this is a cloudwatch alarm and its cost is reported as 219$ per month, but as per cloudwatch pricing it should be only 0.3$ per month, seems like the cost calculation considers this pricing plan as "per hour" as it calculates here in the code(0.3*730=219$)

• Hardcoded cost as 0 for RDS, ECS and some other products:
  I can see the cost is returned as 0 in some of the products, it seems like cost computation is not yet integrated for these products but including these products in the inventory is giving false information to the overall cost breakup.

To Reproduce
Steps to reproduce the behavior:

1. Installed komiser cli on ec2-instance (also tried with docker compose using the image tailwarden/komiser:3.1.6
2. created config.toml file to get aws account credentials from ENVIRONMENT_VARIABLES

Expected behavior

• Cost Breakup of the account being inaccurate when compared to Aws Cost Explorer

Screenshots
If applicable, add screenshots or Loom video to help explain your problem.

Desktop (please complete the following information):

• OS: MacOS 13.5
• Browser: Chrome
• Version: latest

Very Impressed by this project btw!

[github-actions]

Hey, thank you for opening your first Issue! 🙂 While a Tailwarden team member takes a look at your issue we would like to invite you to join our official Discord server, where you can interact directly with other contributors and Tailwarden team members. Link here: https://discord.tailwarden.com

[AvineshTripathi]

Hey @srikar-jilugu thanks for notifying us will fix this soon in coming releases.

[bishal7679]

@AvineshTripathi Assign me!
I will look into it

[Azanul]

Hi @bishal7679, is there an update on this?

[Azanul]

Closing this issue for the following reasons:

• Cloudwatch bug has been fixed, we now use pricing output to calculate cost.
• Hardcoded costs are hardcoded as 0 because each resource under every service doesn't have a cost associated with it.

Feel free to reopen if you notice otherwise.