Self-hosted (AWS)

Self-hosted overview

What Diakrin installs in your AWS account, how it fits together and which guide to follow.

Deployment
Self-hosted
Area
Install

Self-hosted runs the whole Diakrin platform inside your own AWS account, installed by one person with the Diakrin CLI in about an hour. It is for companies that need the console and API inside their network too. If you only need apps and data in your cloud, including on Google Cloud, use BYOC.

What you install

diakrin self-hosted infra up creates the infrastructure below, and diakrin self-hosted deploy puts Diakrin on it. Everything is tagged with your installation id, and destroy removes it again.

PartWhat it is for
VPCA private network with two Availability Zones, a NAT gateway and VPC endpoints for AWS services
Internal ALBThe load balancer for the console, API and webhooks. It has no public address
ECS FargateRuns the api, worker and console services and one-off tasks such as migrations
RDS PostgreSQLThe Diakrin database, encrypted, with deletion protection and a final snapshot on destroy
ECRYour own image registry. deploy copies the signed images in by digest
KMS and Secrets ManagerEncryption keys and generated secrets. Nothing secret is written to a file
ACM certificatesHTTPS for the load balancer and for CloudFront
Audit bucketS3 with Object Lock. Retention is your choice and cannot be shortened later
CloudFront and WAFThe public front door by default: a VPC origin to the internal ALB, protected by AWS WAF

How it fits together

text
people and GitHub
      │  https://<host>
      ▼
CloudFront + AWS WAF        (DIAKRIN_EXPOSE=cloudfront, the default)
      │  VPC origin
      ▼
internal ALB ──► ECS Fargate: console · api · worker
                      │
                      ├──► RDS PostgreSQL
                      ├──► Secrets Manager · KMS
                      └──► audit bucket (Object Lock)
  • Every release is signed by Diakrin. The CLI refuses anything it cannot verify.
  • Diakrin cannot sign in to your installation. Outbound traffic goes only to GitHub, the signed image registry and Diakrin license checks.
  • With DIAKRIN_EXPOSE=none there is no CloudFront. People reach the console over VPN, peering or PrivateLink. See Existing infrastructure and exposure.

Choose your path

Next

Check the prerequisites, then follow the install steps.

Next stepSelf-hosted prerequisites →