cristim / clouds

A simple tool that aims to ease the handling of CloudFormation stacks as code

👋 Hi, I’m @cristim

🌱 I’m currently building apps in Go, and helping companies reduce their AWS costs.

So far I have the following apps, and bulding new ones all the time:

• AutoSpotting - automation for optimizing AWS EC2 costs by up to 90%, by using Spot instances with maximum reliability and with least possible effort (mostly OSS, with a few commercial features)
• EBS Optimizer - catch-all automation for converting EBS volumes to GP3, typically with 20% cost savings (mostly OSS, with a few commercial features)
• a new GUI for both my cost optimization tools, using the Fyne GUI toolkit - not OSS yet but planning to release it once ready
• a CLI tool for managing AWS Marketplace products - https://github.com/LeanerCloud/aws-marketplace-cli
• a Go library for exposing AWS instance type information - https://github.com/LeanerCloud/ec2-instances-info

💞️ I’m looking to collaborate on business opportunities regarding AWS cost optimization

📫 How to reach me:

• LinkedIn
• email
• Gitter

clouds's Issues

Write tests

It needs to be testable.

Rename some commands to make them more intuitive

The update -c is not really intuitive.

Perhaps we should be using something more git'y like pull/push instead?

Ensure the parameters yaml is sorted

The entries from the yaml file should be sorted alphabetically for easier comparison between cloned and dumped stacks. The order is randomized at dump time.

Packaging for major OSes

Support major Linux distributions with native packages.

Attempt to build it for Mac and Windows as well.

Git-like command for configuration handling

Something like clouds config would be nice to have.

Automated delete of stacks that failed to be created

The deletion should be done while performing the next create/update.

The cost estimation is not shown in some cases

If the there are warnings when creating or updating a stack, the cost estimation is not shown. This needs to be fixed.

Get it included in major Linux distributions

Make clouds configurable

Clouds should be a configurable hierarchically, much like git is:

• configuration per stack
• per working-directory
• global configuration file

These configs could remember things like

• the AWS account that was last used in this working directory/stack/globally?
• set various parameters, like for the git integration

Distribute the zsh completion as an oh-my-zsh plugin

Improve tab-completion for command flags

The completion is nice for commands and stack names but it's quite brittle for parameters. This needs to be improved.

Implement bash completion support

This should be on par with the nice stuff we already have on zsh.

Investigate integration with git

Perhaps it would make sense to implement a thin wrapper on top of git commands for some operations. This needs to be configurable

Decouple local and remote stack deletion

The delete command now deletes the local copy as well, which is sometimes annoying.

There should be an additional local/remote flag that makes it differentiate between the working directory and the AWS stack at deletion.