Below are some of the tips how to Design an application migration and which component has to placed in which level below are some of the tips for the same
1) If it is publicly accessed web application then we need to design in such a way that initial request is hitting Route 53 then to ELB
Request will hit Route53 from there request will
be forwarded to ELB
2) Number of Subnet's to be created
a) Management subnet, ( Antivirus, to check valid Request),
In Management subnet we will have all management related activities like antivirus, firewall... Even we can place ELB will be in management subnet.
In Management subnet we will have all management related activities like antivirus, firewall... Even we can place ELB will be in management subnet.
b) Web Subnet
Where web application resides. This subnet can either be public or priavte based on application. Inbound rule for this subnet will be like all traffic from management
Where web application resides. This subnet can either be public or priavte based on application. Inbound rule for this subnet will be like all traffic from management
c) Application Subnet
Where the actual application resides. Inbound for this subnet will be like all traffic from web subnet and outbound will be like all traffic to web and data db subnet
Where the actual application resides. Inbound for this subnet will be like all traffic from web subnet and outbound will be like all traffic to web and data db subnet
d) DB subnet
Ports for application for DB will be different, so it is better to create a seperate subnet for DB. Because opening the ports for application in Security group will open the port to DB instances as
well. So it is better to create different subnet. Inbound - only from application
Available tools to migrate.
racemi - migration 80 mb chunks, during migration it
will create a timestamp replica for disk
migration
No comments:
Post a Comment