Service Offerings
Cloud Platform Enterprise Product Guide
Last updated: January 22, 2026
Acquia will provide the PaaS services described below only if purchased by Customer, as indicated in the Order.
Cloud Platform Enterprise is a managed Platform as a Service for Customer’s Drupal website(s). Cloud Platform Enterprise includes all the features of Cloud Platform, is subject to the Service Level Policy, and includes the additional features set forth below.
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 an 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.
Cloud Platform provides application platform services for Node.js applications. Deploying Node.js applications on Cloud Platform requires that the Customer purchase a Node.js platform package along with their 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 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 Cloud Platform customers who have elected to utilize the Platform CDN, the following Resource Limits 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 | 8 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. |
Acquia provides the Acquia AI Provider service as an integrated gateway in Acquia Cloud Platform Enterprise to facilitate secure communication between Customer’s Drupal applications and supported Large Language Models (LLMs).
Acquia AI Provider provides a unified foundation and secure credentials management for the Acquia AI Provider module. While Cloud Platform enables access to these models, Customer is responsible for the configuration and implementation of specific AI-powered features in their Drupal application code.
Customer may utilize the service for automated content operations and application development, including but not limited to:
Automated content metadata: Generation of relevant tags, SEO keywords, and meta descriptions.
Accessibility enhancements: Automated creation of descriptive alt-text for image assets.
Application logic: Site automation, content personalization engines, and customized user journeys.
Direct Provisioning: Acquia acts as the single point of contact for the procurement of AI capabilities through Cloud Platform, removing the need for Customer to establish separate third-party vendor relationships for supported LLMs.
Technical Support: Acquia provides full support for the Acquia AI Provider module and the underlying infrastructure. Support for community-contributed AI modules in the Drupal AI ecosystem is limited to the platform’s connectivity and does not include troubleshooting of the module code.
Compliance: Acquia AI Provider is maintained as a FedRAMP compliant solution.
Model Selection: Acquia provides access to a curated selection of LLMs, for example, Amazon Nova Pro v1. Customers must select a model from the list of available models while enabling the Acquia AI Provider module through the Cloud Platform user interface.
Data Security: Credentials for AI services are injected directly into the Customer's environment through the Cloud Platform interface to ensure secure, streamlined access without requiring manual API key management by the Customer.
Acquia AI Provider usage is governed by annual "AI Credit" allocations. One (1) AI Credit represents a unit of prepaid value redeemed for accessing supported LLM services through Cloud Platform.
Credit Value: The specific number of credits consumed per request is determined by the selected model and the volume of data processed, measured in "tokens". Customers cannot use this feature beyond the credit limit, which is enforced at the subscription level.
Token: The smallest unit of data processed by the specific model powering the service.
Model Variances: Consumption rates vary by model. For example, 100 credits provide a higher volume of tokens for Amazon Nova Pro compared to Claude Sonnet 4. 100 AI Credits give approximately 78M Nova Pro tokens or 24M Nova Premier tokens or 20M Claude Sonnet 4 tokens.
Usage Enforcement: Consumption is subject to rate limitations (tokens and requests per minute) as defined at the time of subscription. Unused annual credits do not roll over to subsequent contract years.
Acquia's AI Gateway is deployed in the following zones:
US
EU
APAC
Requests are processed by the regional AI Gateway unless the model is unavailable locally; in such cases, traffic fails over to the US zone. AI credits per 1M token varies per model across regions. For example, the following table illustrates the AI credits consumed per 1M tokens for the Amazon Nova pro v1 LLM:
us-east-1 | us-west-2 | eu-west-1 | eu-central-1 | ap-southeast-1 | ap-southeast-2 | ap-northeast-1 | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Input | Output | Input | Output | Input | Output | Input | Output | Input | Output | Input | Output | Input | Output |
0.80 | 3.20 | 0.80 | 3.20 | 0.92 | 3.68 | 1.05 | 4.20 | 1.08 | |||||
Acquia Cloud Platform supports phishing-resistant multi-factor authentication (MFA) for Acquia ID logins. This feature supports FIDO2 (WebAuthn) authenticators, such as security keys (like YubiKey) and biometric methods (like fingerprint or facial recognition).
Product privacy notice for Acquia ID.
Cloud Platform Enterprise includes the following web server administration tasks:
Service Offeringsapache.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 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 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 Cloud Next technologies]The 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 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. 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 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 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 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 is on shared development or staging infrastructure, Customer acknowledges that such environments are only for low impact testing and development activities.
If Customer is on shared production infrastructure, Customer acknowledges that no atypically high load will knowingly be triggered on any production environments without written notification to Acquia in a Customer support ticket at least five (5) business days prior to any such event.
Should Customer’s use of shared infrastructure impact the performance or availability of said infrastructure, Customer may be required to move to dedicated infrastructure and would then need to pay the associated infrastructure fees. Furthermore, Customer will not perform any load tests or vulnerability tests on live website(s) unless Customer has purchased dedicated servers and will provide Acquia at least five (5) business days advance notice of any such testing.
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 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”).
Resource Limits are defined as follows:
| Cloud Capacity Units (CCU) | Bandwidth |
|---|---|
| Up to 14 | 2 TB |
| 14 to 20 | 2 TB |
| 20 to 23 | 2 TB |
| 23 to 25 | 2.5 TB |
| 25 to 27 | 3 TB |
| 27 to 29 | 3.5 TB |
| 29 to 32 | 4.25 TB |
| 32 to 35 | 5 TB |
| 35 to 40 | 6.25 TB |
| 40 to 45 | 7.5 TB |
| 45 to 50 | 8.75 TB |
| 50 to 55 | 10 TB |
| 55 to 65 | 12.5 TB |
| 65 to 75 |
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:
Resource Limits can be increased by purchasing Performance Boosts.
Resource Limits apply to all subscriptions, applications, and environments running on 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 Resource Limits not readily visible to Customer in the Cloud Platform user interface, Customer will not be held responsible for Resource Limits violations occurring before formal notification is sent to Customer by Acquia. Notifications will be sent when Acquia, during routine audits of Cloud Next platform utilization, becomes aware of excessive usage beyond Resource 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 Resource Limits.
Cloud Platform CD environments (CDEs) are on-demand development environments available as part of Cloud Platform CD subscriptions and can be added to 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. Cloud Platform CD has two components:
Some 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 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 Cloud Platform subscription.
Acquia may make available, for Customer provisioning, a single IDE entitlement with each Cloud Platform subscription.
New Relic Application Performance Monitoring (“New Relic APM”) licenses are included with Cloud Platform Professional, Cloud Platform Enterprise, and 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, and Browser. Access to such services is subject to change.
Use Restrictions: Use of New Relic APM is restricted to applications hosted on the Cloud Platform and cannot be utilized by non-Acquia services.
: Use of New Relic is subject to the following resource limits:
| Date | Update |
|---|---|
| February 25, 2026 | Added details about the AI Provider module |
| November 6, 2025 | Added details of support for secure login and link to Acquia ID product privacy notice. |
| May 20, 2025 | Added quicklinks. |
| May 7, 2025 | Added document changelog. |
| 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. |
4.32 |
0.84 |
3.36 |
0.96 |
3.84 |
| 15 TB |
| 75 to 85 | 17.5 TB |
| 80 to 95 | 20 TB |
| 95+ | Increase by 2.5 TB per 10 CCUs |
Cloud Platform Enterprise and customers are limited to 250 GB of data ingest per month per subscription, and five million APM Events per month per subscription. All customers are limited to 1 Full User per subscription. The New Relic Synthetics usage is limited to 9000 checks per month per subscription. For additional documentation on limits, see Site Factory and Cloud Platform Professional product guides.
Should Customer’s usage exceed the resource limits for their subscription by 20% for a given month, they will be charged an overage fee determined by the applicable fee schedule set forth in Acquia’s then current commercial price book. Should Customer’s usage exceed a limit by less than 20% for a single month and subsequently usage is reduced below limit, Customer will not be charged for those overages. Should the Customer exceed subscription limits by any amount for two consecutive months, then overages will be applicable at the stated rate. Customer will also have to pay the backdated amount.
Upon request made by Customer within 7 days of termination or expiration of the Subscription Services, Acquia will make Customer Data and Customer Applications available to Customer for export or download. At the end of such 7-day period, Acquia will delete or otherwise render inaccessible any Customer Data and Customer Applications, unless legally prohibited. Acquia has no obligation to retain the Customer Data for Customer purposes after this 7-day post termination period.
Acquia Inc. reserves the right to change the Products and Services Guide based on prevailing market practices and the evolution of our products. Changes will not result in a degradation in the level of services provided during the period for which fees for such services have been paid.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
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 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 Cloud Platform customers who have elected to utilize the Platform CDN, the following Resource Limits 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 | 8 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 provides the Acquia AI Provider service as an integrated gateway in Acquia Cloud Platform Enterprise to facilitate secure communication between Customer’s Drupal applications and supported Large Language Models (LLMs).
Acquia AI Provider provides a unified foundation and secure credentials management for the Acquia AI Provider module. While Cloud Platform enables access to these models, Customer is responsible for the configuration and implementation of specific AI-powered features in their Drupal application code.
Customer may utilize the service for automated content operations and application development, including but not limited to:
Automated content metadata: Generation of relevant tags, SEO keywords, and meta descriptions.
Accessibility enhancements: Automated creation of descriptive alt-text for image assets.
Application logic: Site automation, content personalization engines, and customized user journeys.
Direct Provisioning: Acquia acts as the single point of contact for the procurement of AI capabilities through Cloud Platform, removing the need for Customer to establish separate third-party vendor relationships for supported LLMs.
Technical Support: Acquia provides full support for the Acquia AI Provider module and the underlying infrastructure. Support for community-contributed AI modules in the Drupal AI ecosystem is limited to the platform’s connectivity and does not include troubleshooting of the module code.
Compliance: Acquia AI Provider is maintained as a FedRAMP compliant solution.
Model Selection: Acquia provides access to a curated selection of LLMs, for example, Amazon Nova Pro v1. Customers must select a model from the list of available models while enabling the Acquia AI Provider module through the Cloud Platform user interface.
Data Security: Credentials for AI services are injected directly into the Customer's environment through the Cloud Platform interface to ensure secure, streamlined access without requiring manual API key management by the Customer.
Acquia AI Provider usage is governed by annual "AI Credit" allocations. One (1) AI Credit represents a unit of prepaid value redeemed for accessing supported LLM services through Cloud Platform.
Credit Value: The specific number of credits consumed per request is determined by the selected model and the volume of data processed, measured in "tokens". Customers cannot use this feature beyond the credit limit, which is enforced at the subscription level.
Token: The smallest unit of data processed by the specific model powering the service.
Model Variances: Consumption rates vary by model. For example, 100 credits provide a higher volume of tokens for Amazon Nova Pro compared to Claude Sonnet 4. 100 AI Credits give approximately 78M Nova Pro tokens or 24M Nova Premier tokens or 20M Claude Sonnet 4 tokens.
Usage Enforcement: Consumption is subject to rate limitations (tokens and requests per minute) as defined at the time of subscription. Unused annual credits do not roll over to subsequent contract years.
Acquia's AI Gateway is deployed in the following zones:
US
EU
APAC
Requests are processed by the regional AI Gateway unless the model is unavailable locally; in such cases, traffic fails over to the US zone. AI credits per 1M token varies per model across regions. For example, the following table illustrates the AI credits consumed per 1M tokens for the Amazon Nova pro v1 LLM:
us-east-1 | us-west-2 | eu-west-1 | eu-central-1 | ap-southeast-1 | ap-southeast-2 | ap-northeast-1 | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Input | Output | Input | Output | Input | Output | Input | Output | Input | Output | Input | Output | Input | Output |
0.80 | 3.20 | 0.80 | 3.20 | 0.92 | 3.68 | 1.05 | 4.20 | 1.08 | 4.32 | 0.84 | 3.36 | 0.96 | 3.84 |
Acquia Cloud Platform supports phishing-resistant multi-factor authentication (MFA) for Acquia ID logins. This feature supports FIDO2 (WebAuthn) authenticators, such as security keys (like YubiKey) and biometric methods (like fingerprint or facial recognition).
Product privacy notice for Acquia ID.
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 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 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 Cloud Next technologies]The 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 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. 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 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 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 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 is on shared development or staging infrastructure, Customer acknowledges that such environments are only for low impact testing and development activities.
If Customer is on shared production infrastructure, Customer acknowledges that no atypically high load will knowingly be triggered on any production environments without written notification to Acquia in a Customer support ticket at least five (5) business days prior to any such event.
Should Customer’s use of shared infrastructure impact the performance or availability of said infrastructure, Customer may be required to move to dedicated infrastructure and would then need to pay the associated infrastructure fees. Furthermore, Customer will not perform any load tests or vulnerability tests on live website(s) unless Customer has purchased dedicated servers and will provide Acquia at least five (5) business days advance notice of any such testing.
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 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”).
Resource Limits are defined as follows:
| Cloud Capacity Units (CCU) | Bandwidth |
|---|---|
| Up to 14 | 2 TB |
| 14 to 20 | 2 TB |
| 20 to 23 | 2 TB |
| 23 to 25 | 2.5 TB |
| 25 to 27 | 3 TB |
| 27 to 29 | 3.5 TB |
| 29 to 32 | 4.25 TB |
| 32 to 35 | 5 TB |
| 35 to 40 | 6.25 TB |
| 40 to 45 | 7.5 TB |
| 45 to 50 | 8.75 TB |
| 50 to 55 | 10 TB |
| 55 to 65 | 12.5 TB |
| 65 to 75 | 15 TB |
| 75 to 85 | 17.5 TB |
| 80 to 95 | 20 TB |
| 95+ | Increase by 2.5 TB 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:
Resource Limits can be increased by purchasing Performance Boosts.
Resource Limits apply to all subscriptions, applications, and environments running on 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 Resource Limits not readily visible to Customer in the Cloud Platform user interface, Customer will not be held responsible for Resource Limits violations occurring before formal notification is sent to Customer by Acquia. Notifications will be sent when Acquia, during routine audits of Cloud Next platform utilization, becomes aware of excessive usage beyond Resource 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 Resource Limits.
Cloud Platform CD environments (CDEs) are on-demand development environments available as part of Cloud Platform CD subscriptions and can be added to 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. Cloud Platform CD has two components:
Cloud Platform Enterprise and customers are limited to 250 GB of data ingest per month per subscription, and five million APM Events per month per subscription. All customers are limited to 1 Full User per subscription. The New Relic Synthetics usage is limited to 9000 checks per month per subscription. For additional documentation on limits, see Site Factory and Cloud Platform Professional product guides.
Should Customer’s usage exceed the resource limits for their subscription by 20% for a given month, they will be charged an overage fee determined by the applicable fee schedule set forth in Acquia’s then current commercial price book. Should Customer’s usage exceed a limit by less than 20% for a single month and subsequently usage is reduced below limit, Customer will not be charged for those overages. Should the Customer exceed subscription limits by any amount for two consecutive months, then overages will be applicable at the stated rate. Customer will also have to pay the backdated amount.
Upon request made by Customer within 7 days of termination or expiration of the Subscription Services, Acquia will make Customer Data and Customer Applications available to Customer for export or download. At the end of such 7-day period, Acquia will delete or otherwise render inaccessible any Customer Data and Customer Applications, unless legally prohibited. Acquia has no obligation to retain the Customer Data for Customer purposes after this 7-day post termination period.
Acquia Inc. reserves the right to change the Products and Services Guide based on prevailing market practices and the evolution of our products. Changes will not result in a degradation in the level of services provided during the period for which fees for such services have been paid.
If this content did not answer your questions, try searching or contacting our support team for further assistance.