Consider fixing these issues, they don't align with your company's FinOps policies & the Well-Architected Framework.
FinOps policies
🔴 EBS - consider upgrading gp2 volumes to gp3
gp3 volumes are the latest generation of general-purpose SSD-based EBS volumes that enable you to provision performance independent of storage capacity, while providing up to **20% lower price per GB** than existing gp2 volumes. With gp3 volumes, you can scale IOPS (input/output operations per second) and throughput without needing to provision additional block storage capacity. This means you only pay for the storage you need.
resource [aws_instance.my_web_app](https://github.com/djm81/ai-wizard/blob/ab96c4589e460ba9be0ae58ac28baf92a949dd59/infracost_test.tf#L9)
* Set `root_block_device.volume_type` to `gp3`.
in project ` main `
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](https://github.com/djm81/ai-wizard/blob/ab96c4589e460ba9be0ae58ac28baf92a949dd59/infracost_test.tf#L9)
* `Environment` has invalid value `production`. Must be one of the 3 allowed values - did you mean `Prod`?
* Missing mandatory tag `root_block_device.Service`. Consider using default tags to avoid adding tags to individual resources.
* Missing mandatory tag `root_block_device.Environment`. Must be one of ` Dev `, ` Stage `, ` Prod `. Consider using default tags to avoid adding tags to individual resources.
in project ` main `
resource [aws_lambda_function.my_hello_world](https://github.com/djm81/ai-wizard/blob/ab96c4589e460ba9be0ae58ac28baf92a949dd59/infracost_test.tf#L24)
* 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](https://dashboard.infracost.io/org/dominikusnold/settings/usage-defaults), see [docs](https://www.infracost.io/docs/features/usage_based_resources/#infracost-usageyml) 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.
15 cloud resources were detected:
∙ 6 were estimated
∙ 9 were free
```
💰 Infracost report
Consider fixing these issues, they don't align with your company's FinOps policies & the Well-Architected Framework.
🔴 EBS - consider upgrading gp2 volumes to gp3
gp3 volumes are the latest generation of general-purpose SSD-based EBS volumes that enable you to provision performance independent of storage capacity, while providing up to **20% lower price per GB** than existing gp2 volumes. With gp3 volumes, you can scale IOPS (input/output operations per second) and throughput without needing to provision additional block storage capacity. This means you only pay for the storage you need.
🔴 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.
Monthly estimate increased by $294 📈
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. 15 cloud resources were detected: ∙ 6 were estimated ∙ 9 were free ```This comment will be updated when code changes.