Summary
AWS Migration Process and Setup
e-Gain instructor discussed the importance of understanding the migration process, particularly in the context of AWS. He explained that he would set up an end-to-end migration, launching a Windows machine and making changes to it. He emphasized that he would create a replication server to connect both ends, and that the migration tool would work at a block level. Debajit also mentioned that he would record the entire migration session for future reference. He further explained the process of creating an instance on AWS, selecting the appropriate operating system, and configuring the security group. He also mentioned the use of the AWS migration hub for managing the migration process.
Server Migration Process With AMS
e-gain instructor discussed the process of server migration using the Applications Migration Service (AMS). He explained how to launch an agent, discover server information, and assess server capacity. He also highlighted the use of a heat map for understanding network connections and the data collector for monitoring data collection status. Debajit further detailed the process of adding a server, installing the migration tool, and configuring the migration. He emphasized the need for administrator access and the use of access keys and secret access keys for the migration process. Debajit also demonstrated how to download and install the migration tool on the source server.
AWS Server Migration Process
Instructor explained the process of server migration using AWS. He detailed how the migration tool identifies volumes, replicates data, and creates a replication server. He emphasized that the replication server is crucial as it syncs data between the source and target servers. Debajit also highlighted that the replication server is created using a pre-configured template, and once the initial sync is complete, the target server can be created. He noted that the entire process could take around 30 minutes.
Replication Server Configuration and Options
Instructor discussed the replication server configuration, emphasizing that one server can handle up to 10 volumes. He advised that if a customer has more than 10 volumes, another replication server should be used for better performance. Debajit also mentioned the option of private encrypted migrations and the use of VPN or direct connect for private replication between source and target. He further explained the launch template options, which include the server launch settings, subnet, security group, and post-launch options such as system manager installation or encryption.
Server Replication Process and Status
He discussed the replication process of a server, noting that it was only 41% complete. He explained that the replication process typically takes 30 to 35 minutes for 30GB of storage and that the replication status can be viewed in the Source server. Debajit also mentioned that the replication process can be paused and resumed, and that the replication status can be viewed in the Migration dashboard. He further explained that the replication process involves creating a snapshot from the EBS to EBS replication, which is then used to create the target server. Debajit emphasized that the replication process must be completed in a specific order, with each step being completed before moving on to the next.
Server Migration Cost Estimation
Instructor discussed the process of server migration, emphasizing the importance of understanding the cost implications, particularly for large volumes of data. He explained how to use the AWS Pricing Calculator to estimate costs and suggested starting with less critical servers for migration experience. Debajit also highlighted the importance of grouping servers into applications for easier tracking during migration. He concluded by recommending starting with low priority or non-critical workloads before moving to production servers.
Project Progress and Testing Instances
Instructordiscussed the progress of a project, mentioning that it was almost ready for testing. He explained the process of launching test instances, which takes around 54 minutes, and noted that the 30GB task had been completed. Debajit also mentioned the creation of a new server for testing, which he referred to as the 'conversion server'. He emphasized that this server would be used for testing all functionalities, regression tests, and load tests.
Application Migration Service Overview
Instructor discussed the application migration service, emphasizing the importance of choosing the right instance for each need and the need for stable connectivity between the source and target during migrations. He recommended direct connect for complex and important migrations and stressed the importance of cleaning up resources after testing to avoid unnecessary costs. Debajit also mentioned that the next class would cover lambda and API gateway integrations, as well as cloud permissions.