Web Dev full-stack [LAMP] since 2005, but much heavier on the JS stuff these days.
Jack of all Stacks, Master of some.
Always looking to learn new things. Always glad to help out, just ask.
Location
Atlanta, GA
Education
B.S. in Biochemistry 2004, M.S. in Computer Information Systems 2007
Great write up, and the whole time reading it i'm like "This explains why AWS' interfaces and UI/UX are so terrible in so many ways"
Don't get me wrong, AWS is an amazing platform, it can do far too much in far too many ways and the interfaces are often confusing as hell.
And then there's the stupid little things that kill me. Why can't we download an S3 bucket as a zip file....sure they're not "directories"...who cares, you can write code to make em directories for a moment and then zip em up...i've had at least half a dozen clients ask me about this....
So, we wrote our own api connection to S3 that just loops through the files downloads them and then zips em up....but man it's a pain in the butt to deal with.
Just one example of many "simple" things I feel were overlooked because AWS is developer driven.
Great points! I too had many frustrations with AWS long before I came to work for Amazon. It's an amazingly-powerful suite of tools. But I always felt that it was surprisingly obtuse/confusing and it often felt like it was missing key features. But now I realize that this is because most of the AWS tools were built to meet internal needs. And those internal needs don't always map to customer requirements when it's exposed as a public service.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great write up, and the whole time reading it i'm like "This explains why AWS' interfaces and UI/UX are so terrible in so many ways"
Don't get me wrong, AWS is an amazing platform, it can do far too much in far too many ways and the interfaces are often confusing as hell.
And then there's the stupid little things that kill me. Why can't we download an S3 bucket as a zip file....sure they're not "directories"...who cares, you can write code to make em directories for a moment and then zip em up...i've had at least half a dozen clients ask me about this....
So, we wrote our own api connection to S3 that just loops through the files downloads them and then zips em up....but man it's a pain in the butt to deal with.
Just one example of many "simple" things I feel were overlooked because AWS is developer driven.
Great points! I too had many frustrations with AWS long before I came to work for Amazon. It's an amazingly-powerful suite of tools. But I always felt that it was surprisingly obtuse/confusing and it often felt like it was missing key features. But now I realize that this is because most of the AWS tools were built to meet internal needs. And those internal needs don't always map to customer requirements when it's exposed as a public service.