News for hackers. Stuff that matters.
Re:How we got our AWS bill to around 2% of revenue by nordsieck on Sunday June 28, 2020 @03:53AM (#23667348)
> Their setup is trivial - they could do it at 0.2% of revenue with a cheap vps on Linode or other...

Lightsail has pretty comparable pricing to Linode. I'm sure they could re-architect their app to use fewer instances, but they could do that and stay on Lightsail as well.

Moving to linode isn't going to give them a 90% savings.

Re:How we got our AWS bill to around 2% of revenue by mattbillenstein on Sunday June 28, 2020 @03:07PM (#23671210)
Pretty interesting, I didn't realize the pricing was the same and you get bandwidth.

This bandwidth pricing is very interesting because if you have apps that ship a lot of bytes, you can just run like haproxy on lightsail and get those bytes very very cheap instead of paying standard egress data pricing at like 9 cents per gig...

Re:How we got our AWS bill to around 2% of revenue by PhantomGremlin on Sunday June 28, 2020 @04:37PM (#23671844)
I just asked the same question https://news.ycombinator.com/item?id=23671787 before I saw your comment.

Does this work? It seems like using lightsail is a way to drastically reduce egress data pricing??? It's like a free lunch, what's the catch?

Re:How we got our AWS bill to around 2% of revenue by mattbillenstein on Sunday June 28, 2020 @08:10PM (#23673114)
Only thing I can think of is if they charge you egress out of a vpc to lightsail or something - would like to know if anyone has tried this.
Re:How we got our AWS bill to around 2% of revenue by wolco on Sunday June 28, 2020 @04:04AM (#23667384)
The price seems on par. Are there hidden costs on aws?
Re:How we got our AWS bill to around 2% of revenue by dijit on Sunday June 28, 2020 @04:22AM (#23667444)
I'm assuming that you might not be aware of AWS pricing.

It's actually incredibly complicated and often very difficult (if not impossible) to predict. We have a dedicated part of our organisation which exists solely to figure out costs ahead of time for project.

I'm not sure if it's intentionally obfuscated, I would suspect not, because "pay for what you use" can be broken down into many areas.

Re:How we got our AWS bill to around 2% of revenue by znpy on Sunday June 28, 2020 @06:32AM (#23667888)

    It's actually incredibly complicated and often very
    difficult (if not impossible) to predict.
Not a joke: there are people that optimize aws bills for a living.
Re:How we got our AWS bill to around 2% of revenue by Ozzie_osman on Sunday June 28, 2020 @10:27AM (#23668899)
There are startups that build specialized AI to optimize AWS bills for a living.
Re:How we got our AWS bill to around 2% of revenue by radicalbyte on Sunday June 28, 2020 @06:23AM (#23667855)
Azure is the same and Microsoft spent 20 years making their software licencing more and more unpredictable.

It absolutely is a strategic choice and not an accident.

Re:How we got our AWS bill to around 2% of revenue by dan15 on Sunday June 28, 2020 @01:16PM (#23670323)
This is the main reason I don't use it. I like having predictable monthly pricing that remains consistent.
Re:How we got our AWS bill to around 2% of revenue by scarface74 on Sunday June 28, 2020 @06:17AM (#23667830)
What is incredibly complicated about Lightsail? That’s kind of the point of it.
Re:How we got our AWS bill to around 2% of revenue by mittalsuraj18 on Sunday June 28, 2020 @07:27AM (#23668091)
Egress charges.

Lightsail and digital ocean give you 1TB egress minimum included in billing. Now try to input that number into EC2 instance. If I am not wrong, that turns out to be 130$ approx