For the complete documentation index, see llms.txt. This page is also available as Markdown.
Bind an Elastic IPv4 Address
You can bind up to 4 elastic IPv4 addresses to a private IPv4.
Procedures
Click the instance name to go to instance Details > Information > Network interface.
Select the private IPv4 you want to bind elastic IPv4 and go to Actions > Bind Elastic IPv4.
Select a desired elastic IPv4 and click Confirm to bind. If no desired elastic IPv4, click New Elastic IPv4 to create a new IPv4.
See Create an Elastic IPv4 for detailed steps.
Note
You can also go toElastic IPv4>Actions>Bind Private IPv4to bind the elastic IPv4.
Bypass Mode Configuration Guide
1. Scope and Prerequisites
1.1 Applicable Scenarios
Single network interface (NIC) only
Supports multiple IPs (up to 254)
All IPs must be in Bypass mode
1.2 Supported Operating Systems
Ubuntu: 20.04 / 22.04 / 24.04
Debian: 10 / 11 / 12
CentOS: 7 / 9
Rocky Linux: 8.10 / 9.6
1.3 Important Notes
A reboot is required after running the script, otherwise the configuration will not take effect
Mixed modes are not supported (Bypass Mode + NAT Mode)
Security groups are not supported in Bypass mode. Traffic on a Bypass elastic IP is not filtered by the platform in either direction, whatever security group the instance uses. Configure a firewall inside the guest operating system before exposing services on a Bypass elastic IP. See Elastic IP: Standard vs Bypass
2. Operation Steps
Create Command:
Path:
Console → Orchestration Service → Commands → Create Commands
copy and add the following script and create command.
Run Command:
Path:
Console → Elastic Compute → Elastic Compute Instance List → Actions → Operations → Run command → Select the command→ Confirm
Run the created command.
Reboot the Instance
After execution, you must manually reboot the instance.
Add Additional IPs (Optional)
To attach more IPs, repeat:
Bind IP
Run command
Reboot instance
Create Compute Instance
Create an instance following the standard process.