So now, from the below chart; we will see as per this blog subject what kind of costly defects can be created and the reasons under different management and team practices, and the work culture lacking scenarios.
How the Costly Cloud Defects can be controlled ?
You can watch the below video.
If you are working in Cloud projects this might be for you to scale up with coaching and mentoring on AWS Solutions usage.
One might have AWS-SAA certificate. But they need the domain knowledge also on how/where/when to use these AWS services. So this coaching gives you that kind of feeling after completion. If you are really keen and ready to spend weekly 15+ hrs for self practice, this might be suitable to scale up in the Cloud era.
So now, we will see as per this blog subject what kind of defects can be created under the below scenario:
Assume the a Cloud engineer joined newly in a job. He might be a fresher for IT and learnt AWS through either online or class room training sessions. He is highly self motivated and proactive. Being fresher with less CTC the employer hired him, instead of taking the infra experienced IT professional with costly CTC. Now they have given the below tasks to complete in a certain hours.
Need to create N number of EC2s and install some software in Y days.
Need to connect those EC2s using SSH and to test the loaded software.
What the Cloud Engineer has done with his mind set and by having limited infra exposure/knowledge ?
a) He created each EC2 separately. Because he did not practice on Boot strapping or IAC options.
b) He installed the required software in each EC2 by using SSH connection. And tested them once they are configured. Which is typical traditional sysadmin activity. But he is using the VMS.
What is the expectation from the Cloud expert/manager [who doesn’t give guidance, but he is more capable in tracking the work ? – we can see many such managers in IT field as trackers to crack the work culture!! ] ?
The manager expect him to write and run a JSON or YAML script to do all the above tasks.
And he expected him to do in a day or two.
But this poor fresher has taken a week time to complete the job by sitting on week-end also.
The management has planned to allocate the planned EC2s on 4th day to distribute to the technical staff where they are going to use for some other technical tasks. But its delayed due to a fresher is deployed for this activitiy.
Now, you as An Experienced Cloud Architect what you are suppose to do while recruiting a fresher for this kind of work?
Are you going to check by which tool he can write JSON or YAML scripts in AWS ?
Is he capable of creating EC2s with bootstrapping options also to install libs and software to save time ?
Is he capable of using Cloudformation template [by creating] along with Ansible to setup small EC2 servers/configurations ?
Do you think if he knows the above tools usage only, is it enough to do the work or plan/design the script properly ?
Are you going to check the Domain infra knowledge also with the candidate ?
Is the planned person and the executor are the same ?
If they are not the same, how the communication happened in between them ?
To meet the schedule; with what techniques/tools to use in the project, was it kept in the Cloud design specifications ? Was it communicated to the Cloud Engineer ?
Was it communicated clearly to the low level resources in the project [Like; Cloud Engineers, Architects, etc] on the design and tools usage as a standard ?
Did they estimate the competency of the existing resources ?
Are there any initial training/mentoring/knowledge transfer activities are lacking ?
So, finally what are the management related process defects you can find in this scenario as an experienced Cloud Architect ?
Obviously, many such kind of questions can strike to the mind set of experienced Infra professionals to dig the root causes of these defects. Such kind of situations are happening across Cloud projects and they are increasing the projects cost instead of decreasing. In many news or blogs we have been watching the management is spending more than the past infra cost for Cloud, so what for ? Because of having not the work culture matured managers in IT ?
So, one need to rethink on their environment also for further progress/process improvements. Even in case of a fresher, an experienced person would have been deployed also he might have done the same way due to lack of IAC/Infra creation knowledge. This comes from the experience or exposure or practice only. Hence the Cloud professionals including so called managers are also mandated to learn these techniques.
Some of them in the past I have observed during my Cloud consulting activities. With that knowledge only I have simulated these defects from my management experience. But these are the realistic issues appearing in Cloud projects.
I have given some solutions related to some of the above technical needs through videos/blogs where a fresher can learn well:
So now, as per this blog subject what kind of defects can be created under the below scenario:
Assume the Cloud Architect assumed the Application level session management is applied in their applications as per the development standards. So with this standards, they can track the sessions used by different users. So the ELB Session management is disabled under cost savings by the Cloud architect. But unfortunately, the past developers not followed the session management standards across the business modules. So when user is trying to create a checkout process in an e-commerce site, his session was appearing with timeout. So this should be the defect from the past application design level defect. So, the business users complained it as it is moved to Cloud the application is not working. So the issues were triggered against the Cloud team rather than the right communication was not followed in the project. The responsible CTO/CIO people never implemented such kind of review process to make sure the application details to supply in all aspects, for right Cloud services designing. Their focus was more on cost savings!!
My questions for Cloud Architect and their management is:
Why did the Cloud Architect assumed without confirming from the right technical people on the session management used for all the modules ?
Do the Cloud Architect need to know the application details also himself without having support from the top people ?
When the Cloud Architect designed the cloud services plan, why the right [top] people did not review and realize it ?
What kind of IT Governance was implemented or enforced here by the CTO/CIO with Cloud Transformation projects ?
Did the management feel they need to safeguard all the role people in IT or just by putting pressure they do create the defects and finally they realize the process defects ? And ultimately pinks slips will be ready for wrong people to get fired ?
What is the management maturity we can find in such kind of situations ?
Did the management realize the Cloud roles correctly and completely and they supported them in this scenario ?
Caution to Cloud professionals:
Hope you as Cloud Architect, could catch what are the specifications you need to ask upfront when they ask you to create such kind of infra in Cloud. You and your team need to realize the Cloud professional role is not just to operate the screen flows as we learnt from the typical Cloud Trainings!! You need to understand the application domain knowledge also.
To know the real specifications for your role visit:
With reference to the booming Cloud Market [refer to some of my videos/blogs] and the Conversions to Cloud by different business organizations; Globally millions of IT professionals were mandated to learn the Cloud technologies to sustain their jobs in IT.
When we talk about these converted IT Professionals, they were forced to move into Cloud due to the sustainability of their job.
At the same time their employers are also enforced by their management to accelerate the cost savings for IT infra.
So how they do the planning for Cloud ?
On top there can be a CTO/CIO plans it to convert into Cloud. And they have the complete knowledge of the infrastructure with reference to their technology being used for business systems.
There will be Cloud Architects, they are responsible to create the Cloud implementation design.
Then the plan and the design is released to the Cloud engineers by allocating the tasks.
In between due to lack of [turn around] time, the Cloud engineers are pressured to create the environments. Here everybody can find one point, the management did not plan the knowledge transfer perfectly to the low level people. Then they can create many costly defects as per their knowledge and experience. So there is no ‘uniformity was followed’ in this case. It need not be a cost effective solution the Cloud Architects or Cloud Engineers have done. And there was no review also done. Once the monthly Cloud bill is arrived they will realize on it. Then they can realize the costly burning/bill happened by comparing to their planned cost saving on Infra. So this way they are enforced to track the resources who created these costly defects.
The following picture has got this kind of analysis. And what are the basic reasons the Architects and Engineers are not able to understand the domain conversion scenarios, when the management plans and release it for implementation.
Here we need to remember, every IT Professional need to realize that one fine day the current size of the resources will not be there in any project due to Cloud and the automation implementation is happening.
So the self matured professional need to realize where they are lacking and step down to learn those from experts, on war footing basis to prove and safeguard their jobs in IT.
If you want to learn the details, I have discussed in the below video with the relevant coaching on AWS-SAA course also.