Before you configure Edge Standard, ensure you meet the following requirements:
Active subscription: You must have an active Acquia Cloud platform subscription with an Edge Standard entitlement.
Acquia purge module: Install the latest version of the Acquia Purge module on your Drupal application to ensure cache invalidation functions correctly.
DNS access: You must have administrative access to your external DNS provider, such as Amazon Web Services (AWS) Route 53 or GoDaddy, to perform ownership validation and traffic repointing.
Acquia ID: Administrative users must be able to log in to the Edge console at Edge Console | Acquia.
Acquia-hosted custom domains: Edge Standard is designed for custom domains such as example.com where you can repoint DNS.
Edge Standard does not currently support the following products or scenarios:
Acquia Cloud Site Factory (ACSF)
Acquia Cloud Professional (ACP)
Node.js applications
Customers requiring Federal Risk and Authorization Management Program (FedRAMP)-compliant WAF or CDN
Multi-Experience Operations (MEO) or multi-region failover setups
SSL certificates: Acquia Edge Standard automatically provisions and manages SSL certificates for all configured domains. Bring Your Own (BYO) certificate is not supported. After DNS validation, certificates generate automatically. Customers remain responsible for maintaining a valid SSL certificate on the Cloud Platform origin. For details, visit Provision a hostname.
Root domains: Support for root (bare) domains is available only if your DNS registrar provides CNAME flattening (ALIAS or ANAME records).
Stacked CDNs: Stacking Edge Standard with other reverse-proxy CDNs (such as Platform CDN) is not supported.
For an overview of all Edge offerings, visit Acquia Edge overview.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.