- Release Notes and Announcements
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Logging In to Linux Instances
- Logging in Windows Instance
- Managing Instances
- Working with Cloud Disks
- Managing Keys
- Managing Firewall
- Managing Snapshot
- Managing Image
- Private Network Interconnection
- OPS and Monitoring
- Access Management
- Transfering File
- Uploading Local Files to Lighthouse
- Uploading File from Windows to Linux Lighthouse Instance via WinSCP
- Uploading File from Windows to Lighthouse Instance via FTP
- Uploading File from Windows to Windows Lighthouse Instance via Remote Desktop Connection
- Uploading File from Linux or macOS to Linux Lighthouse Instance via SCP
- Uploading File from Linux or macOS to Lighthouse Instance via FTP
- Uploading File from Linux to Windows Lighthouse Instance via rdesktop
- Uploading File from macOS to Windows Lighthouse Instance via MRD
- Best Practices
- Ops Guide
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- RenewInstances
- DescribeInstanceVncUrl
- DescribeInstancesDeniedActions
- DescribeInstancesDiskNum
- DescribeInstancesReturnable
- DescribeInstancesTrafficPackages
- DescribeModifyInstanceBundles
- DescribeResetInstanceBlueprints
- IsolateInstances
- ModifyInstancesBundle
- RebootInstances
- ResetInstance
- ResetInstancesPassword
- StartInstances
- StopInstances
- ModifyInstancesAttribute
- ModifyInstancesRenewFlag
- CreateInstances
- DescribeInstances
- TerminateInstances
- CBS APIs
- Snapshot APIs
- Key APIs
- CCN APIs
- Image APIs
- Firewall APIs
- Scene APIs
- Package APIs
- Quota APIs
- Region APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- Contact Us
- lighthouse Policy
- Release Notes and Announcements
- User Guide
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Logging In to Linux Instances
- Logging in Windows Instance
- Managing Instances
- Working with Cloud Disks
- Managing Keys
- Managing Firewall
- Managing Snapshot
- Managing Image
- Private Network Interconnection
- OPS and Monitoring
- Access Management
- Transfering File
- Uploading Local Files to Lighthouse
- Uploading File from Windows to Linux Lighthouse Instance via WinSCP
- Uploading File from Windows to Lighthouse Instance via FTP
- Uploading File from Windows to Windows Lighthouse Instance via Remote Desktop Connection
- Uploading File from Linux or macOS to Linux Lighthouse Instance via SCP
- Uploading File from Linux or macOS to Lighthouse Instance via FTP
- Uploading File from Linux to Windows Lighthouse Instance via rdesktop
- Uploading File from macOS to Windows Lighthouse Instance via MRD
- Best Practices
- Ops Guide
- Troubleshooting
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- RenewInstances
- DescribeInstanceVncUrl
- DescribeInstancesDeniedActions
- DescribeInstancesDiskNum
- DescribeInstancesReturnable
- DescribeInstancesTrafficPackages
- DescribeModifyInstanceBundles
- DescribeResetInstanceBlueprints
- IsolateInstances
- ModifyInstancesBundle
- RebootInstances
- ResetInstance
- ResetInstancesPassword
- StartInstances
- StopInstances
- ModifyInstancesAttribute
- ModifyInstancesRenewFlag
- CreateInstances
- DescribeInstances
- TerminateInstances
- CBS APIs
- Snapshot APIs
- Key APIs
- CCN APIs
- Image APIs
- Firewall APIs
- Scene APIs
- Package APIs
- Quota APIs
- Region APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- Contact Us
- lighthouse Policy
Regions
Overview
Tencent Cloud IDCs are distributed across different regions worldwide. To minimize access delay and improve download speed, we recommend you select the region closest to your end users.
Considerations
Each region includes multiple availability zones.
By default, Lighthouse instances in different regions are not interconnected over the private network.
Note:
How to Select a Region
When 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".
AZs
Overview
An Availability Zone (AZ) refers to a physical location with independent power supply and network resources within a region.
AZs in the same region are interconnected through low-latency private network linkages, which allows Lighthouse instances in different AZs in the same region to communicate with each other through private networks. For applications with high disaster recovery requirements, deploy Lighthouse instances to different availability zones within the same region to ensure fault isolation. Note that it may cause a longer communication latency.
Considerations
Lighthouse instances in different AZs in the same region under the same account are interconnected over the private network by default.
Note:
How to Select an AZ
We 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.
Supported Regions and Availability Zones
Note:
Lighthouse instances are available in the following availability zones.
Hong Kong/Macao/Taiwan (China)
Hong Kong (China): Hong Kong Zone 1, Hong Kong Zone 2, Hong Kong Zone 3.
Other countries and regions
Singapore: Singapore Zone 1, Singapore Zone 2, Singapore Zone 3.
Tokyo: Tokyo Zone 1, Tokyo Zone 2.
Seoul: Seoul Zone 1, Seoul Zone 2.
Silicon Valley: Silicon Valley Zone 1, Silicon Valley Zone 2.
Frankfurt: Frankfurt Zone 1, Frankfurt Zone 2.
Toronto: Toronto Zone 1.
Mumbai: Mumbai Zone 1, Mumbai Zone 2.
Connectivity
Both private and public IPs are assigned to Lighthouse instances for private and public network connectivity.
Private network connectivity: Data transfer between Lighthouse instances in the same region is over the local area network (LAN), which is free of charge. See Private network connectivity.
Public network connectivity: Lighthouse instances are assigned with public IPs for internet access (both upstream and downstream). Note that you need to pay for the outbound traffic.
Private network connectivity
The table below describes the private network connectivity between Lighthouse instances:
Scenario | Supported by Default | Supported over CCN | |
In the same regionUnder the same account | Access between Lighthouse instances | Yes | - |
| Connection between Lighthouse instances and LighthouseDB instances | Yes | - |
Across regionsUnder the same account | Access between Lighthouse instances | No | |
| Connection between Lighthouse instances and LighthouseDB instances | No | |
Under different accounts | Access between Lighthouse instances | No | - |
The private network connectivity between Lighthouse instances and other Tencent Cloud services:
Scenario | Supported by Default | Supported over CCN |
CVM | No | |
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 | |
CFS | No | |
CLB | No | - |
Note:
For 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.
Public network connectivity description
Regions in the Chinese mainland: Stable BGP network access is provided to ensure that access to Lighthouse within the Chinese mainland is over a stable low-latency network.
Regions outside the Chinese mainland: The public network bandwidth is mainly provided for users outside the Chinese mainland. 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).
Note:
We recommend you select the region closest to your end users to minimize the access delay and improve the network stability.
Yes
No
Was this page helpful?