<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tools on AutoSpotting</title><link>https://autospotting.io/categories/tools.html</link><description>Recent content in Tools on AutoSpotting</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 16 Jul 2026 21:58:55 +0300</lastBuildDate><atom:link href="https://autospotting.io/categories/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>Vantage Just Updated ec2instances.info and Released All Their Code, Now What?</title><link>https://autospotting.io/blog/leanercloud/2025-05-26-vantage-code-release.html</link><pubDate>Mon, 26 May 2025 00:00:00 +0000</pubDate><guid>https://autospotting.io/blog/leanercloud/2025-05-26-vantage-code-release.html</guid><description>&lt;p&gt;In case you haven&amp;rsquo;t noticed, Vantage recently updated &lt;a href="https://ec2instances.info?utm_source=leanercloud.beehiiv.com&amp;amp;utm_medium=referral&amp;amp;utm_campaign=vantage-just-updated-ec2instances-info-and-released-all-their-code-now-what"&gt;ec2instances.info&lt;/a&gt; with a new refreshed look and feel.&lt;/p&gt;
&lt;p&gt;Over the weekend I had a deep-dive into their changes and thought about what to do with the &lt;a href="http://cloud-instances.info?utm_source=leanercloud.beehiiv.com&amp;amp;utm_medium=referral&amp;amp;utm_campaign=vantage-just-updated-ec2instances-info-and-released-all-their-code-now-what"&gt;cloud-instances.info&lt;/a&gt; fork I &lt;a href="https://leanercloud.beehiiv.com/p/forking-ec2instances-info-as-a-vendor-neutral-alternative-at-cloud-instances-info"&gt;launched&lt;/a&gt; just a few weeks ago.&lt;/p&gt;
&lt;h2 id="why-i-forked-it-in-the-first-place"&gt;Why I forked it in the first place?&lt;/h2&gt;
&lt;p&gt;I covered this in more depth in my initial post, but basically when I decided to fork it, their main public code base hadn&amp;rsquo;t been touched in the last 6 months, and barely touched in the last year, except for a couple of my pull requests.&lt;/p&gt;</description></item><item><title>Progress Report for the First Week After Forking ec2instances.info</title><link>https://autospotting.io/blog/leanercloud/2025-05-14-cloud-instances-progress-report.html</link><pubDate>Wed, 14 May 2025 00:00:00 +0000</pubDate><guid>https://autospotting.io/blog/leanercloud/2025-05-14-cloud-instances-progress-report.html</guid><description>&lt;p&gt;It&amp;rsquo;s been a little more than a week since I decided to fork &lt;a href="http://ec2instances.info?utm_source=leanercloud.beehiiv.com&amp;amp;utm_medium=referral&amp;amp;utm_campaign=progress-report-for-the-first-week-after-forking-ec2instances-info"&gt;ec2instances.info&lt;/a&gt; as &lt;a href="https://cloud-instances.info/index.html?utm_source=leanercloud.beehiiv.com&amp;amp;utm_medium=referral&amp;amp;utm_campaign=progress-report-for-the-first-week-after-forking-ec2instances-info"&gt;cloud-instances.info&lt;/a&gt;, which I &lt;a href="https://leanercloud.beehiiv.com/p/forking-ec2instances-info-as-a-vendor-neutral-alternative-at-cloud-instances-info"&gt;announced&lt;/a&gt; publicly last Thursday.&lt;/p&gt;
&lt;p&gt;While in my previous post I mostly focused on the context around this fork and how I got to it, on this post I want to talk a bit about what happened after after I decided to fork the project over the last few days and where we&amp;rsquo;re at right now.&lt;/p&gt;</description></item><item><title>Forking ec2instances.info as a vendor-neutral alternative at cloud-instances.info</title><link>https://autospotting.io/blog/leanercloud/2025-05-08-forking-ec2instances-info.html</link><pubDate>Thu, 08 May 2025 00:00:00 +0000</pubDate><guid>https://autospotting.io/blog/leanercloud/2025-05-08-forking-ec2instances-info.html</guid><description>&lt;p&gt;Most people using AWS for enough time end up using the &lt;a href="http://ec2instances.info?utm_source=leanercloud.beehiiv.com&amp;amp;utm_medium=referral&amp;amp;utm_campaign=forking-ec2instances-info-as-a-vendor-neutral-alternative-at-cloud-instances-info"&gt;ec2instances.info&lt;/a&gt; website (a.k.a. instances.vantage.sh) to conveniently compare EC2 instance types across families based on specs and pricing.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s basically an online spreadsheet with a lot of data about all cloud instance types and filters to slice and dice that data, as you can see below:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://autospotting.io/images/blog/leanercloud-content/forking-ec2instances-info-as-a-vendor-neutral-alternative-at-cloud-instances-info/image-2.png" alt="Illustration from: Forking ec2instances.info as a vendor-neutral alternative at cloud-instances.info" loading="lazy" decoding="async"&gt;
&lt;/p&gt;
&lt;h2 id="the-ec2instancesinfo-open-source-project"&gt;The ec2instances.info Open Source project&lt;/h2&gt;
&lt;p&gt;Few users realize that this very useful website is backed by an open source project.&lt;/p&gt;</description></item><item><title>Releasing Additional Terraform Building Blocks to the LeanerCloud ONCE Bundle</title><link>https://autospotting.io/blog/leanercloud/2024-06-02-terraform-building-blocks.html</link><pubDate>Sun, 02 Jun 2024 00:00:00 +0000</pubDate><guid>https://autospotting.io/blog/leanercloud/2024-06-02-terraform-building-blocks.html</guid><description>&lt;p&gt;Announcing a new release to the &lt;a href="https://leanercloud.beehiiv.com/p/adopting-model-cli-tools-terraform-building-blocks"&gt;LeanerCloud&lt;/a&gt; &lt;a href="https://leanercloud.beehiiv.com/p/adopting-model-cli-tools-terraform-building-blocks"&gt;ONCE&lt;/a&gt; bundle, which consists of the Terraform serverless microservice building blocks.&lt;/p&gt;
&lt;p&gt;The bundle also contains the Optimizer CLI FinOps tool for GP2 to GP3 conversion for EC2 and EDS, and rightsizing with conversion to Graviton for RDS, Elasticache and OpenSearch, released previously.&lt;/p&gt;
&lt;p&gt;These Terraform building blocks are a set of example Terraform modules for building serverless applications using Lambda and ECS Fargate. They will have a slightly different license from the CLI tools, which will allow you to use them to build proprietary products and use within your team, which is not permitted for the CLI tools.&lt;/p&gt;</description></item><item><title>Adopting the ONCE Model for All My CLI FinOps Tools and Terraform Building Blocks</title><link>https://autospotting.io/blog/leanercloud/2024-05-27-adopting-once-model.html</link><pubDate>Mon, 27 May 2024 00:00:00 +0000</pubDate><guid>https://autospotting.io/blog/leanercloud/2024-05-27-adopting-once-model.html</guid><description>&lt;p&gt;I decided to release all the CLI tools and Terraform building blocks I use in my customers engagements under the &lt;a href="https://once.com?utm_source=leanercloud.beehiiv.com&amp;amp;utm_medium=referral&amp;amp;utm_campaign=adopting-the-once-model-for-all-my-cli-finops-tools-and-terraform-building-blocks"&gt;37signals ONCE Model&lt;/a&gt;, and under their ONCE source-available &lt;a href="https://once.com/license?utm_source=leanercloud.beehiiv.com&amp;amp;utm_medium=referral&amp;amp;utm_campaign=adopting-the-once-model-for-all-my-cli-finops-tools-and-terraform-building-blocks"&gt;license&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="whats-included"&gt;What&amp;rsquo;s included?&lt;/h2&gt;
&lt;p&gt;For now this release only includes Optimizer, my flagship CLI tool for automated optimization of AWS resources which I use all the time in my service &lt;a href="https://leanercloud.com?utm_source=leanercloud.beehiiv.com&amp;amp;utm_medium=referral&amp;amp;utm_campaign=adopting-the-once-model-for-all-my-cli-finops-tools-and-terraform-building-blocks"&gt;engagements&lt;/a&gt; to save my customers lots of money.&lt;/p&gt;
&lt;p&gt;The main use case for the Optimizer tool is for mass-optimization of any or even all of the supported resources within your AWS account, and it is mainly built for hands-on FinOps consultants or people doing large optimization initiatives like I do for my customers.&lt;/p&gt;</description></item></channel></rss>