adding ifra test

[sahatmih-flutterint]

No description provided.

[infracost]

💰 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.

FinOps policies
🔴 EC2 - consider using Graviton instances Graviton instances are around 20% cheaper than equivalent x86 instances.
	resource aws_instance.my_web_app Switch instance_type from m3.xlarge to m6g.xlarge — save $981/year (42%) in project main
🔴 EC2 - consider using latest generation instances for m family instances Upgrade to the latest generation of Amazon EC2 instances in the M family for enhanced CPU performance, increased memory capacity, and improved networking bandwidth, all at a more cost-effective price compared to previous generations.
	resource aws_instance.my_web_app Switch instance_type from m3.xlarge to m6i.xlarge — save $648/year (27%) in project main
🔴 Lambda - consider using Graviton Graviton lambda functions are 20% cheaper than x86 equivalents with up to 19% improved performance. If you do not use x86 binary dependencies, setting lambda functions to use ARM64 can result in significant savings and improved performance. See AWS docs for details.
	resource aws_lambda_function.my_hello_world Set architectures to ["arm64"]. 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 Environment has invalid value production. Must be one of the 3 allowed values - did you mean Prod? 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. Missing mandatory tag: root_block_device.Service. Consider using default tags to avoid adding tags to individual resources. 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_instance.my_web_app
  +$294

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

    + root_block_device

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

+ 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

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.

3 cloud resources were detected:
∙ 3 were estimated

---

_{This comment will be updated when code changes.}