Live data from Hacker News

AWS services explained in one line each

adayinthelifeof.nl

41–50 of 355 posts

Re: AWS services explained in one line each

#41
post #35
post #31

Similar to https://expeditedsecurity.com/aws-in-plain-english/ Why does AWS use such convoluted language? Is it because they're dominant and it adds friction to moving to another provider?

Because your enlightened state is in conflict with their commercial interest. Providing complex answers to simple questions, almost always is due to a need to hide sth.

It reminds me of cult-speak, where everything has to be redefined according to some abstract higher level representation, even when it's simple.

Re: AWS services explained in one line each

#42

AWS sounds like a good idea until you start calculating the cost of the setup with any kind of clustering and moderate data traffic.

The compute is really a negligible part and one that you can severely effect.

Outbound bandwidth is the real killer, going at ~$90/TB

Re: AWS services explained in one line each

#43
post #18

Earlier quoted context omitted.

The whole lot of IOT services are pretty confusing. Mostly because I have no experience with IOT/MQTT in general and it took a few days to actually figure out how to create and connect things (emulated). I actually bought some IOT devices (lamps, sensors) to try it out, but this turned out to be vendor-locked without any possibilities for MQTT. I reckon somebody with more experience in the IOT field could provide mor…

Do your sensors/lamps use Zigbee? I use the excellent Zigbee2MQTT library and a DIY Zigbee sniffer. Now I can use most vendor-locked IOT-devices (Hue, Ikea Tradfri, cheapo Chinese stuff) in my Home Assistant without the need of a separate bridge. Check if your devices are supported here: https://www.zigbee2mqtt.io/information/supported_devices.htm...

The devices have a ESP8266, and they should be easily flashed with custom firmware to connect to MQTT. But I found that OTA flashing did not work, and the only viable option is to solder apparently. I'm dangerous enough without a soldering iron in my vicinity.

Re: AWS services explained in one line each

#44
post #9

Useful, but it contains factual errors: >S3 File storage. Not directly used for mounting, but you can directly download files from HTTP. You most certainly can mount S3 buckets, and its done frequently in data pipelines throughout the industry[0]. >S3 Glacier Low cost storage system for backups and archives and such Sure but it would be good to include why there is a tradeoff in price, why is it low cost? For Glacier…

Yes, you can use a S3 bucket and Route53 to host a high availability, static website for mere pennies.

You should be wary of any hostilities between your site and it's users. Even though it can't be brought down, your wallet sure can be if you don't set it up really carefully.

You can simply retrieve the page constantly over a residential connection to drive up the costs to over hundreds of dollars

Re: AWS services explained in one line each

#45
post #31

Similar to https://expeditedsecurity.com/aws-in-plain-english/ Why does AWS use such convoluted language? Is it because they're dominant and it adds friction to moving to another provider?

Same with Azure. Even when I understand what it does, I am baffled of how they came up with the name.

Re: AWS services explained in one line each

#48
post #35

Earlier quoted context omitted.

Because your enlightened state is in conflict with their commercial interest. Providing complex answers to simple questions, almost always is due to a need to hide sth.

It reminds me of cult-speak, where everything has to be redefined according to some abstract higher level representation, even when it's simple.

This is typical in finance. Many of the financial "instruments" are given funny nouns that hide the true character of what they are (usually shitty loans, or stocks being sold at a mark-up).

Re: AWS services explained in one line each

#49
post #26

Consider that your typical enterprise software project will use quite a lot of these, and that you pay for them all separately, and sometimes pay twice for them (e.g. S3 you pay for storage and for outbound bandwidth). It's quite a tour de force how Amazon have taken "separation of concerns", applied it to web services and used it to create complex and difficult to understand or predict pricing to print money. Bravo.

Yup; if you go with AWS, expect to build a pretty complicated setup distributed over many services. Even the basic LAMP / Wordpress stack mentioned in a sibling comment and often used in tutorials starts at $50 / month once you add everything up, and that's without any traffic.

Although I guess Lightsail would be a lot more affordable.

Re: AWS services explained in one line each

#50
It's sad that this is so necessary, but I'm still confused by the very first two lines of this list.

> EC2 Virtual Private Servers > Lightsail Amazon’s hosting provider (vps, dns, storage)

Both of these are VPS? EC2 has no storage?

Absolutely not a criticism of your list, more a comment on how baffling AWS is these days. I stopped using AWS once they hit the point where I couldn't reasonably be expected to remember what all the three letter acronyms were. I still occasionally have to use it for S3, Route53 and IAM - but every time I log into the console I find that they've removed them from my "pinned" services in the menu bar and I have to pin them again. Even this tiny detail is enough to make me not want to have to deal with that * 1000 by taking up more of the services.

Post reply on HN