Ghostline

A personal connectivity product for browsing and video from Dubai under current internet filtering. Stockholm is the active primary exit. Cape Town is parked as an on-demand backup, retaining its IPs and credentials. Clients manually choose Xray / VLESS / REALITY or AmneziaWG.

The repo has one regional deployment model: one Bottlerocket Graviton EC2 host, one ECS gateway task with three application images, a restricted network daemon and two EIPs. Every meaningful release temporarily provisions a second host, then uses native ECS blue-green hooks to hand off the two EIPs and retire the source. Separate bootstrap and network-daemon images join the common five-image release pipeline. A shared initializer prepares protocol-private RAM configuration; separate engines mount it read-only, share a formula-derived memory budget and restart independently when eligible. ECR retains images, regional Parameter Store retains credentials, and SSM supplies SSH-free administration.

Architecture and ECS runtime define the model. Stockholm and Cape Town record live state and validation. Mac REALITY uses OneXraySE; AWG remains in Amnezia. Anthony confirmed OneXraySE sleep/wake stability and IPv4/DNS privacy in practical use; native Chrome WebRTC checks also pass. Current-network testing is complete; IPv6 blocking remains unproven and will be revisited with future location/protocol testing.

From infra/, with Node 24 selected:

npm ci
npm test
npm run deployments
npm run ecs stockholm-ecs status

Use the same target-scoped commands for each region. stop retains host/disk/IPs; park retains only the endpoint's billable EIPs; destroy also releases them. Park preserves images and release support. Complete destroy removes owned regional release resources/images while retaining credentials, expiring logs, GuardDuty and independent CloudTrail. Adding a catalog entry allocates nothing. Development and commands.

Start at the documentation map. infra/ owns CDK/tooling, runtime/ecs/ owns native fixtures/image recipes, and .context/ owns live working memory. Secrets and client exports stay under ignored .local/ or their authorized stores. Parameter Store preserves current identities; client profiles can be re-exported on demand. Total credential loss is handled by explicit new-identity provisioning and device re-enrolment; no LastPass backup requirement applies.