Requirements for Azure connector
The recommended VM size of Azure connector is F4s – 4 vCPUs and 8 GB RAM. Ensure that you have a sufficient Azure CPU quota in the region where you are deploying the connector.
- A Standard Storage Account (cannot be Premium) under which the connector can be deployed.
- A virtual network where the connector can be deployed.
- Allow inbound port 443 within the connector’s virtual network or not to the the public internet to view the connector dashboard.
- Outbound Internet access for AWS, Azure, and so on.
Operating Systems Supported by AWS SMS
- Microsoft Windows Server 2003 R2 or later version
- Ubuntu 12.04 or later
- Red Hat Enterprise Linux (RHEL) 5.1-5.11 or later
- SUSE Linux Enterprise Server 11 with SP1 or later
- CentOS 5.1-5.11, 6.1-6.6, 7.0-7.6
- Debian 6.0.0-6.0.8, 7.0.0-7.8.0, 8.0.0
- Oracle Linux 5.10-5.11 with el5uek kernel
- Fedora Server 19-21
Considerations for Migration Scenarios
- A single Server Migration Connector appliance can only migrate VMs under one subscription and one Azure Region.
- After a Server Migration Connector appliance is deployed, you cannot change its subscription or Region unless you deploy another connector in the new subscription/Region.
- AWS SMS supports deploying any number of Server Migration Connector appliance VMs to support migration from multiple Azure subscriptions and Regions in parallel.
- Step 1: Download the Connector Installation Script
- Step 2: Validate the Integrity and Cryptographic Signature of the Script File
- Step 3: Run the Script
- Step 4: Configure the Connector
- (Alternative Procedure) Deploy the Server Migration Connector Manually
- Step 5. Replicate Azure VM to AWS EC2 instance
Step1: Download the PowerShell script and hash files from the following URLs:
After download, transfer the files to the computer or computers where you plan to run the script.
Step 2: Validate the Integrity and Cryptographic Signature of the Script File
To validate script integrity using cryptographic hashes (PowerShell). Use one or both of the downloaded hash files to validate the integrity of the script file. To validate with the MD5 hash, run the following command in a PowerShell window:
PS C:\Users\Administrator> Get-FileHash aws-sms-azure-setup.ps1 -Algorithm MD5
To validate with the SHA256 hash, run the following command in a PowerShell window:
PS C:\Users\Administrator> Get-FileHash aws-sms-azure-setup.ps1 -Algorithm SHA256
Compare the returned hash values with the values provided in the downloaded files, aws-sms-azure-setup.ps1.md5 and aws-sms-azure-setup.ps1.sha256.
Next, use either PowerShell or the Windows user interface to check that the script file includes a valid signature from AWS. To check the script file for a valid cryptographic signature (PowerShell)
PS C:\Users\Administrator> Get-AuthenticodeSignature aws-sms-azure-setup.ps1 | Select *
To check the script file for a valid cryptographic signature (Windows GUI). In Windows Explorer, open the context (right-click) menu on the script file and choose Properties, Digital Signatures, Amazon Web Services, and Details. Verify that the displayed information contains “This digital signature is OK” and that “Amazon Web Services, Inc.” is the signer.
Step 3: Run the Script
Run this script from any computer with PowerShell 5.1 or later installed.
PS C:\Users\Administrator> Set-ExecutionPolicy -ExecutionPolicy Undefined -Scope CurrentUser
PS C:\Users\Administrator> Set-ExecutionPolicy -ExecutionPolicy UnRestricted -Scope LocalMachine
PS C:\Users\Administrator> Connect-AzAccount
If you’re a Cloud Solution Provider (Azure CSP), the -TenantId value must be a tenant ID.
PS C:\Users\Administrator> Connect-AzAccount -TenantId ‘xxxx-xxxx-xxxx-xxxx’
PS C:\Users\Administrator> Connect-AzureRmAccount -Tenant “xxxx-xxxx-xxxx-xxxx” -SubscriptionId “yyyy-yyyy-yyyy-yyyy”
PS C:\Users\Administrator> .\aws-sms-azure-setup.ps1 -StorageAccountName name -ExistingVNetName name -SubscriptionId id -SubnetName name
StorageAccountName = The name of the Azure storage account where you want to deploy the connector.
ExistingVNetName = The name of the Azure virtual network where you want to deploy the connector.
SubscriptionId = The ID of the subscription to use. The default subscription for the account is used.
SubnetName = The name of the subnet in the virtual network. The subnet named “default” is used.
Step 4: Configure the Connector
RDP to another VM on the same virtual network where you deployed the connector, use Google chrome browser to the connector’s web interface using the following URL, https://ip-address-of-connector
- On the connector landing page, choose Get started now
- Review the license agreement, select the check box, and choose Next.
- Create a password for the connector. The password must meet the displayed criteria. Choose Next.
- On the Network Info page, you can find instructions to perform network-related tasks, such as setting up AWS proxy for the connector. Choose Next.
- On the Log Uploads page, select Upload logs automatically and choose Next.
- On the Server Migration Service page, provide the following information:
- For AWS Region, choose your Region from the list.
- For AWS Credentials, enter the IAM credentials that you created in Configure AWS SMS Permissions and Roles. Choose Next.
- On the Azure Account Verification page, verify that your Azure subscription ID and location are correct. This connector can migrate VMs under this subscription and location. Provide the object ID of the System Assigned Identity of the connector VM, which was provided as output from the deployment script.
- If you successfully set up the connector, the Congratulations page is displayed. To view the health status of the connector, choose Go to connector dashboard.
- To verify that the connector that you registered is listed, open the Connectors page on the Systems Manager console.
(Alternative Procedure) Deploy the Server Migration Connector Manually
Complete this procedure to install the connector manually in your Azure environment.
To install the connector manually
Log into the Azure Portal as a user with administrator permissions for the subscription under which you are deploying this connector.
Make sure that you are ready to supply a Storage Account, its Resource Group, a Virtual Network, and the Azure Region as described in Requirements for Azure connector.
Download the connector VHD and associated files from the URLs in the following table.
Verify the cryptographic integrity of the connector VHD using procedures similar to those described in Step 2: Validate the Integrity and Cryptographic Signature of the Script File.
Upload the connector VHD and associated files to your Storage Account.
$resourceGroupName = “myResourceGroup”
$urlOfUploadedVhd = “https://mystorageaccount.blob.core.windows.net/mycontainer/myUploadedVHD.vhd”
Add-AzVhd -ResourceGroupName $resourceGroupName -Destination $urlOfUploadedVhd -LocalFilePath “E:\Virtual hard disks\myVHD.vhd”
Create a new managed disk with the following parameter values:
$sourceUri = “https://storageaccount.blob.core.windows.net/vhdcontainer/osdisk.vhd”
$osDiskName = “myOsDisk”
$osDisk = New-AzDisk -DiskName $osDiskName –Disk (New-AzDiskConfig -AccountType Standard_LRS -Location $location -CreateOption Import -SourceUri $sourceUri) -ResourceGroupName $destinationResourceGroup
Where $SourceUri or Storage Blob (Choose the VHD blob you uploaded from step 3.c.)
Create a public IP address and NIC
Create the public IP. In this example, the public IP address name is set to myIP.
$ipName = “myIP”
$pip = New-AzPublicIpAddress -Name $ipName -ResourceGroupName $destinationResourceGroup
-Location $location -AllocationMethod Dynamic
Create the NIC. In this example, the NIC name is set to myNicName.
$nicName = “myNicName”
$nic = New-AzNetworkInterface -Name $nicName -ResourceGroupName $destinationResourceGroup -Location $location -SubnetId $vnet.Subnets.Id -PublicIpAddressId $pip.Id -NetworkSecurityGroupId $nsg.Id
Set the VM name and size
$vmName = “myVM”
$vmConfig = New-AzVMConfig -VMName $vmName -VMSize “F4s”
$vm = Add-AzVMNetworkInterface -VM $vmConfig -Id $nic.Id
Add the OS disk
$vm = Set-AzVMOSDisk -VM $vm -ManagedDiskId $osDisk.Id -StorageAccountType Standard_LRS -DiskSizeInGB 128 -CreateOption Attach -Windows
Complete the VM
New-AzVM -ResourceGroupName $destinationResourceGroup -Location $location -VM $vm
Download the two role documents:
Edit SMSConnectorRole.json. Change the name field to sms-connector-role-subscription_id. Then change the AssignableScopes field to match your subscription ID.
Edit SMSConnectorRoleSA.json. Change the name field to sms-connector-role-storage_account. For example, if your account is testStorage, then the name field must be sms-connector-role-testStorage. Then change the AssignableScopes field to match your Subscription, Resource Group, and Storage Account values.
You must use Az CLI or Az PowerShell for this step.
PS C:\Users\Administrator> New-AzRoleDefinition -InputFile C:\Temp\roleDefinition.json
Assign roles to the connector VM. In Azure Portal, choose Storage Account, Access Control, Roles, Add, Add Role Assignment. Choose the role sms-connector-role, assign access to Virtual Machine, and select the connector VM’s System Assigned Identity from the list. Repeat this for the role sms-connector-role-storage_account.
Restart the connector VM to activate the role assignments.
Step 4: Configure the SMS Connector.
This step guides you to replicating Azure VMs Using the AWS SMS Console. Use the AWS SMS console to import your server catalog and migrate your Azure VMs to Amazon EC2. You can perform the following tasks:
- Replicate a server using the console
- Monitor and modify server replication jobs
- Shut down replication
To replicate a VM from Azure to AWS using the console
- Install the Server Migration Connector as described in Getting Started with AWS Server Migration Service, including the configuration of an IAM service role and permissions.
- In a web browser, open the SMS homepage.
- In the navigation menu, choose Connectors. Verify that the connector that you deployed in your Azure environment is shown with a status of healthy.
- If you have not yet imported a catalog, choose Servers, Import server catalog. To reflect new servers added in your Azure environment after your previous import operation, choose Re-import server catalog. This process can take up to a minute.
- Select a server to replicate and choose Create replication job.
- On the Configure server-specific settings page, in the License type column, select the license type for AMIs to be created from the replication job. Windows servers can only use Bring Your Own License (BYOL). Choose Next.
- On the Configure replication job settings page, the following settings are available:
- For Replication job type, choose a value. The One-time migration option triggers a single replication of your server without scheduling repeating replications.
- For Start replication run, configure your replication run to start either immediately or at a later date and time up to 30 days in the future. The date and time settings refer to your browser’s local time.
- For IAM service role, provide (if necessary) the IAM service role that you previously created.
- For Enable automatic AMI deletion, configure AWS SMS to delete older replication AMIs in excess of a number that you provide in the field.
- For Enable AMI Encryption, choose a value. If you choose Yes, AWS SMS encrypts the generated AMIs. Your default CMK is used unless you specify a non-default CMK. For more information, see Amazon EBS Encryption.
- For Enable notifications, choose a value. If you choose Yes, you can configure Amazon Simple Notification Service (Amazon SNS) to notify a list of recipients when the replication job has completed, failed, or been deleted.
- For Pause replication job on consecutive failures, choose a value. The default is set to Yes. If the job encounters consecutive failures, it will be moved to the PausedOnFailure state and not marked Failed immediately.
- Choose Next.
- On the Review page, review your settings. If the settings are correct, choose Create. To change the settings, choose Previous. After a replication job is set up, replication starts automatically at the specified time and interval.
- On the Replication jobs page, select a job and choose Actions, Start replication run. This starts a replication run that does not affect your scheduled replication runs, except in the case that the on-demand run is still ongoing at the time of your scheduled run. In this case, the scheduled run is skipped and rescheduled at the next interval. The same thing happens if a scheduled run is due while a previous scheduled run is still in progress.
- In the AWS SMS console, choose Replication jobs. You can view all replication jobs by scrolling through the table. In the search bar, you can filter the table contents on specific values. Filter the jobs by PausedOnFailure to identify all the paused jobs.
- After you have finished replicating a server, you can delete the replication job. Choose Replication jobs, select the desired job, choose Actions, and then choose Delete replication jobs. In the confirmation window, choose Delete. This stops the replication job and cleans up any artifacts created by the service (for example, the job’s S3 bucket). This does not delete any AMIs created by runs of the stopped job.
- Once Replication is complete, Pause the replication, Shutdown the Azure VM and Power on AWS EC2 instances.
- Once Migration is complete and when you are done using a connector and no longer need it for any replication jobs, you can disassociate it. Choose Connectors and select the connector to disassociate. Choose Disassociate at the top-right corner of its information section and choose Disassociate again in the confirmation window. This action de-registers the connector from AWS SMS.