ec2instances.info VS vscode-infracost

This web page for comparing EC2 pricing using filtering https://instances.vantage.sh/?region=us-east-2 is open source https://github.com/vantage-sh/ec2instances.info

Worked on adding Dedicated Host pricing to https://ec2instances.info so it can display pricing for mac1 and mac2 AWS instances. Ended up being much more involved than expected, https://github.com/vantage-sh/ec2instances.info/pull/667

It's community supported! We just pay the bills and maintain hosting it :)

Do you mind opening an issue on the repo here? https://github.com/vantage-sh/ec2instances.info

Thank you for the report!

Hey HN, 10 years after the project began we have updated the UI for the cloud server comparison site known as EC2Instances.info. This refresh brings a sticky filter bar so you can scroll and see what filters are applied, a more compact navbar, and improved UX for comparing instances.

I've also fixed numerous long standing UI bugs including: comparisons now load correctly on RDS and ElastiCache, sort by max ENI works, sort by RDS instance storage works, and all dropdowns have consistent behavior.

For maintainers and contributors, all the frontend libraries are upgraded to their latest versions, https://github.com/vantage-sh/ec2instances.info. Going forward, we are aware that the homepage size is quite large and have plans to address this.

We have tried to be good stewards of this project and evolve it carefully. Eager to hear what you think of the new UI!

Disclaimer: I maintain https://github.com/vantage-sh/ec2instances.info for them

Hi everyone! I am the new maintainer for ec2instances.info, an AWS server comparison site. I just shipped my first major feature called Detail Pages, https://github.com/vantage-sh/ec2instances.info/commit/31e2fb41a280eb86da9d135b4b852f8d6325c33f

Sorry for being harsh, but it is really screwed up for Firefox users. For me it's completely unusable, because when trying to filter it freezes for more than 20 seconds before displaying the filtered values. And that's on a rather recent desktop PC.

There is an open bug report regarding that, however nothing has happened in the past year to fix it: https://github.com/vantage-sh/ec2instances.info/issues/586

https://github.com/vantage-sh/ec2instances.info/issues/316 https://github.com/vantage-sh/ec2instances.info/issues/617

Hi, we are Ali, Hassan, and Alistair, co-founders of Infracost (https://www.infracost.io/). Infracost helps engineers see the cost of each Terraform change before launching resources. When changes are made, it posts a comment with the cloud cost impact. For example, “you’ve added 2 instances and volumes, and change an instance type from medium to large, your bill will increase by 25% next month, from $1000 to $1250 per month”.

We launched in February 2021 (https://news.ycombinator.com/item?id=26064588), and Infracost is now being actively used by over 3,000 companies. However, there is a shift happening in the cloud cost management space. New teams, called FinOps teams (a combination of "Finance" and "DevOps"), are being formed within companies to manage cloud costs.

One of the first tasks assigned to these teams is to determine "who is using what" - that is, which teams, business units, products, etc. are spending the most on cloud. To accomplish this, they use tags. Tags are labels that all cloud resources should have and are key-value pairs. For example, a server could be tagged with: product=HackerNews; environment=production; team=blueTeam. So if resources are not tagged properly, then you can’t tell who is using what.

However, FinOps teams face challenges because their tools are reactive. These tools begin by analyzing cloud bills and providing visibility of tags from there. This means that they are looking at resources that are already running in production and costing money. A customer recently shared, “I want all resources to be properly tagged. But if they are not, I would rather a resource not be tagged at all than be tagged incorrectly.”

My "aha" moment! FinOps teams can define a tagging policy that can be validated in CI/CD before resources are launched. This is important because if code is shipped with the wrong tags, FinOps teams will have to fight for sprint time to fix them. Even if you shut down an untagged resource directly in the cloud, the next time Terraform runs, the resource will launch again with no tag. You need to fix the issue at its root.

I’d love your feedback on our solution to the tagging problem. You define your tag key-value policy in our SaaS product, and Infracost checks all Terraform resources per change. If anything fails the policy, it posts a comment with the details of which resources need tags, and what the allowed values are. Once fixed, it will let the code be shipped to production.

Try it out by going to https://dashboard.infracost.io/, setting up with the GitHub app or GitLab app, and defining your tagging policy. It will then scan your repository and inform you of any missing tags and their file and line number. You can use the free trial, but if you need more time, please message me and I’ll extend it for you.

I would also love to hear how others ensure that the correct tag keys and values are applied to all resources, and whether this is done proactively or reactively. Additionally, I would be interested in hearing about any lessons learned in the process.

Cheers

Great toolchain, including Infracost or tfsec.

Infracost is an open-source tool for estimating the cost of cloud infrastructure using Infrastructure as Code templates.

Throughout this post, you will see me mention the cost of running this using an estimate. I have been using for a while, a tool called infracost which is an open source (with subscription based additions) cost estimator tool - https://www.infracost.io/. For this demonstration, using the sample code listed above, it would cost an estimated $76.65/month - so if you don't want rack up a bill, only deploy when you want to test, and use Terraform to destroy the services when you are done.

Infracost : Infracost is an open-source tool that allows users to see the cost of running their infrastructure, such as AWS resources, in near real-time. It uses the AWS Price List API to determine the costs of resources, and can be integrated into CI/CD pipelines to provide cost feedback during the development process. This allows developers to make informed decisions about their infrastructure and optimize costs. Additionally, Infracost can be used to create alerts based on cost thresholds, so you can be notified when your infrastructure costs exceed a certain amount. This can be especially useful for teams that operate on a tight budget or need to manage costs closely.

An Infracost API key. You can get one by signing up for free at Infracost.io.

Since Wing compiles to Terraform, you should be able to manually run Infracost (https://www.infracost.io) to get an idea of costs.

Having that capability baked into the language/compiler would be a great addition.