PADI Axelerant
padi.com Enterprise Architecture
v1.1 · 6 November 2026
Work in progress · Version 1.1, last updated 6 November 2026
Platform

AWS

AWS runs the finder and every deployment pipeline. The website itself runs on Acquia.

Accounts

Account Name Operated by Runs
871993978063 CI/CD and non-production Axelerant Web, edge and finder development and staging pipelines, web production pipelines (moving to the production account), CI artifact registry, finder development and staging
984950935535 Production Axelerant Finder production, production pipelines, monitoring-as-code state
441054594441 PADI Travel PADI Travel PADI Travel database, DMS replication, Kinesis change streams
388221456699 PADI core production PADI Member file export and its event forwarder
920060764880 PADI non-production PADI Non-production member file
Not recorded PADI DNS PADI Route 53 public zone for padi.com
Figure 30. Accounts and cross-account links. Development reads the staging stream; staging reads production data; production has its own stream so a reload never blocks staging.
Figure 30. Accounts and cross-account links. Development reads the staging stream; staging reads production data; production has its own stream so a reload never blocks staging.

Finder production network

Figure 31. Finder production network. If the NAT gateway's zone fails, running hosts keep serving; outbound calls and new hosts wait for the zone to recover.
Figure 31. Finder production network. If the NAT gateway's zone fails, running hosts keep serving; outbound calls and new hosts wait for the zone to recover.

Conventions

Area Convention
Infrastructure as code AWS CDK (TypeScript) in each repository; Terraform for Cloudflare and finder monitoring; Ansible over SSM for finder hosts
Shared pipeline library @padiww/cicd-constructs, published to the CI registry in the non-production account
Hosts IMDSv2 only, private subnets, security groups admit Cloudflare address ranges only