francoislagier

Hey! CloudCustodian is such an amazing tool! Part 3 of this series would be focus on "audit and find mistagged resources" and cloudcustodian was already on our list to look at. Thanks for pointing me to c7n_trailcreator.

disclaimer: technical co-founder at CloudForecast

Please invite [email protected]; Good luck everybody!

Francois here, one of the co-founder of CloudForecast.io! Serverless with Lambda fits our needs almost perfectly. We are not using API Gateway and it is truly spiky. Timeouts and recursions were a bit of challenge but nothing crazy since our use cases were fairly simple. Cold starts are definitely a pain but since it's not customer-facing we can leave with it ...

We treat Reserved Instance spending differently in order to provide an accurate forecast. The spend will be treated differently based on your purchase type (All Upfront, Partial Upfront, and No Upfront). Please reach out at [email protected] if you more questions.

Thanks for the question. That's a use case we haven't considered yet, great feedback! As of today, we are using the Organization concept in AWS so "One CloufForecast.io account" == "One Master billing account in AWS". Your use case seems to be slightly different since it's multiple accounts across multiple clients. I would love to discuss options with you and see if we can help. We recently started discussing options with consultant/agency to figure out how to best work together. Please reach out to us at [email protected].

Absolutely, we are already looking into. We are also looking into providing reports that can support multiple cloud providers.

The "Sunny"/"Cloudy"/"Stormy" is based on the personalized threshold (E.g 10% increase compared to yesterday). The alerts can be set for your overall AWS spend but also at the Product (EC2, RDS), Region and Tags level.

For our tech stack, we are mostly using AWS Lambda with the Serverless.com framework. We were able to get off the ground quickly while keeping the cost down