Skip to main content Link Menu Expand (external link) Document Search Copy Copied
Migrate Linux workloads to Azure

Task 02 - Connect to the on-premises VM

Description

In this task, you will connect to the on-premises APP VM that was created with the ARM template. You will configure the web application running on the VM to connect to the migrated PostgreSQL database, now running in Azure Database for PostgreSQL Flexible Server instance.

Success Criteria

  • The web application is now connected to the migrated database.

Solution

Expand this section to view the solution

  1. In the Azure Portal, navigate to the Resource Group that you created for this lab, then select the On-premises APP VM named similar to terrafirm-onprem-app-vm.

    The Resource group with on-premises workload VM highlighted.

  2. On the Virtual Machine blade, either use the Search function in the left hand menu or click on Bastion. We will use a bastion host as the method to connect to our VMs as this is a more secure method.

    The Virtual machine blade searching for "Bastion".

    The Virtual machine blade with Bastion selected.

  3. Within the Bastion page, enter the following:
    1. Authentication Type VM Password
    2. Username demouser
    3. VM Password <the secure password you created when you created the VMs in Task01>

    The Bastion Connection page.

    Note: You may need to allow popups if they are blocked in your browser.

  4. When connectioned to the VM via the Bastion host you will get a screen like this:

    Copnnection via Bastion host.

  5. Once connected via Bastion, run the following command to install the git utility on the server by using the clipboard within the session:

    Clipboard within the Bastion session.

  6. Click the arrows which will expand the window

    Clipboard within the Bastion session.

  7. Once connected to the VM via the Bastion host, execute the following command to open the orders.php file for the web application in a text editor. The application needs to be configured to connect to the Azure Database for PostgreSQL Flexible Server database that was previously migrated.

     sudo nano /var/www/html/orders.php

    orders.php file is open in editor.

  8. Within the orders.php file, set the following values for the database connection details section to configure it for the Private Endpoint for your Azure Database for PostgreSQL Flexible Server.

    Obtaining the IP address for connecting to the Private Endpoint

    1. host: Enter the IPAddress for the Azure Database for PostgreSQL Flexible Server instance that was previously copied.

    orders.php file with database connection details set.

  9. To save the file, press ^X (ctrl-X) to exit the editor, press Y to save the modified buffer, then press Enter to write the changes to the file.

  10. Open a new browser tab, and navigate to the following URL to test that the web application is installed. Be sure to use http:// since the web application is not currently configured for TLS/SSL.

     http://<ip-address>/orders.php

  11. The web application will look similar to the following screenshot.

    Web application is displayed in web browser.

  12. Note that the database connection IP address has changed from the IP address which was the on-premises PostgreSQL database (typically 10.0.0.4) to the newly migrated database hosted in Azure Database for PostgreSQL Flexible Server.

    Note: The address might be in IPv6 notation.

    Validation of the Web application connected to the migrated PostgreSQL database

You are now in a position to stop the On-premises server that was hosting the database.

  1. In the Azure Portal, navigate to the Resource Group that you created for this lab, then select the On-premises Workload VM named similar to terrafirm-onprem-workload-vm.

    The Resource group with on-premises workload VM highlighted.

  2. Click stop

Stopping the on-premises workload VM .

  1. Click Yes to pop-up requesting that you want to stop the VM.

Congratulations you have migrated the database to Azure and configured the on-premises web application to use this migrated database. You will now Azure Arc-enable the on-premises VM that hosts the web application in the next lab.