Work in progress · Version 1.1, last updated 6 November 2026
Platform
Acquia Cloud
Two Acquia applications host the new site, one for Next.js and one for Drupal. AWS pipelines build and deploy both.
Applications and environments
Application
Product
Repository
Environments
Hostnames
padifrontend
Front End Hosting Advanced (Cloud Next), Node.js
padi.com
dev, stage, prod
web-* and account-* via padifrontend{env}.prod.acquia-sites.com
padicom
Cloud Platform, Drupal
drupal.padi.com
dev, stage, prod
cms-* via padicom{env}.prod.acquia-sites.com
Acquia Pipelines and Code Studio are not used. Deployments push a prebuilt artifact to the Acquia Git repository, tag it, and switch the environment to that tag through the Acquia API (see Deployment pipelines).
Setting
Development
Staging
Production
Drupal memcache
256 MB
1,024 MB
2,048 MB
Drupal OPcache
256 MB
256 MB
384 MB
Shield (CMS basic auth)
On for editorial paths; content API, files and webhooks exempt
Same
Same
Frontend basic auth
On
On
On until cutover
Drupal configuration split
dev
uat
prod
Frontend configuration
Acquia environment variables at run time; AWS Secrets Manager at build time
Same
Same (27 Acquia variables in production)
Scheduled jobs (CMS)
Drupal cron hourly; edge purge queue every minute
Drupal cron hourly; scheduler, purge queue and delayed purges every minute
Same as staging
Region
AWS us-west-2 (Oregon)
Same
Same
Infrastructure
Figure 29. Acquia hosting of the new site.
There is no Datadog Agent or log forwarding on Acquia. The frontend sends traces and runtime metrics directly; the CMS sends traces directly. Application logs are available only in Acquia's own log views.
Platform limits and how the design handles them
Limit
Effect
Handling
Varnish cannot be purged for Node applications
Stale HTML could persist
Pages leave the frontend marked private; HTML is cached at Cloudflare instead
Responses with more than about 22 KiB of headers return 502
Large preload and cache-tag headers break pages
A header guard trims preload links; cache tags are capped at 8 KB
Redirects and 404s are cached publicly for 15 minutes
New pages or fixed redirects can lag
404 cache tags are purged on publish
A code switch takes 5 to 10 minutes
A frontend deploy takes about 12 minutes
Prebuilt artifact; only the default locale is prerendered
No log forwarding
No application logs in Datadog
Errors captured as trace spans
Production replaces application 500 errors on API and asset paths with an Acquia 503 page
Error details are lost to the client
Cause is found in traces
Autoscaling reacts 1 to 2 minutes after saturation
A sudden surge can briefly exceed capacity
Long edge TTL absorbs most traffic; a saturated server answers a fast 503 with a retry hint
Shared egress address for padicom
Cannot allow-list Drupal precisely
Cloudflare admits Acquia's egress range to the search index host, which also requires a client certificate and a content-only role
