The introductory could be done better, I agree. I think a full tutorial with code sample + lab account will help people to accelerate (I am slowly building up s

The introductory could be done better, I agree. I think a full tutorial with code sample + lab account will help people to accelerate (I am slowly building up some code sample myself to train people internally). I suggest to AWS they need to slow down on making new products, and instead focus on enhancing the existing products. Some of the products lack of critical features, and in some cases their APIs are not complete. TODO TODO. Kind of embarrassing. I can understand why they don't do that. Several reasons, 1) they assume people who are looking to build infrastructure in their cloud platform have some experience, if not, extensive experience with operation and building infrastructure. Second, there is a whole support model they sell. Lastly, they have partners to do training. IMO, AWS has done good job presenting intro materials to experienced operation folks in their reInvent videos. I can go on to defend why I think the entry barrier exists, or how AWS can do better. Here is my only tip to any new AWS customers: your mileage is different so don' start plugging in a dozen AWS native services into your architecture just because everyone is using it. Start simple. In our case, we are forced to use two ELBs in front of our nginx and our router service, which eventually routes the requests to our app server. That's a lot of web servers passing traffic. There should be a native offering of Nginx and Apache IMO. ELB is garbage (I say this with a love and hate passion) if you want to replace Nginx / Apache entirely. Anyway, IMO, the major take away of building a cloud infrastructure is "instance is cheap to recycle [if you have the right tool]." > This is where DigitalOcean and Vultr are profiting the most - publishing tutorials, Are you referring to https://www.digitalocean.com/community/tutorials/ https://www.digitalocean.com/community/tutorials/ ? I find them useful, but some of the community tutorials are suggesting (maybe just me) wrong approach. I don't think DO is the first one, I remember browsing Linode content quite often back in the days. Anyway, I think the gap is filled by developing a PaaS such as Herkou, on top of IaaS (AWS, GCE, Azure). Of course, you can build one yourself.