Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.
With the spotlight very much on Cloud technology within the IT industry, it’s difficult to avoid the topic these days. Due to the constant flood of new information, added pressure, emphasis and focus on cloud migration is driving corporations to investigate and understand what ‘the cloud’ actually is and discuss if they should utilise this technology as a potential gain to their business.
As this understanding and knowledge of the Cloud grows, many Senior Directors and CTOs are taking a different look at their own infrastructure estate with one question hanging over their heads: Should we consider migrating some/all of our services to the Cloud?
This article is your guide when asking that very same question.
There are many pieces to consider and some of them will be more applicable to others depending on your line of business, your company size, and your strategy. However, all items should be considered before making a decision to ensure you have sufficient information to deliver a successful Cloud infrastructure environment for you and your customers.
Here are the questions to ask yourself when deciding whether or not to migrate to the cloud:
The first question you should ask yourself is “Do I need the cloud?” Before answering this question you need to have an understanding of what the Cloud can provide you and your business, its features and benefits, its potential gains, and its risks and restrictions. You need to have a grasp of all of these elements and also understand your current on-premise infrastructure estate to be able to make a comparison of the two to ascertain the full scope of benefits to you.
What is driving you to take a leap into the Cloud and harness what it has to offer? Is it a strategic reason? Financial? Something else?
A key aspect and draw of the Cloud is its huge potential cost savings. One main reason for this is that it prevents the need to spend CAPEX (Capital Expenditure are funds used by an organisation to purchase or upgrade physical assets) on your own hardware and all the costs associated with this like provisioning, power and cooling. Also, Cloud services are typically billed as utilities in that you only pay for what you use when you use it. However, be sure to understand ALL of the Cloud costs and how it relates to you and your business. For example, AWS charges for all outbound data transfer leaving the AWS environment and if your business processes large amounts of data that is then sent externally, this is something that needs closer scrutiny.
There are so many different service options provided by public cloud vendors, it’s important to understand what it is exactly you want to migrate to a Cloud environment before investing. Do you want to migrate your entire on-premise Data Centre estate to the Cloud, or just your Web services? Perhaps you only want to use the Cloud for its endless Storage capabilities or as a DR function. Maybe you wish to create a testing and development environment that allows you to spin up and shut down instances on demand, preventing you from having to spend vast amounts of CAPEX on hardware within your own Data Centre. Whatever the reason, the use cases for migrating services to the Cloud are endless and it’s important to have a clear understanding of what it is you need to migrate to the Cloud to make the best use of its power and benefits.
Additional care and attention should be used when looking at storing confidential information in the Cloud to ensure there is sufficient security controls in place and that it meets with your current stringent security standards, as well as any certifications such as ISO/IEC 27001.
You may have services and applications that have been written ‘in house’ and may not be able to fully support many successful and important elements of Cloud technology. For example, elasticity and scalability maybe not be supported by a custom built application. Your application may not be able to function in a decoupled environment where your services are able to work independently of each other (AWS is very good at implementing a decoupled environment, allowing elements of the infrastructure to fail without adverse implications on other aspects of your application). Can your applications benefit from the on-demand element of the Cloud?
It is up to you to ensure that what you want to achieve from the Cloud can be achieved with the services and applications you want to migrate. As a result, you may have to spend time and money to redesign your application to work as expected after migration.
Your reasons to move to the cloud may not be financial, however, the cost of this step is still something that needs to have your consideration. You must ensure you have a full understanding of all the costs that the Cloud services will incur. These include the operational costs, such as the services used themselves, the impact of potential change of bandwidth and data transfer, not to mention the costs of educational training for your employees on how to monitor, manage and control the services. If there is a requirement to redevelop existing applications to make sure they mesh into the Cloud environment, then this must also be factored into your decision.
However, with these costs in mind, there are considerable savings to be had by utilising Cloud services:
For the service(s) you are migrating, check to ensure this makes good financial sense from your current mode of operations? If not, communicate this to your Project sponsor and other key stakeholders in the migration to ensure this is highlighted at the right level of seniority preventing this from being overlooked.
There are many public cloud vendors in the marketplace. According to Gartner’s May 18, 2015 “Magic Quadrant for Cloud Infrastructure as a Service, Worldwide”, Amazon Web Services (AWS ) and Microsoft are the only vendors positioned in the Leaders’ Quadrant.
Many vendors are trying to get a segment of the Public Cloud market share, and each of these vendors offers and proposes different solutions and services that may suit your needs more than others. Carefully research each to identify who has the best suited services and tools to meet your business requirements; this may not necessarily be those positioned in the leaders’ quadrant (Amazon Web Services and Microsoft).*
It is also important to review the SLAs that the vendors offer for each of the services that you will be using. What impact does this have on your current customer contracts? Do the vendors offer any kind of compensation should they breach their SLA? Remember to drill down on the agreement levels for each service and offering you will be utilising to ensure it doesn’t represent issues and problems with your current customer base.
Typically Cloud services are delivered as 3 different models:
You need to be clear on what model you need. You might currently own and control everything to do with your infrastructure on-premise, but perhaps as a part of your migration, you could optimise how much you control and move towards more of a PaaS offering, offloading some of the OS patching responsibility to the Cloud vendor and giving you more time to concentrate on your application development. It is a good idea to use this migration as a means of optimising your current mode of operations; Different offerings could benefit you in more than one way. When migrating, you need to employ a different mindset as moving like-for-like infrastructure is not necessarily the best way to deploy your environment.
When utilising Public Cloud providers, it is likely that you will not want to migrate ALL of your estate to the cloud. Instead, you want the Cloud to be seamlessly linked to your own corporate network as an extension, also known as a Hybrid Cloud environment. Look at the differences between Public and Hybrid Cloud environments as they each offer advantages.
It is important to know where your data is stored with your chosen public provider. You may have to adhere to data laws whereby your data must remain within a certain geographic location. Ensuring you have control over your data, its storage location, and any backup replication service that takes place is crucial in this instance.
Keeping your data as close to the users of that data will result in low latency access, so this is an important factor when architecting your network. Maintaining a strong understanding of where you data is stored and replicated is critical when designing a resilient, highly available environment should there be a major disaster.
When making a change in your infrastructure as huge as migrating one or more service to the Cloud, it generates a fantastic opportunity that can be rare in some environments: it allows you to re-invent you current mode of operations. You have a chance to implement new compute and storage power for your systems, a new network design, and a slicker, more defined environment.
Do not always try to implement a ‘like-for-like’ basis as to what you have on-premise. That environment has possibly grown and been added to as time and the years have gone on, and will likely not be as efficient as it could be. Learn from previous mistakes and look to mitigate any risks you have in your current infrastructure. Look at your end goal, look at the tools available, land ook at the services being offered and how you can utilise the service benefits to your gain. Use this chance to implement an efficient, secure, defined environment that is fully controlled and monitored, making full use of the vendor’s Cloud features.
One important and key element to a successful Cloud migration is to ensure you have the right skill set to identify, analyse, design, implement, and manage the migration. Depending on your requirements, it can be a fairly pain free exercise to move some service to the Cloud, however, has that service and migration been optimised to get the most out of the Cloud? Has the right instance type been used? Has it been designed to ‘self heal’ should a problem occur? Has it been configured with the highest level of security possible at both a network level and an instance level?
It’s one thing to implement a Cloud offering, but it’s entirely another to maximise and architect your infrastructure as a self-healing, fault tolerant, highly available and resilient environment that automatically scales up and down and reacts to traffic demand whilst also performing self-monitoring and event notification services to support teams as and when required.
Implementing a poorly designed Cloud environment can have adverse effects against your original business plan and goals in the reason for migrating in the first place.
Do you have specific timescales to get your infrastructure migrated to a Cloud environment? If so, plan effectively to ensure you have the right resources on hand to implement it correctly and to your specifications. If this is your first migration, be realistic with how long it will take and the learning curve that will inevitably be experienced for your employees; the Cloud is a completely new way of deploying infrastructure. There will be issues and there will be problems as with any new IT infrastructure design and build. Do not underestimate the time required in implementing your solution specifically if it’s for a deadline that can’t be changed. For example, you may be deploying your web services to the Cloud in time for the launch of a new, highly anticipated product where traffic demand to your site is expected to rise dramatically, utilising the scalability and elasticity that the cloud provides. Make sure you are being realistic.
Adopting the Cloud changes the dynamics of the IT department within your organisation no matter what. You will essentially be delivering and managing a new IT service. As a result, there may be new roles that need to be created that didn’t exist before. New processes and procedures will need to be created to aid with the migration and on-going support. New tools and monitoring will need to be deployed and understood to ensure the correct reporting of the infrastructure is still being retrieved to meet SLAs. As noted earlier, you may need to reduce your staff count as some of the roles may no longer be required such as hardware and cabling installation engineers.
One element of the Public Cloud that some people are very wary and cautious of is security. The question of "How safe is my data on the Cloud?" often comes up as many people do not know exactly where their data is. However, it's probably fair to say that Cloud security (when implemented correctly) is likely to be more stringent than you have on your own premises today.
Physical security of Public Cloud providers is managed by the vendor and complies with robust compliance programs to reassure customers of the security they have in place. The security and compliance standards that vendors adhere to is easily available to all. For example, please see the Amazon Web Services whitepaper which covers in detail their physical security and also network and service security details.
Its important to note that Security at an instance and network level is a shared responsibility. The vendor will monitor traffic for vulnerabilities across their estate, while you must ensure you architect your infrastructure in a way that complies to your own security controls through the use of Identity Access Management, Security Group, Access Control Lists, Firewalls, Multi-factor Authentication, and any other means you have in locking down your environment. It is important to have someone with the right skill set who understands Cloud security when migrating your infrastructure. They will be responsible for configuring your data correctly, and managing who can get to it so that it will be highly secure. Each vendor has different security controls so a specialist in your chosen vendor is crucial.
*Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.
By no means are these the only factors to consider when thinking of deploying and migrating services onto the Public cloud, but they will have hopefully made you think of elements that you might not have necessarily considered at this stage within your plans. Should you end up migrating to the cloud, I hope this articles initially helped you decide to harness the full power of what the Cloud has to offer and are now able to reap its full benefits to your organization.
Thank you for taking the time to read my article, if you have any feedback please do leave a comment below.
If you liked this article or found it helpful please click the 'Good Article' button at the bottom of this article, it would be very much appreciated.
I look forward to your comments and suggestions.