What does this provide compared to the official documentation for each service available on Amazon's website, e.g. <a href="https://docs.aws.amazon.com/amazonswf/latest/apireference/API_DescribeActivityType.html" rel="nofollow">https://docs.aws.amazon.com/amazonswf/latest/apireference/AP...</a><p>Each one is available from <a href="https://aws.amazon.com/documentation/" rel="nofollow">https://aws.amazon.com/documentation/</a> -> click service -> click "Api Reference"<p>If all you've saved is one click, I don't think it's worth it, so what else does this do?
I really wish someone would re-write all of AWS documentation and make everything simpler to understand. I'd like to use AWS but the documentation as-is would take hours to read.
Keeps redirecting to S3 APIs for me. Is that intended?<p>One thing people should know about AWS and AWS APIs in general is that it is a ghetto. The ad-hoc nature of most AWS services and their weird interactions is indicative of generally bad design. Even with the AWS Ruby SDK I can barely get anything done without consulting 5 different references about which parameters are required, which are optional, and what the sequence of various calls is supposed to be to get an intended result.<p>So even though this is useful a cookbook would have been much more useful.
The whole AWS APIs are formalized and exposed in different ways and that formalism is one of it's strengths: everybody can write a transformation that creates a bindings for his language of choice. For example of this take a look at:<p><a href="https://github.com/boto/boto3/tree/develop/boto3/data" rel="nofollow">https://github.com/boto/boto3/tree/develop/boto3/data</a><p>P.S. Agree that not all of the services adhere to the same bar.