Provisioning Control Plane Infrastructure on AWS
Requirements | Description | Reason for Requirement |
---|---|---|
Postgres | AWS RDS, Postgres version >= 13, Instance Type: db.t3.medium(aws)/db.t4g.medium(aws), Storage: 20GB with autoscale enabled to 30GB, Storage Type: gp3, Encryption: Enabled. For PostgreSQL 17+: Set force_ssl parameter to 0 (off) in parameter group if you need to allow non-SSL connections (default is 1 ). Security Group: Ensure RDS security group allows inbound traffic from EKS node security groups | The database is used by TrueFoundry control plane to store all its state |
S3 bucket | Any S3 bucket reachable from control-plane | This is used by control-plane to store the intermediate code while building the docker image |
Egress Access for TrueFoundryAuth | Egress access to https://auth.truefoundry.com and analytics.truefoundry.com | This is needed to verify the users logging into the TrueFoundry platform for licensing purposes |
Additional TrueFoundry information | Additional information for control plane deployment which will be provided by TrueFoundry team | This includes tenant name, licence key, and image pull secret |
DNS | Domain for control plane and service endpoints | One endpoint to point to the control plane service (e.g., platform.example.com) The control-plane URL must be reachable from the compute-plane. The developers will need to access the TrueFoundry UI at the provided domain |
User/ServiceAccount to provision the infrastructure | Set of permissions needed to provision the infrastructure for TrueFoundry control-plane. Detailed here | Required to set up and manage the infrastructure components |