Self-hosted (AWS)

Self-hosted prerequisites

What you need before the first command: AWS access, a domain, DNS and a GitHub organization admin.

Deployment
Self-hosted
Area
Install

You need one AWS administrator, one domain name and a GitHub organization admin before you run the first command.

Before you start

You needExampleNotes
An AWS account and regioneu-west-1A region listed as supported by the release
The AWS CLI v2, signed in with admin rightsaws sts get-caller-identity worksOne administrator installs Diakrin end to end
A host namediakrin.example.comA name you control. Diakrin is served at https://<host>
DNS for that nameRoute 53 in this account, or any DNS providerRoute 53: records are automatic. Any other provider: the CLI prints two records early
A GitHub organization adminyour-orgInstalls the Diakrin GitHub App and sets its webhook
A Mac or Linux computerTerminal with curl and shInstalls the Diakrin CLI
Audit retention365 daysCannot be shortened after the first install
A Diakrin license file (optional)acme-license.jsonNot needed to install. See License

AWS requirements

  • At least 2 vCPU of Fargate On-Demand quota and 2 Availability Zones in the region.
  • With the default exposure (cloudfront) the VPC needs an internet gateway. A new VPC created by Diakrin has one.
  • The AWS role you sign in with can create VPC, ECS, RDS, ALB, ECR, KMS, ACM, S3, IAM, CloudFront and WAF resources. AdministratorAccess is the simplest choice for the install.

Check your setup

sh
aws sts get-caller-identity

You should see the 12-digit account id of the account you want to install into. If it shows another account, switch profile before you continue.

sh
aws --version

You should see aws-cli/2.

Next

Install Diakrin.

Next stepInstall self-hosted Diakrin →