+0
Daily
5,783
stars
626
forks
80
watchers
431
prs
590
issues
0
releases
README
EC2Instances.info
!Vantage Picture
I was sick of comparing EC2 instance metrics and pricing on Amazon's site so I
made EC2Instances.info.
EC2Instances.info was originally created by Garret
Heaton, is now hosted by
Vantage and developed by the community of contributors.
Project status
Vantage employees are actively maintaining and hosting the site with the help of contributors here. Improvements in the form of pull requests or ideas via issues are welcome!
People have suggested many neat ideas and feature requests by opening issues on this repository. We also have a Slack
Community for anyone to join with a devoted channel named instances-vantage.sh.
Requirements
To do a full build, you just need Docker installed. To develop this, however, you will need Docker and it is suggested you also have nvm installed. You can technically just use a Node version that matches or is higher than next/.nvmrc, though, if you so wish.
Developing locally
The first thing you should do is run npm ci in the root. This is to ensure you have prettier installed as expected.
You then need to either:
- Scrape the data locally
- If you aren't touching the scraper, run curl -L https://instances.vantagestaging.sh/www_pre_build.tar.gz | tar -xzf - in the root of the repository to grab the latest CI artifact.
To start the development server, cd into the next directory and run nvm use (run nvm install before this if the Node version changed or this is first usage). From here, run npm ci, for your first ever time run npm run init, and then npm run dev. This will start the Next development server. Before you make a pull request, it is suggested you run npm run check-types to find any type issues. This will be done before build by the CI, but it does tighten development cycles to do it here.
When you make changes, it is suggested to use the recommended VS Code extensions if that is your editor. If not, tell your editor to auto-format based on the Prettier configuration in the root. Before you make a PR, you should run make format in the root to make sure the formatting is correct for the version of gofmt/Prettier we use.
Make sure your pull requests target develop since this is our staging. When it is merged into main, that is production.
Scraping the data locally
The scraper is written in Go and fetches data from AWS, Azure, and GCP APIs. You'll need credentials for each provider.
AWS: Ensure your IAM user has at least the following permissions:
json
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ec2:DescribeInstanceTypes",
"ec2:DescribeSpotPriceHistory",
"ec2:DescribeInstanceTypeOfferings",
"elasticache:DescribeEngineDefaultParameters",
"rds:DescribeDBEngineVersions",
"rds:DescribeOrderableDBInstanceOptions"
],
"Resource": ""
}
]
}
Set AWS_ACCESS_KEY_ID Top issues
#260Improvement: Include Region as column6 comments · 2017-07-20#903Add EC2 Capacity Block pricing2 comments · 2026-05-27#565Fargate (with Spot)2 comments · 2021-07-09#1005p5e.48xlarge instance region coverage issue1 comments · 2026-10-16#701Add SageMaker pricing1 comments · 2023-07-26#560Break even metric for RIs and Savings plans1 comments · 2021-07-09#961Baseline comparison0 comments · 2026-07-08#299Percent savings calculation for reserved instance (esp for convertibles)0 comments · 2017-11-13