Migrating to VMware Cloud on AWS: the essentials
So you want to migrate to VMware Cloud on AWS but don't know how? Get to grips with the essentials.
So you want to migrate to VMware Cloud on AWS? We applaud your taste and judgment.
You can expect, in the words of AWS, "consistent and interoperable infrastructure and services between VMware-based datacenters and the AWS cloud" – or, in plain English, the smooth integration of two superb services.
For many enterprises, however, there's a catch. As you'll see from AWS's blurb, this is niche stuff. To paraphrase Atlantan rap group Outkast: "What's nicher than being niche? VMware on AWS."
This means making the move to VMware Cloud on AWS is a bit like buying a bespoke suit or a set of solar panels. You know it's a good decision – but you're also keenly aware that it's a complex and costly one. Get it wrong and you could have a nasty dose of cloud regret.
Well, at Ascend Cloud Solutions we like our customers to be in the loop about our services. Not for us the streams of jargon that seek to obscure and falsely reassure. We want you to know exactly what it is you're signing up for.
In that spirit, we've put together this handy guide to the VMware Cloud on AWS migration process – in particular, moving from an on-premises data centre to the cloud (not from one cloud to another).
But before we dive into the process, let's establish the basics. What is it meant to achieve, exactly?
What does it mean to migrate to VMware Cloud on AWS?
VMware Cloud Migration is all about moving virtual machines (VMs) from your on-premises data centre to VMware Cloud on AWS. The aim: to integrate VMware's software stack within an AWS cloud.
There are three stages to this process: plan, build and migrate. Like any large-scale movement of workloads, each step is crucial and cutting corners isn't an option.
(Incidentally, this is one reason why getting a cloud consultant or MSP on board can be advisable. They understand the intricacies of the process and will execute it with ease. But more of that later.)
First up: planning.
1. Planning
Baseball catcher Yogi Berra (not to be confused with picnic hamper snatcher Yogi Bear) once said "If you don't know where you are going, you'll end up someplace else".
In other words: planning is all. Most of the cloud shock, cloud regrets and cloud headaches suffered by enterprises post-migration are down to poor planning.
It's not so different from moving house. Imagine waking up on moving day and not knowing how much stuff you've got to pack. That's the situation the migrator finds themselves in when they don't analyse and size their on-premises workloads.
Then there are AWS resources, network ranges, DNS strategies and network connections to prepare. All these tasks need to be ticked off before a single workload is migrated.
This is, of course, something that an internal IT team can execute – if they've got the expertise. If not, you'll find yourself squandering time and energy on training someone for a one-off job.
Working with a cloud consultant or MSP can make all the difference. They arrive with all the tools in their toolkit and get the job done swiftly and painlessly.
The alternative isn't necessarily a disaster. But it could be disruptive – and as any business leader knows, disruption is about as welcome as an outbreak of rabies in the office.
Once the planning stage is complete, it's time to build.
2. Build
The planning stage is all about determining your needs. Once this is done, you need to build an infrastructure that meets them.
This means creating a cloud software-defined data centre (SDDC) – a virtualised version of your on-premises data centre's functionalities. Next, you have to configure your shiny new infrastructure so that it can run your existing workloads.
This configuration process is in two parts. First, the network needs to be configured. Then, intra-AWS connectivity. You're not yet building a bridge between the two services – just laying the groundwork.
At this stage, you also have the option of downloading HLM Gateway and enabling VMware Aria Operations for Logs.
With all this in place, moving day is nigh. You're ready to migrate to VMware Cloud on AWS.
3. Migrate
It's now time to shift your workloads. This is done by building a "tunnel" between your on-premises data centre and AWS.
This is achieved with a piece of software called VMware HCX: a SaaS offering that's free to all VMware Cloud on AWS customers. It mobilises applications, letting you move them freely between vSphere versions, on-premises and the cloud.
Once HCX is installed – and tested – your workload migrations can begin. This should be done in waves to ensure a smooth migration.
Each wave should include end-user validation and testing – in other words, you're not dumping the lot on the cloud. Instead, you're moving things bit by bit, checking that all's well before moving on to the next wave.
These waves should be planned to create as little disruption as possible. This is something that a reputable cloud consultant or MSP can help you nail. By showing them your staff diary, you're giving yourself the best possible chance of a frictionless migration process.
How we can help
Whether you're moving from your on-premises data centre to the cloud, or switching to AWS from another provider, you might be wondering whether you can do it in-house. As far as we know, you can – assuming that you have the right skills and expertise to hand.
If not, a cloud consultant or MSP can be the difference between a smooth migration and a rocky road with an uncertain destination. By leveraging external expertise, you're maximising your chances of success.
Either way, we hope the move unlocks new efficiencies and opportunities for your business. Onwards and upwards!
Are you looking for a
managed cloud migration service? At Ascend Cloud Solutions, we've handled more than 400 migrations and counting.
Get in touch today for expert guidance and an honest quote.
