58275: Acronis Cyber Cloud: Branding Web Console URL

Last update: 15-06-2021

Suppose that you want to make Acronis Cyber Cloud services available from your domain: cloud.example.com (in the guidelines below, replace cloud.example.com with your domain name). This customization is available starting with version 6.0 of Acronis Cyber Cloud. This feature is applicable to Acronis Cyber Cloud services.

Please make sure that the branding is enabled for the group id you wish to use for URL customization.
It is not possible to customize URL for each service separately (like backup.example.com and files.example com). Each service will have an URL like: cloud.example.com/mc, cloud.example.com/bc, cloud.example.com/fc cloud.example.com/notary
It is not possible to use the same DNS name for multiple groups.

Here is how to set this up:

  1. Ask your DNS registrar to set up a CNAME record to resolve the name cloud.example.com into the respective Acronis domain name.
    Do one of the following depending on whether you have an account in only one Acronis data center or in multiple data centers.

    • You have an account in only one Acronis data center. This is a typical case.
      Set up a single CNAME record to resolve the name cloud.example.com into an Acronis domain name according to the data center where your account is located.

      Data center CNAME record
      Australia (Sydney) cloud.example.com → au1-cloud.acronis.com
      France (Strasbourg) cloud.example.com → eu-cloud.acronis.com
      Germany, “EU2” data center (Frankfurt) cloud.example.com → eu2-cloud.acronis.com
      Germany, “EU4” data center (Frankfurt) cloud.example.com → eu4-cloud.acronis.com
      Germany, “EU8” data center (Frankfurt) cloud.example.com → eu8-cloud.acronis.com
      Switzerland (Zurich) cloud.example.com → eu5-cloud.acronis.com
      Japan (Tokyo) cloud.example.com → jp-cloud.acronis.com
      Russia (Moscow) cloud.example.com → ru2-cloud.acronis.com
      Singapore cloud.example.com → sg-cloud.acronis.com
      United Kingdom (London) cloud.example.com → eu-cloud.acronis.com
      United States, "US2" data center (Ashburn) cloud.example.com →  us-cloud.acronis.com
      United States, "US3" data center (St.Louis) cloud.example.com →  us3-cloud.acronis.com
      United States, "US4" data center (Ashburn) cloud.example.com →  us4-cloud.acronis.com
      United States, "US5" data center (Ashburn) cloud.example.com →  us5-cloud.acronis.com
      Bhutan, "BT01" data center (PBH1)  cloud.example.com →  bt01-cloud.acronis.com
      Canada, "CA01" data center (YVR1)  cloud.example.com →  ca01-cloud.acronis.com
      New Zealand, "NZ01" data center (AKL1) cloud.example.com →  nz01-cloud.acronis.com
      Liechtenstein, "LI01" data center (ACH1) cloud.example.com →  li01-cloud.acronis.com
      Spain, "ES01" data center (VLC1) cloud.example.com →  es01-cloud.acronis.com
      Israel, "IL01" data center (TLV1) cloud.example.com →  il01-cloud.acronis.com
      Korea, "KR01" data center (ICN1) cloud.example.com →  kr01-cloud.acronis.com
      Czech Republic, "CZ01" data center (PRG1) cloud.example.com →  cz01-cloud.acronis.com
      Portugal, "PT01" data center (LIS1) cloud.example.com →  pt01-cloud.acronis.com
      Brazil, "BR01" data center (GRU1) cloud.example.com → br01-cloud.acronis.com
      Greece, "GR01" data center (SKG1) cloud.example.com →  gr01-cloud.acronis.com
      Poland, "PL01" data center (WAW1)  cloud.example.com →  pl01-cloud.acronis.com
      Denmark, "DK01" data center (BLL1) cloud.example.com →  dk01-cloud.acronis.com
      Bulgaria, "BG01" data center (SOF1) cloud.example.com →  bg01-cloud.acronis.com
      Austria, "AT01" data center (VIE1) cloud.example.com →  at01-cloud.acronis.com
      Japan, "JP03" data center (HND1) cloud.example.com →  jp03-cloud.acronis.com
      India, "IN01" data center (BOM1) cloud.example.com → in01-cloud.acronis.com
    • You have accounts in multiple Acronis data centers worldwide (meaning that Acronis has provided you with separate logins from different groups), and you want to use a single domain name to work with all of them. This case normally applies to larger service providers and to providers whose users are spread across continents.
      1. Set up the following CNAME record: cloud.example.comcloud.acronis.com.
      2. In addition, set up CNAME records for each Acronis data center where you have an account, as follows:
        Data center Additional CNAME record
        Australia (Sydney) au1-cloud.example.com → au1-cloud.acronis.com
        France (Strasbourg) eu-cloud.example.com → eu-cloud.acronis.com
        Germany, “EU2” data center (Frankfurt) eu2-cloud.example.com → eu2-cloud.acronis.com
        Germany, “EU4” data center (Frankfurt) eu4-cloud.example.com → eu4-cloud.acronis.com
        Germany, “EU8” data center (Frankfurt) eu8-cloud.example.com → eu8-cloud.acronis.com
        Switzerland (Zurich) eu5-cloud.example.com → eu5-cloud.acronis.com
        Japan (Tokyo) jp-cloud.example.com → jp-cloud.acronis.com
        Russia (Moscow) ru2-cloud.example.com → ru2-cloud.acronis.com
        Singapore sg-cloud.example.com → sg-cloud.acronis.com
        United Kingdom (London) eu-cloud.example.com → eu-cloud.acronis.com
        United States, "US2" data center (Ashburn) us-cloud.example.com → us-cloud.acronis.com
        United States, "US3" data center (St.Louis) us3-cloud.example.com → us3-cloud.acronis.com
        United States, "US4" data center (Ashburn) us4-cloud.example.com → us4-cloud.acronis.com
        United States, "US5" data center (Ashburn) us5-cloud.example.com → us5-cloud.acronis.com
        Bhutan, "BT01" data center (PBH1) bt01-cloud.example.com → bt01-cloud.acronis.com
        Canada, "CA01" data center (YVR1)  ca01-cloud.example.com → ca01-cloud.acronis.com
        New Zealand, "NZ01" data center (AKL1) nz01-cloud.example.com → nz01-cloud.acronis.com
        Liechtenstein, "LI01" data center (ACH1) li01-cloud.example.com → li01-cloud.acronis.com
        Spain, "ES01" data center (VLC1) es01-cloud.example.com → es01-cloud.acronis.com
        Israel, "IL01" data center (TLV1) il01-cloud.example.com → il01-cloud.acronis.com
        Korea, "KR01" data center (ICN1) cloud.example.com →  kr01-cloud.acronis.com
        Czech Republic, "CZ01" data center (PRG1) cz01-cloud.example.com → cz01-cloud.acronis.com
        Portugal, "PT01" data center (LIS1) pt01-cloud.example.com → pt01-cloud.acronis.com
        Brazil, "BR01" data center (GRU1) br01-cloud.example.com → br01-cloud.acronis.com
        Greece, "GR01" data center (SKG1) gr01-cloud.example.com → gr01-cloud.acronis.com
        Poland, "PL01" data center (WAW1) pl01-cloud.example.com → pl01-cloud.acronis.com
        Denmark, "DK01" data center (BLL1) dk01-cloud.example.com → dk01-cloud.acronis.com
        Bulgaria, "BG01" data center (SOF1) bg01-cloud.example.com → bg01-cloud.acronis.com
        Austria, "AT01" data center (VIE1) at01-cloud.example.com → at01-cloud.acronis.com
        Japan, "JP03" data center (HND1) jp03-cloud.example.com → jp03-cloud.acronis.com
        India, "IN01" data center (BOM1) in01-cloud.example.com → in01-cloud.acronis.com
  2. Create a Certificate Sign Request for an SSL certificate for the domain name (or names) that you created in the previous step. As a security best practice, we recommend that you request a certificate for those names only; to do this, specify each name (such as cloud.example.com) in the Subject Alt Name field of the request. Alternatively, you can request a wildcard certificate (that is, a certificate whose Common Name is *.example.com).
  3. Send the Certificate Sign Request to the certificate authority (CA) for signing the certificate. Acronis Cyber Cloud supports both standard and Extended Validation (EV) certificates.
  4. After you receive the signed certificate, create a single .pem file that contains the following (in any order): your certificate, the private key for your certificate, and all the intermediate certificates, including the root certificate of the CA. No empty lines are allowed in the file.
    Instead of creating and sending a .pem file, you can send a corresponding Personal Information Exchange (.pfx) file, which normally contains all the necessary information about the certificate.

    For example, your .pem file may look as follows (omitted lines are marked with ‘<…>’):

    -----END CERTIFICATE-----
    -----BEGIN PRIVATE KEY-----
    -----END PRIVATE KEY-----
    -----END CERTIFICATE-----
    -----END CERTIFICATE-----

  5. Send the following information to Acronis Customer Central:
    1. The desired domain name (such as cloud.example.com).
    2. The .pem or .pfx file that you prepared in the previous step.
    3. The name of your tenant in Acronis Cyber Cloud and the datacenter in which this group is located. You can also include the URL that is shown when you click the group in the list; for example: https://cloud.acronis.com/#groups/69642. If you have groups in multiple Acronis datacenters, please provide this information about each of those groups.
    4. Optionally, the favicon file that your users will see instead of the default one when logging in to your domain. 

    Alternatively, you can upload it to a folder on your secure server and provide the credentials to that folder.

Once you send the file and set up the CNAME record, Acronis Cyber Cloud services normally become available for your domain within a few business days. Your clients will be able to log in to the service by going to https://cloud.example.com.