[deleted]
AWS services explained in one line each
11–20 of 355 posts
Re: AWS services explained in one line each
#12I see that AWS IoT Greengrass is missing. https://aws.amazon.com/greengrass/
I may be wrong but from what I understood, it's more or less a way to manage AWS Lambda functions (cgi-bin scripts), Docker, and a MQTT client connected to AWS on your GNU/Linux devices (raspbian on a raspberry pi for example, or a x86 pc).
However you still need Ansible or similar to manage the device so the actual value is kinda low because if you have a setup to manage the device, it's not much more work to manage docker and a mqtt client yourself. About running AWS Lambda functions on a the device, I think it makes sense for AWS to check the box "IoT edge computing with AWS Lambda" but unless you have a huge codebase in AWS lambda, it seems to be a bad idea.
In one sentence : "vendor locked half baked IoT platform".
Re: AWS services explained in one line each
#13Well this was really useful. I didn't knew cloudfront was an Amazon product. I wonder what cloudflare people think of that.
CacheFly is another CDN with a somewhat similar name ('CF'). I think they're all different enough that things are clear, though.
Re: AWS services explained in one line each
#14Useful, 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…
How is that a factual error? It didn't say that mounting was impossible, just that it isn't directly used for mounting. How did you conclude that it's done frequently throughout the industry? What percentage of S3 customers do you think does this? If I would have to guess I'd say less than 1%. But I am happy to learn I am wrong.
Re: AWS services explained in one line each
#15This can be a good cheat-sheet and no wonder there have been so many attempts at this(1). Maybe we're better off making this as github page where users can send pull requests and add/rewrite to these. (1) https://netrixllc.com/blog/aws-services-in-simple-terms/ (2) https://expeditedsecurity.com/aws-in-plain-english/
I'd prefer to see this integrated into the AWS UX. For an external crowd-sourced version, I'd like to see something like this with a column for maturity, and whether it actually works. The classic AWS services are rock-solid, and perfectly sufficient to build a business on. Many of the newer ones are.... much less so. A green checkmark, yellow question mark, and red land mine icon would go a long way towards letting…
> integrated into the AWS UX
Sure, it should be right in the headline of the service's "about" page. The fact that people need this at all is UX problem.
If people are reading your "about" page and nobody understands what the hell your thing does, maybe your marketing, faux-tech, word salad is pointless.
Re: AWS services explained in one line each
#16Useful and interesting but some of them are either blank or, well: > After reading it over and over again, i still have no idea what it does. > Some quantum thing. It’s in preview so I have no idea what it is. > in preview so no idea.
Yes.. some of them I have absolutely no clue on what it does. They might serve some edgecase specific for that domain. There are a few services in preview which I cannot see for myself what it does. I will try to update and correct services as soon as I have more info (or somebody can provide it to me)
Indeed. One of the entries like this is a dedicated robot infrastructure service (like, managing real robot hardware that does something out there - think delivery robots). Certainly out of the usual software domain. They also collaborate with a few different quantum computer companies that do different approaches to quantum computing (gate based and annealing) which is an entirely separate field of science and most likely out of the usual comfort zone of most IT people.
Re: AWS services explained in one line each
#17I see that AWS IoT Greengrass is missing. https://aws.amazon.com/greengrass/ I may be wrong but from what I understood, it's more or less a way to manage AWS Lambda functions (cgi-bin scripts), Docker, and a MQTT client connected to AWS on your GNU/Linux devices (raspbian on a raspberry pi for example, or a x86 pc). However you still need Ansible or similar to manage the device so the actual value is kinda low becaus…
Aurora doesn't get a mention either. It's covered under RDS, but still, it seems worth an entry as a service they offer.
Re: AWS services explained in one line each
#18I see that AWS IoT Greengrass is missing. https://aws.amazon.com/greengrass/ I may be wrong but from what I understood, it's more or less a way to manage AWS Lambda functions (cgi-bin scripts), Docker, and a MQTT client connected to AWS on your GNU/Linux devices (raspbian on a raspberry pi for example, or a x86 pc). However you still need Ansible or similar to manage the device so the actual value is kinda low becaus…
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 more insight in these things.
Re: AWS services explained in one line each
#19Reminded me of these similar threads I read a while earlier:
Azure: https://web.archive.org/web/20190321175020/https://www.exped...
https://news.ycombinator.com/item?id=13442597
Re: AWS services explained in one line each
#20I see that AWS IoT Greengrass is missing. https://aws.amazon.com/greengrass/ I may be wrong but from what I understood, it's more or less a way to manage AWS Lambda functions (cgi-bin scripts), Docker, and a MQTT client connected to AWS on your GNU/Linux devices (raspbian on a raspberry pi for example, or a x86 pc). However you still need Ansible or similar to manage the device so the actual value is kinda low becaus…
Close, greengrass is about pushing real aws lambas down to intermediate site gateways (with certs and crypto and management), and then you can have very lightweight clients with almost no brain talk to that thing. My blurb would read, "vendor locked lambdas at the edge to proxy IoT widgets".