Skip to content

Conversation

S0cialGhost
Copy link
Owner

No description provided.

Copy link

infracost bot commented Oct 3, 2025

💰 Infracost report

Consider fixing these issues, they don't align with your company's FinOps policies & the Well-Architected Framework. Add a PR comment with @infracost help to see how you can dismiss or snooze issues and unblock your PR.

Tagging policies
🔴 FinOps tags

This example Tagging policy shows how you can enforce required FinOps tag keys/values in pull requests. This example checks for the tags 'Service' (can have any value) and 'Environment' (must be Dev/Stage/Prod) on all taggable resources being changed in the pull request. You can adjust it from https://dashboard.infracost.io > Governance > Tagging policies. You have a 14 day trial of this feature as it's part of Infracost Cloud.

resource aws_instance.my_web_app.root_block_device

  • Missing mandatory tag Environment. Must be one of Dev, Stage, Prod. Consider using default tags to avoid adding tags to individual resources.
  • Missing mandatory tag: Service. Consider using default tags to avoid adding tags to individual resources.

in project main

resource aws_instance.my_web_app

  • Environment has invalid value production. Must be one of the 3 allowed values - did you mean Prod?

in project main

resource aws_lambda_function.my_hello_world

  • Missing mandatory tag: Service. Consider using default tags to avoid adding tags to individual resources.

in project main

Guardrails
🔴 Costs increase by more than $3K/yr - please review

Cost increased by $294, threshold was $250. Review the estimate to ensure it meets your expectations. If you are unsure what to do, check with your team lead.

Monthly estimate increased by $294 📈
Changed project Baseline cost Usage cost* Total change New monthly cost
main +$294 - +$294 $294

*Usage costs can be estimated by updating Infracost Cloud settings, see docs for other options.

Estimate details
Key: * usage cost, ~ changed, + added, - removed

──────────────────────────────────
Project: main

+ aws_lambda_function.my_hello_world
  Monthly cost depends on usage

    + Requests
      Monthly cost depends on usage
        +$0.20 per 1M requests

    + Ephemeral storage
      Monthly cost depends on usage
        +$0.0000000309 per GB-seconds

    + Duration (first 6B)
      Monthly cost depends on usage
        +$0.0000166667 per GB-seconds

+ aws_instance.my_web_app
  +$294

    + Instance usage (Linux/UNIX, on-demand, m3.xlarge)
      +$194

    + root_block_device

        + Storage (general purpose SSD, gp2)
          +$100

Monthly cost change for main
Amount:  +$294 ($0 → $294)

──────────────────────────────────
Key: * usage cost, ~ changed, + added, - removed

*Usage costs can be estimated by updating Infracost Cloud settings, see docs for other options.

40 cloud resources were detected:
∙ 20 were estimated
∙ 20 were free

This comment will be updated when code changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant