Overview

This guide describes the process of how your domain is migrated from a legacy Partial CNAME configuration to an Acquia Edge Managed CNAME configuration. This migration sets up automatic SSL renewal for domains routing through Acquia Edge powered by Cloudflare, consolidates rules from multiple zones into a single zone, and updates Page Rules to new Rulesets. Acquia issues auto-renewing SSL certificates to minimize downtime during migration.

This guide applies to customers that Acquia has identified as eligible to upgrade to the Managed CNAME program. If you are eligible, an Acquia team member contacts you to discuss the migration process. Customers on a Partial CNAME configuration who are not eligible at this time remain on their current configuration until they become eligible.

During your migration, you complete the following actions:

1. Verify and provide preference order of hostnames being migrated.
2. Confirm that the rules meet the requirements based on the previous configuration.
3. Update the external DNS to route traffic to Acquia Edge Managed CNAME directly.

Acquia Professional Services handles all other tasks, including zone configuration, CDN and WAF rule transfer, DNS routing, hostname creation, and a lite security audit.

Prerequisites

Before you begin, verify the following:

• You have access to your domain DNS provider. Examples include Route 53, Cloudflare, and GoDaddy.
• You have access to Acquia Edge powered by Cloudflare at dash.cloudflare.com.
• You have received your [name].acquiaedge.net CNAME target.

Overview

This guide describes the process of how your domain is migrated from a legacy Partial CNAME configuration to an Acquia Edge Managed CNAME configuration. This migration sets up automatic SSL renewal for domains routing through Acquia Edge powered by Cloudflare, consolidates rules from multiple zones into a single zone, and updates Page Rules to new Rulesets. Acquia issues auto-renewing SSL certificates to minimize downtime during migration.

This guide applies to customers that Acquia has identified as eligible to upgrade to the Managed CNAME program. If you are eligible, an Acquia team member contacts you to discuss the migration process. Customers on a Partial CNAME configuration who are not eligible at this time remain on their current configuration until they become eligible.

During your migration, you complete the following actions:

1. Verify and provide preference order of hostnames being migrated.
2. Confirm that the rules meet the requirements based on the previous configuration.
3. Update the external DNS to route traffic to Acquia Edge Managed CNAME directly.

Acquia Professional Services handles all other tasks, including zone configuration, CDN and WAF rule transfer, DNS routing, hostname creation, and a lite security audit.

Prerequisites

Before you begin, verify the following:

• You have access to your domain DNS provider. Examples include Route 53, Cloudflare, and GoDaddy.
• You have access to Acquia Edge powered by Cloudflare at dash.cloudflare.com.
• You have received your [name].acquiaedge.net CNAME target.

Step 1: Verify hostnames

Acquia Professional Services provides a list of hostnames that are being migrated to the Managed CNAME configuration.

1. Review the list of hostnames.
2. Add notes for any discrepancies or legacy domains that can be removed.
3. Specify the preferred launch order for hostnames.

Step 2: Verify migrated rules

Acquia Professional Services provides documentation showing which rules are being migrated to the Managed CNAME configuration. This document shows how rules are consolidated to streamline rule management.

1. Review the documented rules.
2. Add notes for any discrepancies or concerns related to rule transfers.

Acquia Professional Services adjusts the rules based on feedback provided.

Step 3: Configure DNS routing and populate hostnames

Acquia Professional Services builds the origin DNS routing based on your existing DNS configurations. This sets a default origin server and additional custom origin servers based on data currently configured in DNS.

Acquia Professional Services populates the verified hostnames in the new Managed CNAME configuration as custom hostnames in the order of preference for launch. Acquia Professional Services populates hostnames immediately before launch to ensure timely HTTP validation.

Step 4: Launch hostnames

Acquia Professional Services updates the legacy zone DNS to route traffic to the new Managed CNAME configuration. This results in traffic being processed by the new migrated rules.

1. Update the legacy DNS to route traffic to the new [name].acquiaedge.net configuration.
2. Verify that SSL and hostnames are active.
3. Verify that the site renders without SSL or origin errors.
4. Confirm that the site launch is successful.

Step 5: Complete hostname launches

Acquia Professional Services completes the hostname launches for Step 3 and Step 4 based on the preference order defined in Step 1.

Step 6: Finalize DNS

Acquia Professional Services provides a final document with DNS changes that need to be performed. These DNS changes are performed by the customer with their primary DNS provider.

1. Lower the DNS TTL to 5 minutes or less.
2. Wait until the DNS TTL change has propagated.
3. Update primary DNS records based on the details shared by Professional Services.
4. Verify DNS has propagated.

Step 7: Clean up legacy configurations

Acquia Professional Services performs a cleanup process to remove the legacy zone configurations. After cleanup, only the [name].acquiaedge.net zone remains available in the account.

Tasks handled by Acquia Professional Services

Acquia Professional Services completes the following tasks before and during migration. Customers do not need to take action on these items:

• Security audit and threat assessment
• Zone build and configuration
• WAF rule deployment
• Origin server configuration and health checks
• Cache rules and page rules
• Rate limiting and bot management, if applicable
• Go-live validation