How to Select a RegionWhen creating a Lighthouse instance, you can select a region based on the following considerations. Note that the region cannot be changed after the instance is created successfully.
- Business requirements: To guarantee the quality of public network access and reduce the packet loss and delay, we recommend you select the region closest to your end users.
- Instance package: Available instance packages vary by region. You can select one based on the CPU, memory, system disk, public network bandwidth, and monthly traffic usage of the instance as required by your application. For more information, see Price Overview.
- Cost budget:
- Instance packages in and outside the Chinese mainland differ in configuration and price.
- Instance packages for Linux and Windows outside the Chinese mainland differ in price.
You can select a package based on your budget and requirements. For billing details, see Price Overview.- Cross-border network quality: For Lighthouse instances outside the Chinese mainland, as access from the Chinese mainland may experience a significant delay and packet loss due to the ISP network lines (non-cross-border access typically suffers no impact), Tencent Cloud only guarantees that the public network bandwidth provided in instance packages is the "peak bandwidth".
How to Select an AZWe recommend you select an AZ that is "randomly assigned". You can also specify an AZ as needed. Note that the AZ cannot be changed after the instance is created successfully.
NoteLighthouse instances are available in the following availability zones.
Hong Kong (China): Hong Kong Zone 1, Hong Kong Zone 2, Hong Kong Zone 3.
Both private and public IPs are assigned to Lighthouse instances for private and public network connectivity.
Scenario | Supported by Default | Supported over CCN | |
---|---|---|---|
In the same region Under the same account |
Access between Lighthouse instances | Yes | - |
Connection between Lighthouse instances and LighthouseDB instances | Yes | - | |
Across regions Under the same account |
Access between Lighthouse instances | No | - |
Connection between Lighthouse instances and LighthouseDB instances | No | - | |
Under different accounts | Access between Lighthouse instances | No | - |
Scenario | Supported by Default | Supported over CCN |
---|---|---|
CVM | No | Yes. For more information, see Private Network Interconnection. |
COS (in the same region) |
Yes. For more information, see COS Regions and Access Endpoints.
You can determine whether Lighthouse accesses COS over the private network by referring to FAQs. |
- |
COS (in different regions) | No | - |
TencentDB | No | Yes. For more information, see Private Network Interconnection. |
CFS | No | Yes. For more information, see Private Network Interconnection. |
CLB | No | - |
NoteFor the above use cases where private network connectivity is not supported, you can connect the instances over the public network, and configure firewall policies to ensure the security. Note that you need to pay for the outbound traffic.
NoteWe recommend you select the region closest to your end users to minimize the access delay and improve the network stability.
Was this page helpful?