dpackard

6 ms·

1. 1.▲
   Cloud cost rate optimization vs. usage optimization(cloudthread.io)

   1 points by dpackard 3y ago|0 comments
2. 2.▲
   by dpackard 3y ago

   Thanks! Cost Explorer is nice. If you want more granular data (resource level, hourly) then you need to look at your Cost and Usage Report which you can do with Cloudthread or AWS CUDOS dashboards. Biggest way to save quick with zero engine
3. 3.▲
   by dpackard 3y ago

   Yes, but right now for GCP we're only aggregating cost recommendations from Google Recommender. For AWS on the other hand we're also computing dozens of our own savings opportunities. In the coming month we'll be adding more
4. 4.▲
   by dpackard 3y ago

   Sometimes the difference between a savings opportunity and engineering action is a Jira ticket :) Thanks Pranav!
5. 5.▲
   by dpackard 3y ago

   Thanks for the input. Definitely tough to balance being opinionated and guiding with best practices vs being flexible for unique company use cases and right now we're trying to "nudge" :) We particularly wanted the "Easy
6. 6.▲
   by dpackard 3y ago

   Definitions we use when rating savings opportunities are below. Right now users can’t edit the difficulty but that’s helpful feedback if you think it’s something you’d use! Would you want the ability to change difficulty to one of our fixed
7. 7.▲
   by dpackard 3y ago

   Yes, for companies using TA these are included in the Opportunities Explorer. Most of the TA cost optimization recs we replicate and compute ourselves so that companies that don’t pay for TA (lots of $ !!!) can see those opportunities. And
8. 8.▲
   Show HN: Cloudthread Savings Hub – Find AWS Savings or We'll Pay You(cloudthread.io)

   54 points by dpackard 3y ago|19 comments
9. 9.▲
   by dpackard 4y ago

   Major use case is a unified Catalog for your entire environment and the ability to change tagging at scale through the Catalog without going into individual Terraform files to make tagging changes. This helps with consistency as engineers o
10. 10.▲
    by dpackard 4y ago

    CloudTrail + Lambda is a good way to create automations in AWS! Great idea for a future setup option, especially for companies that don't use GitHub. Here are some reasons we think GitHub + Terraform IaaC is a good approach: 1. One ben
11. 11.▲
    by dpackard 4y ago

    Daniele here from Cloudthread. Doing cost attribution by account is a great way to segment costs in AWS. If it currently solves all your cost allocation needs, then you can possibly get away without using tagging. At scale many organization