Acronis Cyber Cloud: Branding Web Console URL
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 all Acronis Cyber Cloud services: Acronis Backup Cloud, Acronis Disaster Recovery Cloud, Acronis Files Cloud, Acronis Notary, Acronis Storage.
Here is how to set this up:
- 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 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 - 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.
- Set up the following CNAME record: cloud.example.com → cloud.acronis.com .
- 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 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
- You have an account in only one Acronis data center. This is a typical case.
- 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 ).
- 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.
- 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 '<…>'):
-----BEGIN CERTIFICATE-----
MIIRYDCCEEigAwIBAgIQBaXDvDN9wk6EZT3Ap/pFZjANBgkqhkiG9w0BAQsFADBw
MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3
<…>
IBf/w6TsZu2XsjePfO+dcA9/2i0aHmLs6bkKMqSt7J1nsNiNCbZQtkQUbdZYpqpI
7aW3Be/IF0yUyHu0YudusDk2/aZIKzG6CpkK0ENzkZcJYyA5
-----END CERTIFICATE-----
-----BEGIN PRIVATE KEY-----
FArOLHhvZwbUr9pogUHdm1GxzQ8mnLw9z3xYmWMyAxOVSLYkarUo1qVdYjHXIqYv
3lsEmQdQQQ1V2fvPC2sKV4EAW6cfWUvk8JmM7hvH358CdPMHvxpgL30Z3vCvaVIQ
<…>
1WIw7pmvXRfWdMXkEWjA7yg1UQbJFmCa/rkE7EikeG2TvMhDYrmxf8xKYGqVTppE
KJPZno5R30zxRMHEj4ftok==
-----END PRIVATE KEY-----
-----BEGIN CERTIFICATE-----
MIIEsTCCA5mgAwIBAgIQBOHnpNxc8vNtwCtCuF0VnzANBgkqhkiG9w0BAQsFADBs
MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3
<…>
0wGjIChBWUMo0oHjqvbsezt3tkBigAVBRQHvFwY+3sAzm2fTYS5yh+Rp/BIAV0Ae
cPUeybQ=
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIDxTCCAq2gAwIBAgIQAqxcJmoLQJuPC3nyrkYldzANBgkqhkiG9w0BAQUFADBs
MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3
<…>
vEsXCS+0yx5DaMkHJ8HSXPfqIbloEpw8nL+e/IBcm2PN7EeqJSdnoDfzAIJ9VNep
+OkuE6N36B9K
-----END CERTIFICATE----- - Send the following information to Acronis Customer Central :
- The desired domain name (such as cloud.example.com).
- The .pem or .pfx file that you prepared in the previous step.
- 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.
- Optionally, the URL to the browser favicon that your users will see instead of the default one when logging in to your domain. For example: http://example.com/favicon.ico . Both HTTP and HTTPS URLs are supported. You need to provide the URL, not the file itself.
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 .