Acquia Cloud Edge consists of two products that are available for Acquia Cloud Enterprise and Acquia Cloud Site Factory subscriptions:
- Acquia Cloud Edge Protect – Secures your application with protection against distributed denial of service (DDOS) attacks, a Web Application Firewall (WAF), and high-speed DNS. Acquia Cloud Edge Protect examines web traffic looking for suspicious activity.
- Acquia Cloud Edge CDN – Provides a globally load balanced content delivery network (CDN) so that visitors interact with your application at the fastest possible speeds, no matter where on the globe they are located.
Acquia Cloud Edge Protect and Acquia Cloud Edge CDN can be purchased and used together or separately.
Setting up Acquia Cloud Edge
To add Acquia Cloud Edge Protect or Acquia Cloud Edge CDN to your Acquia Cloud Enterprise or Acquia Cloud Site Factory subscription, contact your account manager at Acquia. Acquia will set up and support Acquia Cloud Edge for you.
You can then use the Acquia Cloud Edge web user interface to manage the service for your domains.
Accessing Acquia Cloud Edge
To access the Acquia Cloud Edge web user interface, sign in to Cloudflare using the email address and password provided for your Acquia Cloud Edge account by Acquia.
For more information about how to use Acquia Cloud Edge after it is set up, see the CloudFlare knowledge base.
Testing Acquia Cloud Edge
You can test Acquia Cloud Edge by editing your
/etc/hosts file to point your domain to the CloudFlare IP address for the domain. To do this, complete the following steps:
- Find the IP address of the subdomain to be routed through Acquia Cloud Edge using a command similar to the following:
[domain_name]is your fully qualified domain name.
For example, if your domain name is
test.example.com, the command would be:
The response will appear similar to these results:
; <<>> DiG 9.8.3-P1 <<>> test.example.com.cdn.cloudflare.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64242
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;test.example.com.cdn.cloudflare.net. IN A
;; ANSWER SECTION:
test.example.com.cdn.cloudflare.net. 300 IN A 188.8.131.52
test.example.com.cdn.cloudflare.net. 300 IN A 184.108.40.206
test.example.com.cdn.cloudflare.net. 300 IN A 220.127.116.11
test.example.com.cloudflare.net. 300 IN A 18.104.22.168
test.example.com.cdn.cloudflare.net. 300 IN A 22.214.171.124
- Select one of the IP addresses in the
ANSWER SECTIONof the
- Edit your
/etc/hostsfile to add a line based on the following format, using the IP address and your domain name:
For information about how to edit your
/etc/hostsfile, see the Using an /etc/hosts file for custom domains during development knowledgebase article.
- Enter the domain name in your browser and examine the page response headers.
If Acquia Cloud Edge is functioning properly, you will see that the page response headers include a
Confirm that traffic is going through Acquia Cloud Edge
The first step in testing a site with Acquia Cloud Edge is ensuring that requests to the website are being sent through the Edge network. This can be done in one of two ways:
- Using the browser address bar
www.example.com/cdn-cgi/tracein any browser, where
www.example.comis the domain you are testing. The response will show details similar to the following:
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.134 Safari/537.36
This response identifies that the request was processed by the Edge network.
- Using the Claire plugin for Chrome
The Claire plugin is a free download that you can get from the Chrome web store.
After you install the plugin, any website that you access through the Edge network will cause the plugin to display an orange cloud icon in the Chrome address bar. This provides a visual indicator the request was processed by the Edge network.
If you do not see the expected results, then the domain is not yet correctly configured for Acquia Cloud Edge. Confirm that the DNS configurations have been made correctly.
Acquia Cloud Edge and HTTPS (SSL)
Acquia Cloud Edge CDN and Acquia Cloud Edge Protect include a single SAN certificate per domain that covers the bare domain and wildcard third-level domains. If you want to use your own custom SSL certificates with Acquia Cloud Edge, you can upload the same certificate that you use on Acquia Cloud to Acquia Cloud Edge. If you do this and you change or rekey your SSL certificate, you must apply the updated or new certificate to both Acquia Cloud and Acquia Cloud Edge to maintain consistency and simplify support.
Acquia Cloud Edge typically waits 100 seconds for a response from your backend (origin) servers before timing out. If a response has not been received from your origin server after 100 seconds, the connection is closed and an
Error 524: A timeout occurred will be served. Long-running processes, such as report generation, may trigger this error.
Acquia Cloud Enterprise customers can request a timeout increase to a maximum of 600 seconds. Alternately, the application should be modified to return HTTP responses in the time limit.
Rate limiting of traffic is available as an add-on feature for Acquia Cloud Edge Protect subscribers. If you need to throttle responses from a given IP for a specified amount of time, contact your Acquia account manager for additional details.
Logs and Log sharing
Acquia Cloud Edge supports log sharing, which enables subscribers to access web log data on a per-domain basis. These logs can be forwarded for aggregation and analysis.
Audit logs for Acquia Cloud Edge are retained for eighteen months. Access logs are retained for three days. These logs are accessible to the customer using the Cloudflare API.
Acquia Cloud Edge does not support the Always Online feature.