private_subnets_ids
Description
The private_subnets_ids parameter specifies the IDs of private subnets to use for creating the Rack. This is an advanced configuration parameter intended for edge use cases where the cluster needs to be installed into existing subnets.
Default Value
The default value for private_subnets_ids is an empty string. When set to an empty string, Convox will automatically create private subnets within the VPC.
Use Cases
- Existing VPC Integration: Use this parameter to integrate your Convox rack with existing private subnets in a VPC.
- Custom Network Configuration: Specify custom subnet IDs to meet specific network requirements and configurations.
Setting Parameters
The private_subnets_ids parameter must be configured at rack installation. Example:
| Key | Value |
|---|---|
private_subnets_ids |
subnet-12345678,subnet-87654321,subnet-11223344 |
Additional Information
When configuring private_subnets_ids, ensure that you also set the vpc_id parameter and properly configure the VPC with a NAT gateway and route table. Additionally, configure the public_subnets_ids parameter, as the load balancer will use public subnets. With high_availability set to true (the default), pass exactly three subnets; any other count fails the install.
With eks_control_plane_private_subnets set to true, the EKS control-plane network interfaces go in these subnets. That needs 2 or more of them, with at least one in every availability zone of public_subnets_ids and none in another zone.
Using this parameter lets you place rack workloads into private subnets you already manage rather than having Convox create new ones. This advanced configuration is suitable when your internal services must run inside an existing private network layout.
