AWS Architect Certification Training
- 51k Enrolled Learners
- Live Class
Irrespective of the business, organizations always experience competition. Hence staying updated with the market needs, becomes a must, and ‘time’ becomes an integral constituent. What if there was a way business could focus on their business goals and outsource their maintenance and monitoring tasks somewhere else. Would that help save time & meet the market needs with more efficiency? Migrating to cloud lets you do exactly the same. This AWS Migration article would walk you through all the necessary pointers that you need to consider before you plan to migrate to Cloud.
For starters, let me define Migration for you:
Business is no easy task when it comes to handling situations like security, scaling up or down, etc. Let’s look at a few scenarios where AWS Migration could be a better resort.
Migrating your project means moving your data from the on-premise data center to cloud. FYI we are not referring to clouds in the sky. In this case, cloud is the virtualization used over a data center to make the functionalities more flexible. Many companies like GoDaddy, Expedia etc., have recently moved their business to cloud.
Having defined Migration, let me tell you where, how, and who is going to help you migrate your data. The implementation is provided by Amazon Web Services (AWS). So, let’s find out what AWS is?
You can learn more here: What is Cloud computing?
Amazon Web Services (AWS) is a subsidiary of Amazon.com which provides on-demand cloud services. AWS made a debut in 2006 with a few services. Then, in 2012 launched the AWS Marketplace that accommodated a vast range of services provided by AWS.
Data Migration seems an easy process because in layman’s term, it means moving your data from one location to the other. However, it is more complex as the process involves different phases. Let me now talk about the various phases of Migration:
There are times you need not require to move your entire business to the cloud.This is where segregation is important. You need to identify the applications which can be Migrated and which cannot. This is what the first phase is all about. Now, let’s go to Phase 2 i.e. choosing the method for AWS Migration.
Depending on the data, AWS provides different ways to Migrate your application e.g. AWS Snowball, AWS Snowmobile, AWS Direct Connect, etc. Once you have chosen an appropriate way to move your data, also look for the resources you’ll need for it. Let’s now explore the different ways of storing data on AWS Cloud in Phase 3.
Once you know how and what you are migrating, next, you have to figure out how and where you will store it. The entire motive of moving to AWS is to minimize expenses. In this phase, you’ll test your workload and understand about AWS Storage Service, their benefits, limitations, and the necessary security controls.
Now that you have all the pre-requisites like the blueprint, Migration tools, list of assignments, backups and its synchronization with your on-premises data repositories. You can finally migrate your project to AWS Cloud. Once you have Migrated your project to cloud, reliability, and durability are the added benefits you get. Let’s see the changes AWS brings to your architecture in Phase 5.
At this point, you’ve already migrated to AWS, and AWS will bring updates that you’ll need to incorporate in your existing architecture. Hence, you must ensure that you have a 24×7 support team keeping track of system maintenance and upgrades after the Migration.
The complexity of migrating existing applications varies, depending on the architecture, Amazon came up with different strategies which they commonly termed as 6 R’s. Let’s look into each of them:
AWS Migration gives your organization limitless benefits. Let’s look into the major ones in brief.
These were the benefits of AWS Migration. Let’s jump into the services offered by AWS to ease the process of Migration.
Out of the many tools provided by Amazon to automate data migration, I’ll be talking about the more commonly used ones.
Now that you know everything about AWS, and AWS Migration, let me show you a use case where you will be migrating a Virtual OS from my local machine to AWS Cloud.
You will be migrating an on-premise Virtual OS running on VMWare to AWS using Import/Export (AWS Direct Connect) method.
1. Create a .vmdk export file for Ubuntu 14.04.
2. Download & configure AWS CLI.
3. Create an IAM User.
Now click on “Add User”.
Next, select a unique User name.
Now give Administrator access.
Click on Create User.
4. Create an S3 bucket and add file(image file of the OS).
Select a unique Username.
Review and Create Bucket.
Add the exported .vmdk file.
Click on Upload.
Wait till the image reflect on the list.
5. You can upload the file using AWS CLI also.
6. Once the file is uploaded, create an AMI for the imported image file.
Your image is now available as an AMI.
7. You can run the AMI created in two ways:-
7 (a). Using CMDER :
Copy the connection string and paste it to the CMDER Console, it will take few minutes to connect and then will open your Ubuntu 14.04.
7 (b). Using Putty :
Configure the .pem file to your Putty and provide the username and the connection string. It will show initializing and few minutes later you will land on to Ubuntu 14.04.
In this way, we have successfully migrated a virtual OS on AWS. I hope you enjoyed reading this AWS Migration article.
If you want the source code to configure AWS CLI, please comment below.
If you wish to learn AWS Migration and migrate your own applications, then check out our Migrating Applications to AWS Training which comes with instructor-led live training and real-life project experience. This training will help you understand Migration in depth and help you achieve mastery over the subject.
Got a question for us? Please mention it in the comments section of ”AWS Migration” and we will get back to you.