Engine Network Introduction

Recent Pages

Engine Network Introduction

Last updated: 2024-09-04 11:12:37

The Engine Network is built on a VPC, assigning IP addresses within the engine network's address range to the computing engines and gateway. The Pods of the computing engines and gateway will directly occupy VPC subnet IP addresses, so it is recommended to choose a subnet with sufficient IP addresses that do not conflict with other products. Users can purchase multiple computing engines within the same engine network and manage them centrally through the gateway.
﻿
﻿
﻿
Usage Limitations
1. The subnet settings should be consistent with the VPC subnet settings, and you should create them yourself. Once created, they cannot be modified.
2. You can use any of the following private subnets:
10.0.0.0 - 10.255.255.255 (Subnet mask range should be between 12 - 28)
172.16.0.0 - 172.31.255.255 (Subnet mask range should be between 12 - 28)
192.168.0.0 - 192.168.255.255 (Subnet mask range should be between 16 - 28)
3. Ensure that you allocate a subnet with sufficient IP addresses for the Engine Network to avoid the inability to create Pods due to IP resource exhaustion when deploying large workloads. If you are unsure about the required scale, it is recommended to use the default configuration.
4. When using federated queries, you should ensure that the engine subnet does not overlap with the data source subnet.
5. Engine network configuration: During the initial setup and purchase, custom network configurations are allowed. If you need to make changes later, please Submit Ticket to apply for modifications.
﻿