Code360 powered by Coding Ninjas X Naukri.com. Code360 powered by Coding Ninjas X Naukri.com
Table of contents
1.
Introduction
2.
AWS Application Migration Service
3.
Service architecture and Network architecture
4.
Network Setting Preparations
4.1.
Staging Area Subnet
4.2.
Network Requirements
4.3.
Operational Subnets
5.
Network Requirements
5.1.
Communication over TCP port 443
5.2.
system-basedCommunication between the Staging Area Subnet and Application Migration Service over TCP port 443
5.3.
Communication between the source servers and Application Migration Service over TCP port 443
5.4.
Communication between the source servers and the Staging Area Subnet over TCP port 1500
6.
Frequently Asked Questions
6.1.
What is AWS Application Migration Service?
6.2.
Which port is required for communication between the source server and MGN?
6.3.
Does MGN work with BitLocker encryption?
6.4.
What does the AWS replication agent do?
6.5.
Is the agentless feature available in all Regions that the AWS MGN service supports?
7.
Conclusion
Last Updated: Mar 27, 2024
Medium

AWS Application Migration Service

Author Ankit Kumar
0 upvote
Master Python: Predicting weather forecasts
Speaker
Ashwin Goyal
Product Manager @

Introduction

Earlier, transferring applications from the source server to any physical or virtual cloud infrastructure was a big deal that took a lot of time and resources. It was very difficult to migrate an application, but AWS Application Migration Service made it easy. 

AWS Application Migration Service (MGN) is a rehost solution that simplifies, expedites, and reduces the cost of cloud migration. MGN replicates the source server into an AWS account. The following article will discuss AWS Application Migration Service, Service and Network architecture, Network settings preparation, and Network requirements.

Let's get started with the discussion.

AWS Application Migration Service

The AWS Application Migration Service (MGN) is a highly automated lift-and-shift (rehost) solution that simplifies, accelerates, and lowers the cost of migrating applications to AWS. It allows companies to move many physical, virtual, or cloud servers without worrying about compatibility concerns, performance difficulties, or protracted cutover windows.

Basically, source servers are replicated into your AWS account through MGN. When you're ready, it instantly converts and deploys your servers on AWS, allowing you to immediately reap the benefits of the Cloud's cost savings, productivity, resilience, and agility.

Let us see the architecture of AWS MGN.

Get the tech career you deserve, faster!
Connect with our expert counsellors to understand how to hack your way to success
User rating 4.7/5
1:1 doubt support
95% placement record
Akash Pal
Senior Software Engineer
326% Hike After Job Bootcamp
Himanshu Gusain
Programmer Analyst
32 LPA After Job Bootcamp
After Job
Bootcamp

Service architecture and Network architecture

The following diagram shows the MGN network architecture. 

MGN Network Architecture

Source: https://docs.aws.amazon.com/mgn/latest/ug/Network-Settings-Video.html

 

AWS MGN supports Windows and Linux operating systems. On the left side, we have the source environment, which includes the combination of physical, virtual or cloud servers. The source environment has two servers in the above diagram, one at the top with two disks and the other at the bottom with three disks. And on the right side, there's an AWS region where the server will be migrated. Here the subnets have already been defined.

First, install the AWS replication agent on source servers. Then the agent performs an authentication handshake against the AWS MGN API endpoint, which is encrypted with TLS 1.3. This registers the agent with the service and automatically provisions the staging area subnet resources for every source disk replicated. For data synchronization, AWS MGN generates a similarly sized EBS volume in the staging area subnet. After the staging area subnets are made, the replication begins. The data is encrypted and sent straight from the source server to the volume on the replication server. Then the replicated servers are launched. After the successful launch, the newly created volumes are no longer kept in sync with source servers.

Now we will see the network setting preparation required for the replication.

learn more, Amazon Hirepro

Network Setting Preparations

Network Setting Preparation consists of three components.

Staging Area Subnet

Before implementing the Application Migration Service, You should build a subnet that will be utilized as a staging area for data duplicated from your source servers to AWS via Application Migration Service. This subnet must be specified in the Replication Settings template. Individual source servers can override this subnet in the Replication Settings. 

Network Requirements

The MGN Replication Servers in your Staging Area Subnet must be able to send data to the Application Migration Service API endpoint at the address "https://mgn.region.amazonaws.com/" via TCP port 443.

The source servers must be able to deliver data to the Staging Area Subnet's Replication Servers over TCP port 1500. They must also be able to transmit data to the Application Migration Service API endpoint, which is located at "https://mgn.region.amazonaws.com/".

Operational Subnets

Each source server's test and cutover instances are launched in a subnet you designate in the Amazon EC2 Launch Template. The Amazon EC2 Launch Template is created automatically when you add a source server to Application Migration Service.

Let's discuss different network requirements in AWS MGN.

These were some network settings. Now let's discuss some network requirements.

Network Requirements

Set the following connection settings to prepare your network for running Application Migration Service:

Communication over TCP port 443

Adding the following IP addresses and URLs to the firewall:

  • The Application Migration Service AWS Region-specific Console address:

(mgn.<region>.amazonaws.com example: mgn.eu-west-1.amazonaws.com)

  • Amazon S3 service URLs:

1. The S3 bucket URL of the AWS Region you're utilizing with the Application Migration Service should be accessible to the AWS Replication Agent installation.

2. The Staging Area Subnet should have access to S3.

system-basedCommunication between the Staging Area Subnet and Application Migration Service over TCP port 443

The Staging Area Subnet's Replication Servers must connect with the Application Migration Service on TCP port 443. The following are the principal operations carried out via this route:

  • The Replication Servers are downloading the Replication Software.
  • Replication Servers are connected to Application Migration Service, and their replication status is displayed.
  • Internal troubleshooting and resource utilization data are monitored on the Replication Servers (CPU and RAM).
  • Replication-related occurrences are reported.

Communication between the source servers and Application Migration Service over TCP port 443

Each source server added to the Application Migration Service must connect with the Application Migration Service (mgn.region>.amazonaws.com) continually over TCP port 443.

Communication between the source servers and the Staging Area Subnet over TCP port 1500

Over TCP port 1500, each source server with an AWS Replication Agent installed communicates with the Application Migration Service Replication Servers in the Staging Area Subnet. The transport of duplicated data from the source servers to the Staging Area Subnet requires TCP port 1500.

When data is duplicated and sent over TCP port 1500, it is encrypted and compressed. The data is encrypted on the source infrastructure before being transported to the Staging Area Subnet. After arriving in the Staging AreaSubnet, the data is encrypted before writing to the volumes.

Let's discuss some Frequently asked questions related to the topic.

Frequently Asked Questions

What is AWS Application Migration Service?

AWS Application Migration Service (MGN) is a rehost solution that simplifies, expedites, and reduces the cost of cloud migration.

Which port is required for communication between the source server and MGN?

TCP port 443 needs to be established between the source server and MGN.

Does MGN work with BitLocker encryption?

MGN does not support BitLocker encryption as it is an operating system based disk encryption feature.

What does the AWS replication agent do?

The AWS Replication Agent reads the content of any volume attached to the server at a block level and replicates it to the Replication Server.

Is the agentless feature available in all Regions that the AWS MGN service supports?

Yes. MGN supports both agent-based and agentless replication in all regions.

It's time to summarise the article.

Conclusion

In this article, we have extensively discussed AWS Application Migration System. We learned AWS MGN with examples and also some faqs related to this topic.

After reading about AWS Application Migration Service, are you not feeling excited to read/explore more articles on related topics of AWS? Don't worry; Coding Ninjas has you covered. To learn, see AWS Cloud MapAWS Cloud DirectoryAWS Application Discovery Service, and Data Exchange in AWS.

Refer to our Guided Path on Coding Ninjas Studio to upskill yourself in Data Structures and AlgorithmsCompetitive ProgrammingJavaScriptSystem Design, and many more! If you want to test your competency in coding, you may check out the mock test series and participate in the contests hosted on Coding Ninjas Studio! But if you have just started your learning process and are looking for questions asked by tech giants like Amazon, Microsoft, Uber, etc; you must look at the problems, interview experiences, and interview bundle for placement preparations.

Nevertheless, you may consider our paid courses to give your career an edge over others!

Do upvote our blogs if you find them helpful and engaging!

Happy Learning!

Next article
AWS Migration Hub
Live masterclass