<story><title>The cloud skills shortage and the unemployed army of the certified</title><url>https://itnext.io/the-cloud-skills-shortage-and-the-unemployed-army-of-the-certified-bd405784cef1</url></story><parent_chain><item><author>drieddust</author><text>I work for a large IT outsourcing company and I have seen the opposite of it with our clients. Most of our clients wants to be on cloud but without any change to their habits so we end up building complete traditional data centers in the Azure or AWS.&lt;p&gt;Most applications are simply cloned from existing On-Premises Infrastructure because every project have a 2 weeks deadline and every single stakeholder just wants to stick it in. Patterns like Auto-Scaling etc is just a far fetched dream.&lt;p&gt;Supporting such Infrastructure where every server is a pet trying to survive in a Slaughter House is a deeply painful.</text></item><item><author>coleca</author><text>I did some freelancing cloud work recently and was shocked at what I saw out there. From small one person operations to startups to large multinational Fortune 500 corporations I saw the same pattern repeated over and over. People using the cloud to spin up infrastructure that have no experience building out infrastructure and making really bad and dangerous mistakes.&lt;p&gt;Amazon, Google, Microsoft and others make it simple to get going but the devil is in the details when it comes to building it right, safe and ready for production.  Just a few examples:&lt;p&gt;• Putting RDS SQL Servers on a public IP with no protection&lt;p&gt;• No templating of servers so if it disappears you have no record of how to get a new one running again&lt;p&gt;• Servers with SSH password authentication turned on with passwords of “Password”, because SSH key auth was “too hard for our devs”&lt;p&gt;• No backups because “it’s in the cloud, isn’t the cloud backing it up for me, like iCloud?”&lt;p&gt;I have an AWS Solution Architect Professional certification and agree you could get a cert and still not be qualified to run or design much on AWS but it does put you ahead of much of what I’ve seen out there.</text></item></parent_chain><comment><author>raincom</author><text>In big companies, 95% of apps are still old school: firewall -- load balancer -- 5 front ends -- 3 back ends -- two database servers.  And the people who developed most of these apps left these companies long time, what these companies have bunch of managers and some developers who maintain that code.&lt;p&gt;People of this kind are extremely conservative, because they are not in a position to fix major issues if something goes wrong--esp new architecture. So, they want to lift as is to aws.&lt;p&gt;A decade ago, I was involved in physically moving three solaris servers that were running un-supported BEA weblogic instances. When I powered on these three servers on a different rack, weblogic cluster failed. No IP change, just moved machines to free up racks in one row. And the people who developed the app, and the dev architect behind it were so mad at us. In the end, they gave up on that app.&lt;p&gt;That&amp;#x27;s how it goes.</text></comment>
<story><title>The cloud skills shortage and the unemployed army of the certified</title><url>https://itnext.io/the-cloud-skills-shortage-and-the-unemployed-army-of-the-certified-bd405784cef1</url></story><parent_chain><item><author>drieddust</author><text>I work for a large IT outsourcing company and I have seen the opposite of it with our clients. Most of our clients wants to be on cloud but without any change to their habits so we end up building complete traditional data centers in the Azure or AWS.&lt;p&gt;Most applications are simply cloned from existing On-Premises Infrastructure because every project have a 2 weeks deadline and every single stakeholder just wants to stick it in. Patterns like Auto-Scaling etc is just a far fetched dream.&lt;p&gt;Supporting such Infrastructure where every server is a pet trying to survive in a Slaughter House is a deeply painful.</text></item><item><author>coleca</author><text>I did some freelancing cloud work recently and was shocked at what I saw out there. From small one person operations to startups to large multinational Fortune 500 corporations I saw the same pattern repeated over and over. People using the cloud to spin up infrastructure that have no experience building out infrastructure and making really bad and dangerous mistakes.&lt;p&gt;Amazon, Google, Microsoft and others make it simple to get going but the devil is in the details when it comes to building it right, safe and ready for production.  Just a few examples:&lt;p&gt;• Putting RDS SQL Servers on a public IP with no protection&lt;p&gt;• No templating of servers so if it disappears you have no record of how to get a new one running again&lt;p&gt;• Servers with SSH password authentication turned on with passwords of “Password”, because SSH key auth was “too hard for our devs”&lt;p&gt;• No backups because “it’s in the cloud, isn’t the cloud backing it up for me, like iCloud?”&lt;p&gt;I have an AWS Solution Architect Professional certification and agree you could get a cert and still not be qualified to run or design much on AWS but it does put you ahead of much of what I’ve seen out there.</text></item></parent_chain><comment><author>halbritt</author><text>They call this &amp;quot;lift and shift&amp;quot;.&lt;p&gt;It&amp;#x27;s a terrible idea, but cloud providers love it because they end up getting paid a lot of money for idle capacity.</text></comment>