Deploy CloudCheckr FinanceManager from the Azure Marketplace

Apart from installing CloudCheckr FinanceManager in any on-premise environment, you can also deploy it from the Azure Marketplace.

Deploying CloudCheckr FinanceManager on the Azure Marketplace is straight forward, and you can complete it in a few minutes in your Azure Portal.


Follow this workflow to complete your deploy:

  1. Log in to the Azure portal and go to the Marketplace to search for the offer:

    Once you’ve selected the offering, you should see the following screen:

  2. Click Create.

    The Deployment Wizard displays.

  3. Type your username and password.
  4. Select your deployment Resource Group and click OK.
    Make sure to write down this username and password, as you will need these when connecting to the Windows server using the Remote Desktop Protocol (RDP).
  5. Click Select to pick a recommended VM size type that has enough CPU’s and Memory (see the installation page for general system requirements). Smaller machines are possible, but will influence performance:
  6. You may select any additional options, but none are required for running CloudCheckr FinanceManager successfully, so you may skip this page simply by clicking OK.
  7. Review the summary and click Create to deploy your VM:

    This may take a few minutes. You may review the status of the Virtual Machine in your VM list:

  8. Write the Public IP address once it is available. Optionally, you may configure a custom DNS name to have an easy way to connect.

You can log in to your instance with RDP, but you should be able to connect to your instance using the public IP address or DNS name of your instance considering the following default URL:

  • https://_<Your_Public_IP>_:8001

By default, no data is loaded into the system, so you’ll have to create a new extractor for obtaining consumption data and a transformer to process that data. A Report Definition is then created to be able to report on your consumption metrics and costs.

CloudCheckr FinanceManager comes standard with an insecure self-signed SSL certificate. It's recommended to replace the default certificate with an official one, signed by your Certificate Authority. To install a signed certificate, follow this procedure:

  1. Download the 32-bit version of openssl.exe from Win32/Win64 OpenSSL Installation, and install this tool on the server.
  2. Use the openssl.exe to generate a valid key file on the server by executing the following command:
    • C:\TEMP>c:\location\to\openssl.exe genrsa -out CLOUDCHECKRFINANCEMANAGER.key 4096
  3. Run the following command to create a certificate signing request file:
    • C:\TEMP>c:\location\to\openssl.exe req -new -key CLOUDCHECKRFINANCEMANAGER.key -out CLOUDCHECKRFINANCEMANAGER.csr
  4. Provide the general information and be sure to include the FQDN of the CloudCheckr FinanceManager server when asked for:
    • ‘Common Name (e.g. server FQDN or YOUR name) []’
      When asked for a password, leave this field blank and press Enter. Otherwise, CloudCheckr FinanceManager cannot use your certificate.
  5. Send the generated CSR file to your Certificate Authority. After your CA processes it, you should receive a .CRT file.
  6. Rename this file to CLOUDCHECKRFINANCEMANAGER.crt and copy it, together with your CloudCheckr FinanceManager.key file, in your %CloudCheckr FinanceManager_PROGRAM_PATH%\server\nginx\conf. This should overwrite the existing key and crt files.
  7. Restart the CloudCheckr FinanceManager Web Service Windows service, and your signed certificate should now be active.

Work with your IT Networking team to configure your domain name, so that the new server name points to the CloudCheckr FinanceManager IP address.

We recommend you use the DNS Server Tools as your DNS provider.

If you need more assistance, review our Installation page or drop us an e-mail or create a ticket in our support portal.

How did we do?