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?
AWS services explained in one line each
31–40 of 355 posts
Re: AWS services explained in one line each
#32Useful, 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…
It's a one-line summary, not an in-depth explanation or comparison. "Not directly used for mounting" is a good summary of the intended use.
Re: AWS services explained in one line each
#33Useful, 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.
Re: AWS services explained in one line each
#34I 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 mor…
The IoT world is full of vendor locked solutions and platforms that you must avoid. And the joke "the S in IoT stands for Security" is very very true, though AWS Greengrass is actually pretty good for security, if you don't mind sending all your data to a USA company of course.
I would recommend to go opensource and skip the platforms that try to lock you in. There is a lot of solutions depending on how low-level you want to be. Like HomeAssistant if you want high level, or a Mosquitto MQTT broker and NodeRed and some dongles on a Raspberry pi if you want to be lower level.
Re: AWS services explained in one line each
#35Similar 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.
Re: AWS services explained in one line each
#36This is useful.
Re: AWS services explained in one line each
#37Well this was really useful. I didn't knew cloudfront was an Amazon product. I wonder what cloudflare people think of that.
> I wonder what cloudflare people think of that. Because of the name? Cloudfront is older then Cloudflare afaik.
Didn't knew that.
Given the discussion few months back, I thought maybe this was one of those lets-copy-our-costumers-business we-already-know-everthing-he-does things.
Re: AWS services explained in one line each
#38Useful, 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.
You are totally right, and your explanation is perfect. No need to bother.
You could also mount gmail accounts as a filesystem.
Re: AWS services explained in one line each
#39Useful, 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.
Not OP, but my current gig is literally building streaming data pipelines on top of S3 using lambdas that only have a few hundred MBs of RAM to process gigabytes or more of data. S3FS is as close as it comes to mounting in my book.
Re: AWS services explained in one line each
#40"Large & scalable non-relational database (but not really a NoSQL system)" triggered
Ha, that caught my eye too. I'd say DynamoDb is kind of the poster child of the whole NoSQL thing.