What does an AWS server Migration developer do?
An AWS server migration developer automates the rehosting of on-premises or cloud servers into Amazon EC2 using AWS Transform MGN. This specialist installs replication agents, configures launch settings, and manages the full lifecycle from initial data sync to final production cutover. They validate network security prerequisites and coordinate test launches to confirm application functionality before switching live traffic. Their work minimizes downtime by orchestrating precise migration waves through AWS Migration Hub.
- Install and configure the AWS Replication Agent on source servers using required IAM credentials to establish a secure replication channel. This agent continuously copies block-level data from the source environment to AWS staging areas without disrupting ongoing operations. The developer verifies that identity and access management policies grant the necessary permissions for data transfer and instance creation.
- Set up MGN launch settings to control how test and cutover instances are created within the target AWS account. These settings define the specific EC2 instance types, security groups, and subnet placements for migrated workloads. The developer ensures that networking rules allow proper communication between migrated servers and existing cloud resources during validation phases.
- Run test launches to start temporary instances for functional validation before executing the final production cutover. This step allows stakeholders to verify application performance and data integrity in the new environment without affecting live users. The developer monitors replication lag and resolves any configuration errors that arise during these dry runs to guarantee a smooth transition.
- Coordinate cutover launches to switch production traffic to the newly migrated EC2 instances with minimal downtime. This action terminates the replication process and promotes the latest replicated data to a fully operational production state. The developer updates migration status in AWS Migration Hub to reflect the completed transition and tracks post-migration health metrics.
- Define networking and security prerequisites for migration staging and launching to protect data during transit and at rest. This includes configuring virtual private cloud settings, firewall rules, and encryption keys to meet organizational compliance standards. The developer documents these configurations in operational runbooks to support future migration waves and audit requirements.
How to hire an AWS server Migration developer on Upwork
Step 1: Post a job
Define your migration scope by listing specific source environments and target EC2 configurations. The Job Post Generator powered by Uma™, Upwork's Mindful AI drafts a complete post from a few sentences describing your needs. You can write a new post, update a saved draft, or reuse an existing post to start hiring immediately.
- Specify whether you need rehosting via AWS Transform MGN or database moves using AWS Database Migration Service.
- List required IAM credentials and security group rules the freelancer must configure for replication agents.
- State if the role includes validating migration task status within AWS Migration Hub after cutover.
Step 2: Evaluate candidates
Look for portfolios that show configured replication settings and successful test launches into AWS. Uma runs instant video interviews and builds shortlists with side-by-side comparisons to help you assess technical fit quickly.
- Verify experience installing the AWS Replication Agent on Linux or Windows source servers.
- Check for documented runbooks that detail launch settings for both test and production cutover instances.
- Confirm the candidate tracks migration progress and updates status in AWS Migration Hub.
Step 3: Interview your top choices
Discuss how the developer handles network prerequisites and security groups during the staging phase. Schedule and conduct these interviews within Upwork Messages to receive an immediate transcript and summary after each session.
- Ask how they troubleshoot replication failures when the AWS Replication Agent loses connectivity.
- Request examples of how they define launch templates to match production instance types.
- Discuss their process for validating data integrity before running the final cutover launch.
Step 4: Agree on scope and begin work
Set clear milestones for agent installation, test launches, and final cutover execution. Use Upwork Messages and the contract workroom for all communication and project management tasks. Identity verification, payment protection, hourly tracking, and project funds add security to every engagement.
- Milestone one covers installing agents and configuring initial replication settings for all source servers.
- Milestone two requires successful test launches and validation of application functionality in EC2.
- Milestone three includes the final cutover launch and integration configuration for AWS Migration Hub tracking.
Upwork is not affiliated with and does not sponsor or endorse any of the tools or services discussed in this article. These tools and services are provided only as potential options, and each reader and company should take the time needed to adequately analyze and determine the tools or services that would best fit their specific needs and situation.
The rates and information provided in this article are based on current data and industry sources available at the time of publication. Freelance rates can vary depending on factors such as experience, location, project scope, and market conditions. Readers are encouraged to conduct their own research to confirm current rates and trends, as this information may change over time.