I made this list for my buddy a while back. It's meant to be more humorous than exactly correct Route 53 - Holy shit! It's NSD WAF - Holy shit! It's modsecurity SES - Holy shit! It's Postfix Inspector - Holy shit! It's OSSEC GuardDuty - Holy shit! It's Snort Data Pipeline - Holy shit! It's Cron and Bash Athena - Holy shit! It's Prestodb Glue - Holy shit! It's Hive Metastore and Spark OpsWorks - Holy shit! It's Chef V…
Where is EKS?
AWS services explained in one line each
321–330 of 355 posts
Re: AWS services explained in one line each
#322Re: AWS services explained in one line each
#323Earlier quoted context omitted.
OK substitute VM with OpenStack then.
I’m really not trying to sound like the “do people still watch TV” guy, but I thought OpenStack fell off the hype curve years ago. Do people still use it.
Re: AWS services explained in one line each
#324Earlier quoted context omitted.
I'm not sure if the sarcastic tone is meant to imply AWS is just a rehash of existing tools, but that's obviously not the case. A list of actual competing software/products/services would be pretty useful.
Especially since “EC2” is not just a VM. There are dozen services at least that come under EC2. Also if you start trying to use DynamoDB like you would Mongo, you’re going to be really upset. The use cases, design considerations and performance considerations of DynamoDB compared to Mongo is night and day.
Re: AWS services explained in one line each
#325Consider 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.
I'm always amazed at the complexity of AWS billing. "Why does this cost so much" turns out to be an incredibly hard problem to answer the moment you don't have 100% perfect discipline when it comes to resource tagging. The fact that there are consultants who specialize in figuring out AWS billing was, in retrospect, a warning sign.
Re: AWS services explained in one line each
#326> VPC Create your own VPCs within AWS Not particularly helpful if you have no idea what a VPC is! Of course it takes 2 seconds to search this for yourself, but still.
Isn't VPC a wel known term? I guess the author just included that definition to make the list complete.
Re: AWS services explained in one line each
#327Earlier quoted context omitted.
Isn't VPC a wel known term? I guess the author just included that definition to make the list complete.
I've updated it to "virtual private network" instead.
Re: AWS services explained in one line each
#328Earlier quoted context omitted.
But here you are, letting us know that they have been wonderful sending consultants. It's part PR, part long term customer acquisition
Maybe, just maybe it’s a good product with good customer service? And the reason it costs so much is because you get what you pay for?
Re: AWS services explained in one line each
#329The complexity of pricing and so much different technology, which we absolutely don't really need, will eventually lead to we start hosting things ourselves.
Oh yeah, and privacy of course :)
Re: AWS services explained in one line each
#330S3 is an object store, not a file system.