Staging — account 371326279611

Region: ap-southeast-2. Staging is a genuinely separate AWS account from production, but its DNS records and its application backends currently live inside the production account, not this one, an important thing to know before going looking for them in the wrong place.

Traffic flow

%%{init: {'flowchart': {'nodeSpacing': 70, 'rankSpacing': 110, 'padding': 20, 'curve': 'basis'}}}%%
flowchart TB
    Internet((Public Internet))

    subgraph PRODACCT["Hosted in the PRODUCTION account (704081087743)"]
        direction TB
        STGZ["staging.arep.co<br/>Simple ALIAS"]
        STGI["staging.arep.ink<br/>A record"]
        OALB["Load balancer<br/>vpc-3dd4bc58, same VPC as its backends"]
        SBACK["staging/campaign, staging/campaign-2,<br/>staging/audience-manager,<br/>staging/deferred-collector<br/>currently stopped"]
        PORTAL["&lt;promoter&gt;.staging-portal.arep.co<br/>→ gateway1 (52.62.81.96)"]
    end

    subgraph STAGACCT["STAGING account (371326279611)"]
        direction TB
        APP["staging-app.audiencerepublic.com"]
        MGR["staging-manage.arep.co/&lt;id&gt;"]
        SDK["sdk-cdn.arep.co/staging/..."]
        SVC["svc.stag.arep.co"]
        VPN["vpn.stag.arep.co"]
    end

    subgraph NETLIFY["Netlify"]
        NF["staging-arep-app.netlify.com"]
    end

    subgraph CF["CloudFront"]
        CFN["Notification Manager distribution"]
        CFS["Widget SDK distribution"]
    end

    Internet --> STGZ & STGI & APP & MGR & PORTAL & SDK
    STGZ --> OALB
    STGI --> OALB
    OALB --> SBACK
    APP --> NF
    MGR --> CFN
    SDK --> CFS

Hostnames

Hostname	App	DNS lives in	Current target
staging.arep.co	C2	Production account (arep.co zone)	A load balancer in the production account, same VPC as the staging backend servers
staging.arep.ink	C2	Production account (arep.ink zone)	Same load balancer
staging-app.audiencerepublic.com	AM2	Public DNS	Netlify (staging-arep-app.netlify.com)
staging-manage.arep.co/<id>	Notification Manager	Public DNS	CloudFront
<promoter>.staging-portal.arep.co	Privacy Portal	Production account	gateway1 (52.62.81.96)
sdk-cdn.arep.co/staging/...	Widget SDK	Public DNS	CloudFront

Compute

The four staging C2/AM2 backend servers are physically instances in the production account's VPC (vpc-3dd4bc58), reachable over the same internal private.a DNS zone as the production backends:

Instance	Role	State
staging/campaign	C2 application server	stopped
staging/campaign-2	C2 application server	stopped
staging/audience-manager	AM2 API backend	stopped
staging/deferred-collector	Background/collector role	stopped

All four being stopped means requests to staging.arep.co currently receive an error response, not because of a DNS or routing problem, the request reaches the load balancer correctly, there's just nothing running behind it right now.

The stag.arep.co zone (staging account)

This is a separate, unrelated per-environment naming convention hosted directly in the staging AWS account, not customer/product traffic:

Record	Points to
app.stag.arep.co	Netlify
cdn.stag.arep.co	CloudFront
svc.stag.arep.co	A load balancer in this account
vpn.stag.arep.co	A fixed IP, VPN access into this account's VPC

A note for whoever's on call

If staging.arep.co needs a DNS change, it has to be made in the production account's arep.co zone, not in the staging account. Nothing about that record lives in 371326279611.