[eximius]

Is it just me, or does anyone else find the documentation of AWS and related services nearly incomprehensible? Maybe it's just too 'enterprise-y' and I haven't spent enough time in that environment, but it feels like all the information is squirreled away in 10,000 different pages and that I'd have to read all of it to just get the basics.

Also, does anyone know if there is an API for AWS to dynamically create, load, and launch EC2 and/or Lambda instances (i.e., boto - though I'm open to suggestions for something else) AND, preferably, have separate billing for each thing? Do I need multiple accounts to do separate billing? Something about IAM roles...?

[deklerk]

YES. Absolutely yes. I _hated_ this aspect of working with AWS. Also, documentation always came off as "generic" and "wordy" without being "useful" - a huge, huge article that might have the tiny sliver you need in it, or perhaps one of its dozens of sister articles would have the answer, who knows.

[lainga]

You're only supposed to grab the tiny sliver so you can mention it to $consultant in desperation.

[PretzelFisch]

I find the documentation good and some frustratingly vague depending on the service. In AWS everything can be done via code including starting and launching EC2/lambda. You'll need to look in their sdk documentation and experiment a little to figure out what everything means and in what order you need to make the api requests.