Some hostname configurations, including apex/root domains, have additional DNS requirements. Before provisioning, review Domain Management limitations to confirm that your DNS configuration is supported.
To route traffic securely through Acquia Edge Standard, you must provision your hostname on the Edge network, validate hostname ownership, and update your authoritative DNS records.
Configuring hostnames
Starting status: Not configured After this step: Ownership validation pending
The provisioning process begins on the Domains page in the Acquia Cloud Platform user interface.
To initiate hostname configuration:
Locate the hostname in the Domains table.
Open the Actions menu and select Validate Ownership.
Confirm that the status changes to Ownership validation pending.
Validating hostname ownership
Provision a hostname
Important
Some hostname configurations, including apex/root domains, have additional DNS requirements. Before provisioning, review Domain Management limitations to confirm that your DNS configuration is supported.
To route traffic securely through Acquia Edge Standard, you must provision your hostname on the Edge network, validate hostname ownership, and update your authoritative DNS records.
Configuring hostnames
Starting status: Not configured After this step: Ownership validation pending
The provisioning process begins on the Domains page in the Acquia Cloud Platform user interface.
To initiate hostname configuration:
Locate the hostname in the Domains table.
Open the Actions menu and select Validate Ownership.
Confirm that the status changes to Ownership validation pending.
Validating hostname ownership
Starting status: Ownership validation pending After this step: Connecting to Edge
After the status changes to Ownership validation pending, you must add the required DNS record to prove hostname control. Complete this step before the hostname connects to the Edge network and before an SSL certificate can be issued.
To validate hostname ownership:
Open the DNS Information panel to retrieve your validation DNS record details.
Sign in to your DNS registrar account. Common DNS registrars include GoDaddy and Amazon Web Services Route 53.
Add the SSL CNAME record as a new entry in your DNS configuration:
Set the hostname to _acme-challenge.<yourhostname>. For example, use _acme-challenge.www.example.com for the hostname www.example.com.
Set the value to the CNAME target displayed in the DNS Information panel.
Allow time for DNS propagation. The platform automatically polls for record detection every few minutes.
Confirm that the record is detected. The hostname status automatically advances to Connecting to Edge.
Waiting for Edge connection and SSL certificate provisioning
Starting status: Connecting to Edge After this step: Ready for DNS repointing
During this phase, the platform completes the following steps automatically:
The platform adds the hostname to the Acquia Edge network.
The platform automatically provisions an SSL certificate for your hostname.
This phase typically completes within a few minutes and requires no user action. When finished, the status changes to Ready for DNS repointing.
Testing hostname on Edge Standard (Optional)
This is a recommended validation step before updating production DNS to route live traffic through Acquia Edge Standard.
Look up the IP address for your Acquia Edge CNAME target.
Update your local hosts file to map one of the IP addresses to your hostname.
Visit the hostname in your browser to verify that functionality is working correctly.
Repointing production DNS
Starting status: Ready for DNS repointing After this step: Configured
To complete provisioning, update your production DNS to route live traffic through Acquia Edge Standard:
Copy the Acquia Edge CNAME target from the DNS Information panel.
Sign in to your DNS registrar account.
Update your authoritative DNS record to point your hostname to the copied Acquia Edge CNAME target.
Confirm that live traffic routes through the Edge network, after which the status becomes Configured.
SSL certificate management
Acquia Edge Standard automatically manages SSL certificate lifecycles for all configured hostnames:
Automated provisioning and renewal: SSL certificates are provisioned automatically during the Connecting to Edge phase and renewed without manual action.
No custom certificate support: Externally uploaded certificates and bring-your-own-certificate configurations are not supported.
Origin certificate requirement: The Cloud Platform origin must present a valid, trusted SSL certificate to maintain secure connections between Acquia Edge Standard and Cloud Platform.
Starting status: Ownership validation pending After this step: Connecting to Edge
After the status changes to Ownership validation pending, you must add the required DNS record to prove hostname control. Complete this step before the hostname connects to the Edge network and before an SSL certificate can be issued.
To validate hostname ownership:
Open the DNS Information panel to retrieve your validation DNS record details.
Sign in to your DNS registrar account. Common DNS registrars include GoDaddy and Amazon Web Services Route 53.
Add the SSL CNAME record as a new entry in your DNS configuration:
Set the hostname to _acme-challenge.<yourhostname>. For example, use _acme-challenge.www.example.com for the hostname www.example.com.
Set the value to the CNAME target displayed in the DNS Information panel.
Allow time for DNS propagation. The platform automatically polls for record detection every few minutes.
Confirm that the record is detected. The hostname status automatically advances to Connecting to Edge.
Waiting for Edge connection and SSL certificate provisioning
Starting status: Connecting to Edge After this step: Ready for DNS repointing
During this phase, the platform completes the following steps automatically:
The platform adds the hostname to the Acquia Edge network.
The platform automatically provisions an SSL certificate for your hostname.
This phase typically completes within a few minutes and requires no user action. When finished, the status changes to Ready for DNS repointing.
Testing hostname on Edge Standard (Optional)
This is a recommended validation step before updating production DNS to route live traffic through Acquia Edge Standard.
Look up the IP address for your Acquia Edge CNAME target.
Update your local hosts file to map one of the IP addresses to your hostname.
Visit the hostname in your browser to verify that functionality is working correctly.
Repointing production DNS
Starting status: Ready for DNS repointing After this step: Configured
To complete provisioning, update your production DNS to route live traffic through Acquia Edge Standard:
Copy the Acquia Edge CNAME target from the DNS Information panel.
Sign in to your DNS registrar account.
Update your authoritative DNS record to point your hostname to the copied Acquia Edge CNAME target.
Confirm that live traffic routes through the Edge network, after which the status becomes Configured.
SSL certificate management
Acquia Edge Standard automatically manages SSL certificate lifecycles for all configured hostnames:
Automated provisioning and renewal: SSL certificates are provisioned automatically during the Connecting to Edge phase and renewed without manual action.
No custom certificate support: Externally uploaded certificates and bring-your-own-certificate configurations are not supported.
Origin certificate requirement: The Cloud Platform origin must present a valid, trusted SSL certificate to maintain secure connections between Acquia Edge Standard and Cloud Platform.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Edge Standard