January update: New GitHub bot & 3 new Graviton policies
Happy New Year 🎉 We’re excited to kick off 2025 with the latest Infracost updates!
New Graviton policies for EC2, ECS and Lambda
Last year, many enterprises used Infracost’s Graviton policies for RDS, ElastiCache, and OpenSearch to achieve significant cost savings. Migrating these managed AWS services to Graviton proved to be low-effort and low-risk, thanks to AWS’ migration features.
As we move into 2025, our biggest enterprise customers are expanding Graviton adoption beyond managed services to their applications. To support this shift, we’re excited to introduce three new Graviton FinOps policies:
- EC2 Graviton: Save 20% compared to equivalent x86 instances.
- ECS Graviton: Save 20% on ECS instances and Fargate containers. By using multi-architecture images and setting task definitions to ARM64, you can achieve significant savings and performance gains.
- Lambda Graviton: Save 20% and enjoy up to 19% better performancecompared to x86 for your Lambda functions that don’t rely on x86 binary dependencies.
Login to Infracost Cloud to explore your savings potential and enable the new policies in pull request comments—so your engineers start taking action today.
Introducing the Infracost GitHub bot
The distributed nature of infrastructure provisioning at large enterprises means fixing issues is a distributed problem too. Take Graviton adoption for example—FinOps teams rely on many engineers to take action across different code repos to realize savings. Coordinating these efforts requires seamless communication and a developer-friendly approach to policy enforcement.
We’re excited to announce a new way for engineers to interact with FinOps teams using the Infracost GitHub bot! The bot enables engineers to act directly within pull requests by posting comments like @infracost help, or @infracost dismiss app isn't compatible with Graviton. This two-way communication ensures engineers can focus on what’s actionable, while FinOps teams get full visibility into dismissed issues and their rationale. All of this happens without the need for Jira tickets or planning meetings 🚀
Infracost Cloud now gives you a clear summary of progress: see the percentage of issues fixed, open issues with estimated timelines, and how many new issues were prevented in pull requests—a key benefit of shifting FinOps left. Try the GitHub App today to use the new Infracost bot.
Other improvements
Infracost now supports replaying events from GitHub, GitLab, and Azure Repos to prevent pull request checks from being delayed by network glitches. Developers can also re-run PRs directly from GitHub or Infracost Cloud after fixing module issues, enabling PR re-evaluation without pushing new commits.
We’ve also enhanced Azure Repos PR comments for better issue tracking. Comments are now marked Active when there is a policy issue, and Closedwhen no action is needed. If a developer updates the status (e.g., to Won’t fix), Infracost won’t reset it to Active after new commits, reducing noise while still requiring acknowledgment of unresolved issues.
Lastly, Infracost CLI v0.10.40 is here with major performance improvements! It includes support for the AWS ap-southeast-5 region, CloudFront Functions, enhanced Spacelift stack variable loading, improved Terragrunt input parsing and module handling, and dependency output mocks. Upgrade now to take advantage of these updates!
Cheers,
Ali Hosseini
Co-founder, Infracost
p.s. follow me on LinkedIn for updates & insights from other Infracost users
