Note
For additional information about Acquia Cloud Platform, see its product documentation.
Last updated: November 23, 2020
Acquia will provide the PaaS services described below only if purchased by Customer, as indicated in the Order.
Acquia Cloud Platform Enterprise is a managed Platform as a Service for Customer’s Drupal website(s). Acquia Cloud Platform Enterprise includes all the features of Acquia Cloud Platform, is subject to the Service Level Policy, and includes the additional features set forth below.
Product Version Notice:
On March 24th, 2021, Acquia released an enhanced version of Acquia Cloud Platform named “Acquia Cloud Next”. This version of the product is available to newly provisioned applications that meet all eligibility requirements. For existing applications provisioned on the previous version of Acquia Cloud Platform, hereafter referred to as “Cloud Classic”, Customers shall be notified in advance of any eligible applications or environments being upgraded to Acquia Cloud Next. All information in this document refers to both versions unless explicitly noted otherwise.
Acquia will maintain Customer’s Drupal applications on the Platform during the Subscription Term in the Region as indicated in the Order. Customer may submit an unlimited number of support requests related to the Platform. Such tickets will not be counted towards the Support Services ticket allotment (if applicable) unless such issue was caused by an error in Customer’s website(s). Acquia will conduct daily backups of the Drupal application and related databases for disaster recovery purposes. Customer may also perform on-demand backups and restores.
1.1.1. Drupal Migration Services
Acquia will work with the Customer to migrate the website(s) onto the Platform. Once migrated, Acquia will conduct a light infrastructure audit of the website to determine whether any issues with the website may cause the launch to be unsuccessful. Following such audit, Acquia will disclose any launch blockers to Customer. Customer may elect to fix the launch blockers or engage Acquia at its standard consulting services rates to fix the blockers. If Customer elects not to correct the launch blockers identified by Acquia, any unavailability due to such launch blockers will not be counted when determining unavailability of the website pursuant to the Service Level Policy. Customer may purchase a full infrastructure site audit for an additional fee and subject to a separate Order.
Acquia Cloud Platform provides application platform services for Node.js applications. Deploying Node.js applications on Acquia Cloud Platform requires that the Customer purchase a Node.js platform package along with their Acquia Cloud Platform Enterprise subscription.
The Node.js Service has four main components:
The Node.js Service includes support for the services listed above and the underlying platform infrastructure. Support for Customer’s Node.js application code and any third-party dependencies deployed by the Customer isn’t included.
Acquia provides an integrated content delivery network (CDN) that customers may use to accelerate the delivery of web assets. The Platform CDN leverages global points of presence (POPs) to help customers deliver faster experiences, no matter where their users are located. Use of the Platform CDN requires customers to make authoritative DNS configuration changes to direct visitor requests to the customer domain through the CDN. The CDN is managed by Acquia and does not support any custom configuration. Customers may control the caching behavior of the Platform CDN through HTTP Cache-Control headers and Drupal tag-based invalidation, and full purge of the CDN cache. The Platform CDN does not support the customer’s custom VCL configurations at the CDN or the Acquia Cloud Platform Varnish tiers, or “stacked” CDN implementations where a reverse proxy-based CDN or WAF service is configured in front of or behind the Platform CDN.
For all Acquia Cloud customers who have elected to utilize the Platform CDN, the following Fair Use policy will apply:
| Item | Limit | Implications |
|---|---|---|
| Bandwidth | 200 GB/month | Acquia Account Manager will engage with the customer to explore upgrade to Acquia Edge CDN |
| Domain | 10 | Acquia Account Manager will engage with the customer to explore upgrade to Acquia Edge CDN |
| SSL certificate | 10 | Acquia Account Manager will engage with the customer to explore upgrade to Acquia Edge CDN |
| Cache file size | 20 MB | Exceeding this limit when trying to cache a file results in a 503 Response object too large error |
| Vary objects count | 200 soft, 400 hard | Exceeding the soft limit results in no error. Newer variants displace the oldest. Active fetches from backend are limited to 400 variants. Exceeding this hard limit results in a Too many variants response. Once the fetches complete, objects will be removed until the soft limit is reached. |
| URL size | 8 KB | Exceeding the limit results in a Too long request string error |
| Cookie size | 32 KB | Exceeding the limit results in Platform CDN stripping the cookie and
setting req.http.Fastly-Cookie-Overflow = 1 |
| Request header size | 69 KB | Depending on the circumstances, exceeding the limit can result in Platform CDN closing the client connection abruptly, or it can result in the client either receiving a 502 Gateway Error response with an I/O error in the body, or receiving a 503 Service Unavailable response with a Header overflow error in the body. |
| Response header size | 69 KB | Exceeding the limit results in a 503 backend read error. See Common 503 errors for more info. |
| Request header count | 96 | Exceeding the limit results in a Header overflow error. A small portion of this limit is reserved for internal Platform CDN use, making the practical limit closer to 85. |
| Response header count | 96 | Exceeding the limit results in a Header overflow error. A small portion of this limit is reserved for internal Platform CDN use, making the practical limit closer to 85. |
| req.body size | 8 KB | Exceeding the limit results in the req.body variable being blank.
Request body payload is available in req.body only for payloads
smaller than 8 KB. req.postbody is an alias for req.body. |
| Surrogate key size | 1 KB | Exceeding the limit results in purging API failures stating “Surrogate key too long, must be less than 1024 bytes.” Any keys that exceed the limit will be dropped instead of truncated. |
| Surrogate key header size | 16 KB | Exceeding the limit results in no error and any keys past the one that exceeds the limit will be dropped. |
Acquia Cloud Platform Enterprise includes the following web server administration tasks:
apache.conf changes (such as modify conf change Code Base locations
and add new sites) [Customization of this file may not be available for
environments running on Acquia Cloud Next technologies]php.ini changes (such as adjust memory limit or enable error logging)
[Customization of this file may not be available for environments running
on Acquia Cloud Next technologies]my.cnf changes (such as enable slow query logs or modify slow query
time) [Customization of this file may not be available for environments
running on Acquia Cloud Next technologies]The Acquia Cloud Platform Enterprise Platform is physically remote from Acquia’s office facilities. A disaster affecting one or more of Acquia’s offices would not impact the availability of Customer website(s) or Customer Data. The Acquia Cloud Platform Enterprise environment consists of major Regions and Availability Zones. Availability Zones are separate yet interconnected data centers within major Regions in Acquia’s global infrastructure. Acquia Cloud Platform Enterprise utilizes a highly available redundant architecture that distributes replicated redundant server types (load balancing, caching, web and database servers) across multiple Availability Zones within the same Region. Acquia will use commercially reasonable efforts to restore the services in an alternate Availability Zone within the same Region (or alternate Region if Multi-Region Failover service has been purchased) in the event service in Customer’s assigned Availability Zone (or Region) is severely impacted.
Acquia will maintain a comprehensive backup solution which includes website code, static assets/files, and databases. Acquia will export MYSQL database one time per day and retain these backups for three days. Customer may also make on-demand backups of any database at any time on the workflow tab of the Acquia Cloud Platform user interface, or using SSH/SCP. During the Subscription Term, Acquia will retain these on-demand backups for Customer until Customer chooses to delete them. Backups will count against the storage space purchased in Customer’s Order. Customer may download these database backups and restore a previous backup on the backups tab of the Acquia Cloud Platform user interface. At the Drupal code layer, Customer-developed code may be managed and deployed by Customer using Acquia’s Git code repository service. This service allows Customer to roll-back and re-deploy the Drupal code, effectively backing up the Drupal layer so that the website code may be re-deployed to a new web server instance as needed. In addition, Acquia conducts daily backups of each website’s files and maintains a complete and current copy of each website, which will be used in the event Acquia must restore the website due to a failure of the Service. Backups are performed daily over the previous week, weekly over the previous month, and monthly thereafter.
The Acquia Cloud Platform Enterprise Platform will make hourly internal disaster recovery snapshots of Customer Data. Acquia will retain these snapshots on a diminishing schedule for three months. These backups will be used to restore Customer website(s) at another location within the same Region in the event of a total data center loss or a loss of multiple disk systems. Acquia will not provide Customer access to these snapshots and will not use these snapshots to restore websites due to data-loss or deletion by Customer.
In the event Acquia becomes aware that Customer’s infrastructure becomes, or may become overloaded due to greater than normal usage, Acquia will notify Customer and will take reasonable actions to increase the available infrastructure capacity in an effort to maintain website performance. If a Customer does not respond to the standard 3 alert notifications, including AM notifications, Acquia will remove the Customer from monitoring and notify the Customer about the removal. Customer agrees that Acquia, in its reasonable discretion, can unilaterally add capacity up to three-times the procured capacity. Fees for overages will be calculated and invoiced monthly in arrears at the then-current rate card. Such additional capacity will remain provisioned for a minimum of five calendar days. In the event Acquia determines that such additional capacity is necessary to maintain website performance for the remainder of the Term, Acquia will contact Customer to obtain approval to increase their cloud capacity or entitlements. If, despite reasonable notification from Acquia that failure to increase the cloud capacity available to one or more applications will adversely impact availability and Customer still fails to purchase a higher tier of service, Acquia may downsize or otherwise limit the cloud capacity available on all customer applications to the original contracted amount. Acquia reserves the right to not provision additional cloud capacity if Customer has any outstanding amounts due or if it determines that additional capacity is unlikely to significantly improve performance, including, without limitation, when the overload is caused by an error in Customer’s software (for example, PHP code), Customer Drupal Instance or during a denial-of-service attack. Acquia reserves the right to bill Customer for traffic and additional cloud capacity associated with a denial-of-service attack.
In the event Acquia becomes aware that Customer’s Cloud Classic infrastructure has reached, or may reach, their allocated storage capacity, Acquia will notify Customer and will take reasonable actions to increase the storage capacity in an effort to maintain website availability. If a Customer does not respond to the standard 3 alert notifications, including AM notifications, Acquia will remove the Customer from monitoring and notify the Customer about the removal. Customer agrees that Acquia, in its reasonable discretion, can unilaterally increase storage to the next standard storage size available. Fees for overages will be calculated and invoiced monthly in arrears at the then-current rate card. Such additional storage capacity will remain provisioned for the remainder of the Term. Customer agrees to pay for such additional storage capacity for the remainder of the Term. Acquia reserves the right to not provision additional storage capacity if Customer has any outstanding amounts due. Acquia reserves the right to remove Customer from monitoring in the event that a recommended or completed storage capacity increase is refused or otherwise disputed by Customer. Downtime incurred while Customer infrastructure is out of monitoring will be excluded from service level policy calculations.
Customer may request Acquia to increase their cloud capacity upon prior written request. Acquia will also make reasonable efforts to contact Customer when it is determined that additional cloud capacity is needed. If a Customer does not respond to the standard 3 alert notifications, including AM notifications, Acquia will remove the Customer from monitoring and notify the Customer about the removal. Fees for overages will be calculated and invoiced monthly in arrears at the then-current rate card for any additional capacity provisioned, for a minimum of five calendar days. If Customer requests additional capacity to the Platform for two (2) consecutive months, such capacity will remain at such level for the remainder of the Subscription Term.
If Customer regularly consumes (for example, more than two times in any week) more than 20% of the shared infrastructure capacity (CPU, memory, disk, PHP processes) assigned to Customer based on the information provided to Acquia on the Platform Questionnaire, or if Customer directly impacts the performance or availability of other customers on shared or infrastructure, Customer understands that Acquia may provision additional capacity for Customer and/or move Customer to dedicated infrastructure at Customer’s expense. Acquia reserves the right to change the underlying infrastructure at any time as long as benchmark performance isn’t degraded.
4.5.1. Resource Limits
Acquia reserves the right to enforce resource limits on Customer applications running on Acquia Cloud Next technologies. Limits may be applied to any resource exceeding Customer’s explicitly defined entitlements, including maximum memory (including any configurable memory allocations), CPU, data transfer/bandwidth, and/or IOPS. Maximum limits may also be set on Customer’s background application processes, which may include frequency of scheduled processes and resources per scheduled process, all as set forth in the product Documentation (each a “Resource Limit” or “Fair Use Limit”).
Fair Use limits are defined as follows:
| Cloud Capacity Units (CCU) | Bandwidth | New Relic Traces |
|---|---|---|
| Up to 14 | 2 TB | 250,000 |
| 14 to 20 | 2 TB | 500,000 |
| 20 to 23 | 2 TB | 1,000,000 |
| 23 to 25 | 2.5 TB | 1,250,000 |
| 25 to 27 | 3 TB | 1,500,000 |
| 27 to 29 | 3.5 TB | 1,750,000 |
| 29 to 32 | 4.25 TB | 2,125,000 |
| 32 to 35 | 5 TB | 2,500,000 |
| 35 to 40 | 6.25 TB | 3,125,000 |
| 40 to 45 | 7.5 TB | 3,750,000 |
| 45 to 50 | 8.75 TB | 4,375,000 |
| 50 to 55 | 10 TB | 5,000,000 |
| 55 to 65 | 12.5 TB | 6,250,000 |
| 65 to 75 | 15 TB | 7,500,000 |
| 75 to 85 | 17.5 TB | 8,750,000 |
| 80 to 95 | 20 TB | 10,000,000 |
| 95+ | Increase by 2.5 TB per 10 CCUs | Increase by 1,250,000 per 10 CCUs |
In this model, Cloud Capacity Units are calculated by Acquia based on CPU utilization, memory utilization, and data transfer within and between Cloud Platform infrastructure layers. To calculate your CCU entitlement, use the following formula:
Fair Use Limits can be increased by purchasing Performance Boosts.
Fair Use Limits apply to all subscriptions, applications, and environments running on Acquia Cloud Next technologies. Stated limits may be higher for Customers with increased entitlements otherwise formalized in Customer’s contract or Acquia’s Support Users Guide.
For Fair Use Limits not readily visible to Customer in the Acquia Cloud Platform product interface, Customer will not be held responsible for Fair Use violations occurring before formal notification is sent to Customer by Acquia. Notifications will be sent when Acquia, during routine audits of Acquia Cloud Next platform utilization, becomes aware of excessive usage beyond Fair Use Limits. Upon receipt of notice, Customer will be provided with a 60 day window to reduce usage or else purchase a Performance Boost to increase Fair Use Limits.
Acquia Cloud Platform CD environments (CDEs) are on-demand development environments available as part of Acquia Cloud Platform CD subscriptions and can be added to Acquia Cloud Platform Enterprise subscriptions. CDEs enable a Customer to dynamically create new environments and deploy code, data and files to those environments in a self-service model. A Customer will be provided the ability to create CDEs up to the number specified within the Customer’s Order. Acquia Cloud Platform CD has two components:
Note
CD environments in Acquia Cloud are not meant to be used with production data or to store production data, especially if your application must adhere to compliance standards such as PCI, HIPAA, or FedRAMP.
Some Acquia Cloud Platform subscriptions include a traffic capacity entitlement to support traffic up to the number of monthly views and unique visits (each as defined below) specified in the applicable Order Form (per SKU) (collectively and individually “Traffic Limits”). For all such subscriptions, application traffic, both actual and capacity limits, shall be viewable in the Acquia Cloud Platform Management Console. When Cloud Platform CDN is enabled, the number of monthly views and unique visits will be reported both from the CDN and from Acquia’s region-specific edge-layer infrastructure, with any duplicative activity automatically filtered out.
Acquia may make available, for Customer provisioning, a one site license for Acquia Site Studio with each Acquia Cloud Platform subscription.
Acquia may make available, for Customer provisioning, a single IDE entitlement with each Acquia Cloud Platform subscription.
New Relic Application Performance Monitoring (“New Relic APM”) licenses are included with Cloud Platform Professional, Cloud Platform Enterprise, and Acquia Site Factory subscriptions. New Relic APM provides Customer with access to New Relic APM Pro. New Relic APM Pro includes Lite access to Synthetics, Insights, New Relic One, and New Relic Browser. Access to such services is subject to change.
Use Restrictions: Use of New Relic APM is restricted to applications hosted on the Acquia Cloud platform and cannot be utilized by non-Acquia services.
Use Limitations: Use of New Relic APM is subject to Fair Use guidelines. Excessive use may result in suspended access to New Relic APM or a requirement that Customer purchase a dedicated account directly from New Relic.
53 State Street, 10th Floor
Boston, MA 02109
United States
Phone: 888-922-7842