Skip to content
These docs are a preview of Self-Managed Kindo 2026.11, an upcoming release.

Amazon Web Services

Requirements and sizing and Infrastructure give the versions each service needs. Kindo has run on every service listed here.

Kindo needsAWS serviceNotes
KubernetesAmazon EKS
PostgreSQLAmazon RDS for PostgreSQLSee PostgreSQL setup
RedisElastiCache for Redis OSS, cluster mode disabledOne node group. Replicas with automatic failover are fine. Not ElastiCache Serverless or MemoryDB: both are cluster mode only
RabbitMQAmazon MQ for RabbitMQ, or one Kindo runs in the clusterKindo’s is a single broker with no failover; see RabbitMQ
Object storageAmazon S3Access keys, IAM roles for service accounts, or EKS Pod Identity
Mail relayAmazon SESSee Email setup
Secret store (optional)AWS Secrets ManagerNot Systems Manager Parameter Store. See Secret store
AI modelsAWS BedrockThrough an IAM role, with no API key. See AI models
IngressAWS Load Balancer ControllerSee Load balancer setup and the example
TLS certificatesAWS Certificate ManagerWith Kindo-managed ingress

The database server that hosts Hatchet uses a custom DB parameter group that holds the Hatchet settings.

  • 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.

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.

SettingValue
Service typeNodePort
Target typeinstance