News for hackers. Stuff that matters.
Re:Troubles with the AWS web console by eternalny1 on Saturday September 07, 2019 @12:30PM (#20904788)
The naming system ... Route53, Fargate, Greengrass, Sumerian, Step Functions, Kinesis ... none of these conjure up basic computing concepts.

Why? Why should "Greengrass" be used for IoT?

Re:Troubles with the AWS web console by scarface74 on Saturday September 07, 2019 @01:20PM (#20905156)
Route 53: What port do you use to connect to DNS?

But the rest, I’ve got nothing as far as making the naming conventions make sense.

But honestly it took me about a year to go from not knowing anything about AWS to being sable to hold my own from a development and networking/Devops standpoint with AWS. Almost everything mapped to concepts I had done before - even the IOT stuff from my time developing field service apps for old Windows CE ruggedized devices.

I could basically draw up an architectural diagram of how I would have implemented the same systems today if I had had AWS at my disposal.

Re:Troubles with the AWS web console by freehunter on Saturday September 07, 2019 @11:20PM (#20908404)
Not to mention they have two products named EBS: Elastic Beanstalk and Elastic Block Storage. Makes work conversations real fun.
Re:Troubles with the AWS web console by cthalupa on Sunday September 08, 2019 @06:53PM (#20913898)
I haven't used Beanstalk in forever, and don't think that it's particularly relevant compared to other alternatives available today, but last time I did, AWS support always abbreviated it to EB when I had to work with them on issues related to it.