key recommendations for effective clould computing:

Business can't succeed in the cloud without knowing the fundamentals of effective cloud management and the hidden cloud migrations which must have to avoid. Infrastructure and operations leaders often struggle to understand the role of cloud computing and to develop strategies that exploit its potential. I&O leaders should complete the prerequisites before making the technology decisions required for successful, service-centered cloud computing strategies.

Following are the key recommendations for effective clould computing:  Identify the cloud-computing-related IT services we will offer or procure.

 Document the internal processes that will be affected by the identified cloud services.

 Map applications and workloads to the associated cloud services. Following are the common mistakes which can sink business.

1. Moving to the cloud without a governance and planning strategy:

It’s dead simple to provision infrastructure resources in the cloud, and just as easy to lose sight of the inadvertent policy, security and cost problems that can be incurred. Here, governance and planning are essential.

While governance and planning is the goal, it doesn’t need to be tackled in one sweep, Use small iterations supported with automation, the three critical areas of governance — monitoring/management, security and finance.

A related mistake is not fully understanding who within the organization is responsible for specific cloud-related tasks, such as security, data backups and business continuity.

2. Believing anything can go into the cloud:

Despite a great deal of progress made over the past several years, many applications still aren't cloud ready. A business can seriously damage application performance, user experience and engagement and its bottom line if it sends something to the cloud that isn't fully baked or requires complex integration with legacy systems.

By understanding, what has been planned to gain by making move to the cloud, and then validate that gain as per desired.

3. Treating the cloud like on-premises data center:

A costly mistake many enterprises make is treating their cloud environment like an on- premises data center. While cloud services can deliver dramatic cost savings, it also require an entirely different resource management process or it might end up wasting, not saving, money.

Ashish Shah (Pg. 31-37) 35

Copyright © 2017, Scholarly Research Journal for Interdisciplinary Studies

4. Believing our cloud service provider will handle everything:

Top-tier cloud service providers (CSPs) supply every customer, regardless of size, with operational capabilities equal to a many IT staff members.

Yet, based on the shared responsibility model, CSPs are responsible only for what they can control, primarily service infrastructure components. Many tasks, particularly deploying, maintaining and enforcing security measures, are left to the customer to provide and manage. In short, don’t trust on cloud service provider will take care of everything to our business.

5. Assuming that "lift and shift" is the only clear cloud migration path:

Cloud cost advantages can evaporate quickly when poor strategic or architectural choices are made. A "lift and shift" cloud transition — simply uploading virtualized images of existing in-house systems onto a CSP's infrastructure — is relatively easy to manage, yet potentially cost inefficient and risky over the long term.

The lift and shift approach ignores the elastic scalability to scale up and down on demand, there may be systems within a design that are appropriate to be an exact copy, however placing an entire enterprise architecture directly onto a CSP would be costly and inefficient. Invest the time up front to redesign our architecture for the cloud and we will be benefited greatly.

6. Failing to monitor service performance:

Not regularly evaluating the cloud service actually being received against planned expectations is a quick way to waste money and degrade essential business operations.

An organization should periodically review the established key performance indicators and take proper actions to handle real and potential deviations from planned results.

7. Assuming existing IT staff can immediately handle a leap to the cloud:

Azure, AWS and all other cloud platforms are radically different from the days of a flat, in- house network that can be managed by nearly anyone’s platforms.

If there's no budget for hiring someone specialized in cloud administration, then there should be a considerable time investment in training the IT staffers that can be mustered, prior to moving any bits or computation cycles toward a cloud solution.

Cloud ignorance can easily lead to a security catastrophe. If a malicious actor had gained access to this data, the vast majority of those entities could have faced everything from extortion to complete internal network compromise.

8. Blindly trusting automated scripts:

One of the primary benefits of moving to a cloud-based environment is the automated provisioning and deprovisioning of computing resources.

For the most part, companies will benefit from any type of automation. Yet automated processes that are poorly written, overly complex and not well documented can lead to lengthy downtimes, significantly affecting critical business operations.

"Automated tests for automated scripts in a controlled environment and training for automation recovery could help mitigate this risk" .

Ashish Shah (Pg. 31-37) 36

Copyright © 2017, Scholarly Research Journal for Interdisciplinary Studies

9. Believing security is no longer our problem:

Cloud services, on the whole, offer fantastic security. Because they work with every possible type of company, [CSPs] think about and solve security problems that our own company never faces.

Still, CSPs generally do nothing to correct a customer's poor system management, flaky software development processes or haphazard security policies.

Noting that one of the core issues in the recent Equifax breach was a failure to patch a web server’s software. If Equifax had migrated their application to a managed cloud service, those patches would have been automatic and would have stopped the breach. This failure to properly implement cloud services can leave gaps in cloud security.

10. Neglecting business continuity and disaster recovery planning:

Everything put into the cloud is 100% safe, While it’s true that the larger cloud providers build infrastructure and services with uptime percentages that far exceed levels the average business can achieve, it doesn’t mean they are immune to outages caused by systems and people.

Many cloud services offer automatic backup and recovery options. What would happen if a malicious hacker or disgruntled system administrator deleted critical data? How would it be retrieved? Are there appropriate backup mechanisms in place? All the considerations that apply for on-premises systems also apply for cloud-based systems.