Amazon Web Services
Requirements and sizing and Infrastructure give the versions each service needs. Kindo has run on every service listed here.
| Kindo needs | AWS service | Notes |
|---|---|---|
| Kubernetes | Amazon EKS | |
| PostgreSQL | Amazon RDS for PostgreSQL | See PostgreSQL setup |
| Redis | ElastiCache for Redis OSS, cluster mode disabled | One node group. Replicas with automatic failover are fine. Not ElastiCache Serverless or MemoryDB: both are cluster mode only |
| RabbitMQ | Amazon MQ for RabbitMQ, or one Kindo runs in the cluster | Kindo’s is a single broker with no failover; see RabbitMQ |
| Object storage | Amazon S3 | Access keys, IAM roles for service accounts, or EKS Pod Identity |
| Mail relay | Amazon SES | See Email setup |
| Secret store (optional) | AWS Secrets Manager | Not Systems Manager Parameter Store. See Secret store |
| AI models | AWS Bedrock | Through an IAM role, with no API key. See AI models |
| Ingress | AWS Load Balancer Controller | See Load balancer setup and the example |
| TLS certificates | AWS Certificate Manager | With Kindo-managed ingress |
PostgreSQL setup
Section titled “PostgreSQL setup”The database server that hosts Hatchet uses a custom DB parameter group that holds the Hatchet settings.
Email setup
Section titled “Email setup”- The sender address, or its domain, is a verified identity in SES. Otherwise SES rejects Kindo’s test email and every sign-in code.
- While the account is in the SES sandbox, the recipient is verified too.
Load balancer setup
Section titled “Load balancer setup”With the AWS Load Balancer Controller and a non-VPC network plugin, such as Calico or Cilium, the services behind the controller use these values. An in-cluster ingress controller, such as NGINX or Traefik, is the alternative.
| Setting | Value |
|---|---|
| Service type | NodePort |
| Target type | instance |
