| Function | Description | Release date | Region | References |
|---|---|---|---|---|
| Bandwidths |
| 07/06/2024 | HCM-03 | Bandwidth |
| Search Servers |
| 05/2024 | HCM-03 | Server |
| Volume |
| 05/2024 | HCM-03 | Volume |
| vLB |
| 05/2024 | HCM-03 | LoadBalancer |
| Tags in Network Interface |
| 05/2024 | HCM-03 | External Interface |
| Network Interface |
| 02/05/2024 | HCM-03 | External Interface |
| Image |
| 02/05/2024 | HCM-03 | Image |
| SSO - IAM |
| 10/04/2024 | HCM-03 | IAM |
| Snapshot |
| 03/04/2024 | HCM-03 | Snapshot |
| Share Snapshot |
| 03/04/2024 | HCM-03 | |
| vDB Memory | With new UI Portal synchronized with existing services on GreenNode, we hope to bring a more user-friendly experience when using services on GreenNode. At the same time, vDB Memory's new portal is integrated with the IAM (Identity and Access Management) feature, making it more convenient for customers to manage and assign access rights. Get started: https://vdb.console.greennode.ai/memorystore/database | 9/7/2024 | HCM-03 |
| Benefits of use | Description of benefits |
Providing Region HAN-01 option when initializing the service Increase access performance for Customers who settle at the Hanoi | Key highlights:
|
Multi Region solution (coming soon): Support DR solutions for businesses This solution will be suitable for customers who need:
| Key highlights:
Cross-region backup: primary data and backups are stored in geographically separate areas, increasing resilience in the event of an incident (including natural disasters or software or software failures). hard). Cross-region load balancer: customers can set up regional load balancing, with high availability and low latency for their end applications. Accordingly, cross-region load balancer provides:
Set up Interconnect up to 10Gbps private line (CrossRegionConnect): helps connect two regions HCM-03 and HAN-01 via Private line, helping to enhance access performance and connection security |
| Content | Basic package | Pro package |
|---|---|---|
| Cost | Free | From 500,000vnđ |
| Quota | Retention: 1 day Metric: 5 resource Log: 10GB/day |
|
| SMS/Email Noti | The system offers a FOC (free of charge) option of 20 emails/SMM per month. Customers can proactively choose a free package or purchase email/SMS package depending on your needs. | The system offers a FOC (free of charge) option of 20 emails/SMM per month. Customers can proactively choose a free package or purchase email/SMS package depending on your needs. |
The top-up amount includes 10% VAT;
Credits received = top-up amount
The top-up amount still includes 10% VAT
Credits received = top-up amount ÷ 110%
WAF Standard plan equals 1 domain / 30 days (includes 300 GB WAF traffic and 3 million WAF requests for the first domain / account). From the 2nd domain under the same account, the system charges based on actual usage.
Where:
· WAF requests: shared across all customer WAF domains and do not expire. If you have no active WAF domains for 30 days, WAF requests will be deleted.
· WAF traffic: does not expire. If you have no active WAF domains for 30 days, WAF traffic will be deleted.
Includes:
· Domestic traffic = 10× domestic storage capacity.
· 1,000 GB international traffic/month.
· Unlimited requests.
Committed performance per project:
· Read: 2,500 req/s
· Write: 1,500 req/s
· Delete: 1,000 req/s
· Total requests: 4,000 req/s
Domestic traffic equal to twice the domestic storage capacity, 1 TB of international traffic per month, and unlimited requests.
Committed performance:
| Function | Description | Release date | Region | References |
|---|---|---|---|---|
| Auto Scaling Load Balancer | The Auto Scaling feature of vLB helps users by:
| 13/08/2024 | HCM03 | Auto Scaling Load Balancer |
| POC wallet for Terraform | Currently, with the increasing demand from customers for using Terraform services, GreenNode has added support for providing POC (Proof of Concept) for the Terraform service. This allows customers to easily trial the service on GreenNode before deciding to fully use it. As of now, the POC wallet supports services including vServer, vStorage, vMonitor, Terraform, and VKS. | 06/08/2024 | HCM03-HAN01 | Argument Integration with Terraform |
| DHCP Options Sets | With the need to customize the DNS Server for virtual machines, DHCP Options Sets allow the specification of DNS Server IP addresses for virtual machines within a VPC. This helps control and optimize how virtual machines access network services and resolve domain names. This feature is currently applied in the HCM03 region. | 10/09/2024 | HCM03 | DHCP Options Set |
| Function | Description | Release date | Region | References |
|---|---|---|---|---|
| Bandwidths | GreenNode is pleased to introduce an upgrade to the Bandwidths service within the GreenNode ecosystem. Specifically, this upgrade includes:
Currently, GreenNode is maintaining both the old and new bandwidth portals in parallel. We plan to close the old bandwidth portal on July 7, 2024. During this time, the system will not automatically switch your old Bandwidth packages to the new portal. You will need to manually delete the old Bandwidth packages on the old portal and purchase new packages on the new portal. | 07/06/2024 | HCM-03 | Bandwidth |
| Region HAN-01 |
| 05/06/2024 | HAN-01 | vServer |
| Service endpoints |
| 06/05/2024 | HCM-03 | Create endpoint |
| Search Servers |
| 05/2024 | HCM-03 | Server |
| Volume |
| 05/2024 | HCM-03 | Volume |
| vLB |
| 05/2024 | HCM-03 | LoadBalancer |
| Tags in Network Interface |
| 05/2024 | HCM-03 | External Interface |
| Network Interface |
| 02/05/2024 | HCM-03 | External Interface |
| Image |
| 02/05/2024 | HCM-03 | Image |
| SSO - IAM |
| 10/04/2024 | HCM-03 | IAM |
| Snapshot |
| 03/04/2024 | HCM-03 | Snapshot |
| Share Snapshot |
| 03/04/2024 | HCM-03 | Share Snapshot |
| Function | Description | Release date | Region | References |
|---|---|---|---|---|
| Network VPCs |
| 07/03/2024 | HCM-03 | Virtual Private Cloud (VPC) |
| Network ACL |
| 07/03/2024 | HCM-03 | Network ACL |
| New Policy L7 |
| 08/03/2024 | HCM-03 | Listener Policies |
| User Data |
| 13/03/2024 | HCM-03 | UserData |
| Function | Description | Release date | Region | References |
| Kubernetes Cluster | Optimize the use of Kubernetes Cluster with the Docker Volume and Boot Volume configuration feature when creating a Node Group: Docker Volume Configuration: Enjoy maximum flexibility with the ability to customize Docker Volume's multi-faceted configuration parameters by size, type, and IOPS to meet your exact requirements. Boot Volume Configuration: You don't need to worry about configuring Boot Volume, The system will automatically configure according to the initial configuration of the cluster. However, the Boot Volume configuration cannot be edited by the user to ensure that the system always operates stably and achieves the best performance. | Nov 15, 2023 | HCM-03-1A | N/A |
| Kubernetes Cluster | We are pleased to announce the release of the latest versions of Kubernetes Cluster, including versions 1.24.17, 1.25.14, 1.26.9, 1.27.6 to 1.28.2. These updates bring many important improvements and fixes, helping you manage your cluster more efficiently and securely. To experience it now, please visit the home interface and explore the power of Cluster creation with these new versions. | Nov 09, 2023 | HCM-03-1A | N/A |
| Create and manage Address Pair Interface with Terraform | You can use Terraform to manage Address Pair Interface, Terraform is an Infrastructure as Code (IaC) tool, to automate the process of creating, configuring, and managing APIs in a cloud environment. cloud. This means you will define the API's configuration in code, rather than doing it manually through the user interface or other cloud management tools. Terraform helps with process automation, consistency, change tracking, easy integration, and security management, which helps reduce errors, create consistency across environments, and manage network infrastructure more effectively. | Oct 11, 2023 | HCM-03-1A | N/A |
| Create & manage Virtual IP Address with Terraform | Using Terraform to manage Virtual IP (VIP) Address in cloud computing refers to the use of Terraform, an Infrastructure as Code (IaC) coding tool, to automate the creation and configuration process. , and manage virtual IP (VIP) addresses in cloud environments. This includes defining the configuration of VIP Addresses and related resources in code, rather than doing it manually through the user interface or other cloud management tools. Using Terraform for Virtual IP Address management in cloud computing offers many benefits, including process automation, consistency across environments, change tracking and control, easy integration, and management. VIP Address security management, and configuration consistency, help reduce errors and facilitate more reliable network infrastructure management in cloud environments. | Oct 11, 2023 | HCM-03-1A | N/A |
| Create & manage Route table with Terraform | Using Terraform to manage Route Tables in cloud computing refers to using Terraform, an Infrastructure as Code (IaC) tool, to automate the creation, configuration, and management process. route tables in a cloud environment. This means you will define route table configuration and routing information in code, instead of doing it manually through the user interface or other cloud management tools. Using Terraform offers many other benefits, including automation of creating, updating, and deleting route tables, consistency across environments, change tracking and control, and easy integration. , and manage the security of route tables, helping to reduce errors and facilitate more reliable network infrastructure management in cloud environments. | Oct 11, 2023 | HCM-03-1A | N/A |
| Snapshot | Snapshot - great new feature, will bring you a completely new user interface, beautiful and easy to use. You'll be able to manage your snapshots more quickly and conveniently than ever before. Explore the exciting features Snapshot offers, including: Friendly and professional user interface Our new user interface is designed to help you manage creating and restoring snapshots quickly and easily. You will easily operate this feature without much difficulty. Create Snapshots for virtual servers and virtual drives Creating Snapshots for virtual servers and drives is a powerful feature, allowing you to create backups exactly at the desired point in time. With this capability, in addition to creating individual Snapshots for virtual drives, you can also create Snapshots for virtual servers with attached drives, to ensure that all your data is fully protected and protected. safe. Restore Snapshots Restore virtual servers and volumes easily from Snapshots to revert to previous data states and minimize system downtime. This feature gives you flexibility and confidence in managing your data and protecting your systems. With this new updated version, we are committed to providing you with powerful tools to protect and manage your data more effectively. Update now to experience this progress! | Oct 03, 2023 | HCM-03-1A | |
| Backup | New backup update: Incremental Backup: Now your data is protected more effectively. Incremental backups only record data changes since the last backup, reducing the amount of data that needs to be transferred and the time needed to perform the backup. This conserves your system resources and network bandwidth, allowing you to focus on more important work. Hourly Backups: In addition to creating daily, weekly, and monthly backups, we now offer Hourly Backups. Hourly backups not only ensure your data is protected more often, but also help minimize data loss and quickly recover from unexpected events. With this feature, you have near real-time data protection, helping to ensure the continuity of your important information. | Oct 03, 2023 | HCM-03-1A |
| Function | Description | Release date | Region | References |
| vDB (Database as a Service) | Email notification for resource usage reaching dangerous thresholds: Active Monitoring: This email notification feature actively monitors database usage and sends notifications when Memory, CPU, or Hard Drive usage exceeds a defined threshold of 85%. Default Threshold: 85% is the system's default threshold, applicable to all Database as a Service users at GreenNode Timely Notifications: Receive timely email notifications, ensuring you're aware of critical resource usage before they become performance bottlenecks. Resource Optimization: With these notifications, you can optimize resource allocation and prevent potential disruptions or delays due to resource constraints. Ease of Use: This notification system is user-friendly, making it easy for users to configure and manage their threshold notifications. | Sept 28, 2023 | HCM-03-1A | |
| vDB (Database as a Service) | Released Postgresql versions 13 & 15, Redis version 6.2 Performance optimization: Latest Postgresql versions 13 & 15, Redis version 6.2 bring significant performance improvements, allowing faster data processing and reduced query response times. Enhanced Security: These new versions include updated security features, improving the protection of your data with improved encryption and authentication mechanisms. Scalability: Postgresql 13 & 15 and Redis 6.2 offer improved scaling options, making it easier to handle growing datasets and workloads. Compatible: They maintain compatibility with previous versions, ensuring a smooth transition to existing applications. Optimized Resource Management: These instances come with optimized resource management capabilities, allowing better utilization of Memory, CPU and Hard Drive Resources. | Sept 15, 2023 | HCM-03-1A | |
| Interconnect | Direct and private physical connection from your network to the GreenNode: The launch of the all-new Interconnect, an ambitious integrated solution for network connectivity and management. This feature includes many important parts, including Direct Connect, MultiCloud Interconnect, VPN Interconnect and Hybrid Interconnect. Here's an overview of what you can expect: Direct Connect:
VPN Interconnect:
Hybrid Interconnect:
| Sept 15, 2023 | HCM-03-1A | |
| Volume | Add NVMe SSD Volume - Boost Storage Performance: We've integrated the new NVMe SSD, a dramatic improvement in storage performance, into your virtual server infrastructure. With the appearance of NVMe SSD drives, data processing on virtual server volumes has been optimized many times. Compared to traditional SATA SSDs, NVMe SSDs provide many times faster read/write speeds and better I/O handling. This means that your application will work faster and more efficiently when using a virtual server service This new feature allows you to choose between NVMe SSDs and traditional SATA SSDs when creating or upgrading volumes for your virtual servers. You have more control and flexibility with a choice of storage to suit the specific needs of your project. | Aug 14,2023 | HCM-03-1A | Volume |
| Virtual server backup service (Backup) | We're excited to announce the latest version of our service - version 2 of the Backup service is out with lots of exciting improvements and new features to enhance your experience. Here are some highlights in this release: Added Backup Now feature to make backups easy:
Easy management with Backup delete feature directly from the driver:
Email notification when successfully creating a backup server:
We hope that this release will give you a better experience and help you manage your data more efficiently. Thank you for always supporting our service. | Aug 04,2023 | HCM-03-1A | Virtual server backup service |
| Connect to Windows and Linux Server using RDP and SSH Client via console | In this update, we focus on optimizing the Server connection process, bringing convenience and simplicity like never before to users. Now, you can set up and connect to Windows and Linux Server via RDP and SSH Client directly on our driver interface, no more switching between different applications. Save time and enjoy an easy connection experience with this new version. | July 19, 2023 | HCM-03-1A | Connect to virtual server |
| Function | Description | Release date | Region | References |
| Function | Description | Release date | Region | References |
| Peering | Supported features for this peering update: Visualized User Interface: Peering has undergone a complete visual transformation, giving it a new and modern look and feel. We've carefully created a new design to enhance usability, making it easier for you to navigate and manage your Peerings. Full Feature Support: We guarantee that all the features and capabilities available in the previous interface are fully supported in this Version. | June 7, 2023 | HCM-03-1A | Peering |
| Route table | Experience the new Route table with listed features: User Interface Redesign: The Route table has undergone a major visual overhaul, providing a modern and intuitive interface. The new design focuses on improving usability, ensuring that users can easily navigate and manage their Route table with ease. Full Feature Support from the Old Version: We understand the importance of a seamless transition, and so this New Version ensures that all the features and capabilities from the previous interface are included. fully supported. You can continue to use familiar functions while benefiting from an enhanced user interface. Specify VPC instead of Subnet in Route table: In order to optimize and simplify the operation and decentralize network resources, you can now specify VPC instead of Subnet in your Route table. | June 7, 2023 | HCM-03-1A | Route Table |
| Kubernetes Cluster | We're excited to announce the release of a major update to the Kubernetes Cluster module, introducing a major overhaul of the new user interface and incorporating significant improvements to the interface. before. Key features and improvements: Redesigned User Interface: The Kubernetes Cluster module has been completely redesigned, providing a more intuitive and user-friendly interface. We've carefully reviewed user feedback and incorporated best practices to make it easier and more efficient to manage your Kubernetes clusters. Enhanced Feature Set: With the New Version, we've extended the capabilities of the Kubernetes Cluster module. Many new features have been introduced to empower users with greater control and flexibility over their clusters along with improved efficiency enhancement options such as High Availability, Auto Healing, Auto Monitoring, Ingress Control, Auto Scaling. These additions are the result of incorporating valuable insights from the previous interface, ensuring an enhanced experience. Configuration of ETCD storage is optimized with 2 main configuration packages: Medium and Small to help meet the needs of using Kubernetes clusters according to the size of organizations and individuals. Performance improvements: We've made significant optimizations to enhance the performance and responsiveness of the Kubernetes Cluster. You can expect faster Kubernetes Cluster load times, smoother navigation. Streamlined Workflows: The release introduces streamlined workflows that simplify cluster management tasks. We've refined and optimized the user flow, reducing complexity and allowing users to accomplish their goals more efficiently. Bug fixes and stability: In addition to new features and improvements, we've addressed many issues and bugs reported by our users. The update includes stability improvements that ensure a more robust and reliable experience when working with Kubernetes clusters. | May 29, 2023 | HCM-03-1A | Kubernetes Cluster |
| Initialize & Manage Load Balancer with Terraform | Allows users to initialize Load Balancer with Terraform in just a few simple commands. Overall, using Terraform to manage the Load Balancer allows for easy version management, change control, and configuration replication. You can use Terraform code to build and configure load balancers consistently and reusable in a variety of environments. | May 26, 2023 | Initialize & Manage Load Balancer with Terraform | |
| Initialize & Manage Kubernetes Cluster (K8S) with Terraform | Allows users to initialize Kubernetes Clusters with Terraform in just a few simple command lines, which simplifies the deployment, management, and scaling of your Kubernetes Clusters, while providing consistency and capacity repeatability in an infrastructure with multiple clusters. | May 15, 2023 | HCM-03-1A | Initialize & Manage K8S with Terraform |
| Function | Description | Release date | Region | References |
| Migrate virtual servers | Allows users to migrate virtual servers from QTSC to HCM-03-1A | 1st Quarter/ 2023 | HCM-03-1A | Virtual server migration service |
| Virtual server backup service (Backup) | Our backup service, has completely redesigned the user interface. This update introduces several new features to optimize user experience and improve backup management. Main highlights:
| March 16, 2023 | HCM-03-1A | Virtual server backup service |
|
|
|
|
|
|
|
|
|
|
Note:
Windows license usage is authenticated according to the IP where the VM purchased the license, then system will active the license.
| | ------------------------------------------------------------------------------------------------------------------------------------------------------ | \| STT | Resource | Type of service | Default | Adjust | Description |
| 1 | SSO User Account/ Email-SĐT | Account | 20 | Yes | Maximum number of SSO User Accounts allowed to register for 1 Email - Phone number through GreenNode Portal |
| 2 | IAM User Account/ Root User Account | Account | 20 | Yes | Number of IAM User Accounts allowed to be created for Root User Accounts through IAM Portal |
| 3 | Service Account/ Root User Account | Account | 20 | Yes | Number of Service Accounts allowed to be created for Root User Accounts through IAM Portal |
| 4 | Acl_Policy | Server | 10 | Yes | Maximum number of Acl Policy per 1 Root User Account |
| 5 | Acl_Policy_Rule | Server | 100 | Yes | Maximum number of Acl Policy Rules per 1 Root User Account |
| 6 | Bandwidth | Server | 100 | Yes | Maximum number of Bandwidth types per 1 Root User Account |
| 7 | Cluster | Server | 10 | Yes | Maximum number of Clusters on 1 Root User Account |
| 8 | Floating_Ip | Server | 50 | Yes | Maximum number of Floating IPs per 1 Root User Account |
| 9 | Image | Server | 50 | Yes | Maximum number of images per 1 Root User Account |
| 10 | Image_Size | Server | 1000 | Yes | Maximum Number of Internet Gateways on 1 Root User Account |
| 11 | Internet_Gateway | Server | 10 | Yes | Maximum GB Memory on 1 Root User Account |
| 12 | Mem | Server | 500 | Yes | Maximum GB of Memory on 1 Root User Account |
| 13 | Minion_Per_Node_Group | Server | 10 | Yes | Maximum Number of Minions in 1 Node Group for 1 Root User Account |
| 14 | Network_Interface_Per_Server | Server | 10 | Yes | Maximum Number of Network Interfaces on 1 Server for 1 Root User Account |
| 15 | Node_Group_Per_Cluster | Server | 5 | Yes | Maximum Number of Node Groups in 1 Cluster for 1 Root User Account |
| 16 | Route | Server | 100 | Yes | Maximum Number of Routes on 1 Root User Account |
| 17 | Route_Table | Server | 20 | Yes | Maximum Number of Route Tables on 1 Root User Account |
| 18 | Secgroup | Server | 10 | Yes | Maximum Number of Security Groups on 1 Root User Account |
| 19 | Secgroup_Rule | Server | 100 | Yes | Maximum Number of Security Group Rules on 1 Root User Account |
| 20 | Server_Group | Server | 5 | Yes | Maximum Number of Server Groups on 1 Root User Account |
| 21 | Service_Endpoint | Server | 10 | Yes | Maximum Number of Service Endpoints on 1 Root User Account |
| 22 | Ssh_Key | Server | 20 | Yes | Maximum Number of SSH Keys on 1 Root User Account |
| 23 | Subnet | Server | 30 | Yes | Maximum Number of Subnets on 1 Root User Account |
| 24 | Vcpu | Server | 1000 | Yes | Maximum Number of VCPUs on 1 Root User Account |
| 25 | Virtual_Ip_Address | Server | 3 | Yes | Maximum Number of Virtual IP Addresses on 1 Root User Account |
| 26 | Vm | Server | 150 | Yes | Maximum Number of Servers on 1 Root User Account |
| 27 | Volume | Server | 200 | Yes | Maximum Number of Volumes on 1 Root User Account |
| 28 | Volume_Maxsize | Server | 5000 | Yes | Maximum GB of Capacity for Volumes on 1 Root User Account |
| 29 | Volume_Size | Server | 10000 | Yes | Maximum GB Total Capacity for Volumes on 1 Root User Account |
| 30 | Vpc | Server | 10 | Yes | Maximum Number of VPCs on 1 Root User Account |
| 31 | Certificate_Per_Lb | Load balancer | 5 | Yes | Maximum Number of Certificates on Load Balancer for 1 Root User Account |
| 32 | Listener_Per_Lb | Load balancer | 10 | Yes | Maximum Number of Listeners on Load Balancer for 1 Root User Account |
| 33 | Load_Balancer | Load balancer | 10 | Yes | Maximum Number of Load Balancers on 1 Root User Account |
| 34 | Member_Per_Pool | Load balancer | 20 | Yes | Maximum Number of Members in 1 Pool for 1 Root User Account |
| 35 | Policy_Per_Lb | Load balancer | 10 | Yes | Maximum Number of Policies for 1 Load Balancer on 1 Root User Account |
| 36 | Pool_Per_Lb | Load balancer | 10 | Yes | Maximum Number of Pools for 1 Load Balancer on 1 Root User Account |
| 37 | As_Cluster | vAS | 5 | Yes | Maximum Number of AS Clusters on 1 Root User Account |
| 38 | As_Node | vAS | 10 | Yes | Maximum Number of AS Nodes on 1 Root User Account |
| 39 | As_Policy | vAS | 10 | Yes | Maximum Number of AS Policies on 1 Root User Account |
| 40 | As_Profile | vAS | 10 | Yes | Maximum Number of AS Profiles on 1 Root User Account |
| 41 | As_Receiver | vAS | 20 | Yes | Maximum Number of AS Receivers on 1 Root User Account |
| 42 | As_Scheduler | vAS | 10 | Yes | Maximum Number of AS Schedulers on 1 Root User Account |
Scheduled O&M operating model
O&M service activation flow
Scheduled Task lifecycle — from creation to each individual run
Execution status model
MIG architecture on vServer: Docker + NVIDIA Container Toolkit manages both MIG GPU (2x 3g.40gb) and non-MIG GPU (full 80 GB) on the same machine
All 7 MIG profiles available on H100 80GB HBM3 — inspect with nvidia-smi mig -lgip
MIG successfully enabled on GPU 0 — mig.mode.current = Enabled
nvidia-smi mig -lgip lists all available profiles and the maximum instance count for each
2 MIG instances of type 3g.40gb created successfully — each with its own UUID and VRAM allocation
Containers on device=0:0 and device=0:1 see different MIG UUIDs — isolation confirmed
2 containers running simultaneously on 2 MIG instances — no conflict, fully independent memory
vLLM serving Qwen2.5-7B-Instruct on MIG 3g.40gb — 34 GB VRAM in use, API responding normally
Benchmark results: 16.27 req/s, 18,739 tokens/s on MIG 3g.40gb with Qwen2.5-7B-Instruct
Because this is attached interface, you can execute the External Interface directly from within the instance.
You must configure to use its IP address from within instance (configure static IP or DHCP)
| | Method to disassociate an IP address |After a Floating IP address is assigned to an instance, the FIP can only be disassociated from GreenNode view.
Billing for Floating IP will based on reservation request if any.
|After a External Interface is attached to an instance, the External Interface can only be detach from GreenNode.
Billing still active until External Interface released
| | Method to release an IP address | When Floating IP are disassociated from any instances, you can delete it from Floating IP page. | When External Interface are detached from any instances, you can delete it from External Interface page. | # Floating IP An floating IP address (FIP) is a public IP address that you can reserve and use as an independent resource. FIPs can be retained independently and associated with or disassociated from primary interface of instances in virtual private clouds (VPCs). ### **Overview** FIPs are NAT IP addresses that are located in the gateway of GreenNode. By means of NAT, FIPs are mapped to the primary network interfaces of the vServer instances. You can associate FIPs with vServer instances that are located in VPCs to enable the instances to communicate over the Internet. FIPs is invisible inside the operating systems of vServer instances. {% hint style="warning" %} When using a Floating IP for outbound Internet access, keep the packet MTU **<= 4000** to reduce the risk of packet loss. For MTU/DF-flag sensitive workloads (VPN tunnels, SIP/UDP, etc.), see [MTU & “DF flag” best practice on GreenNode](/vserver/vmarketplace/network-software-installation/pfsense-on-hcm03/mtu-and-df-flag-best-practice-on-vng-cloud). {% endhint %} ### **Limits** FIPs can be associated with vServer instances. An FIP can be associated only with an vServer instance that meets the following requirements: * The vServer instance is located in a VPC. * The vServer instance is located in the same zone as the FIP. * The vServer instance is in the **Running** or **Stopped** state. * No External Interface are attached. *** ### **Operations** #### Create an Floating IP A Floating IP is created along with the Server initialization. However, you can view the list of Floating IPs attached to the Server in the vServer control panel at the following link:| Criteria | Active/Active | Active/Passive |
| Performance | High, traffic shared across nodes | Lower, only one node handles traffic |
| Availability | Minimal interruption (near-zero downtime) | Brief interruption during failover |
| Cost | Higher (multiple active nodes) | Lower (one active, one standby) |
| Complexity | Higher (sync, load balancing) | Lower (mainly failover configuration) |
| Best fit | Large web systems, distributed platforms | Internal apps, cost-sensitive systems |
| Your system needs | Recommended mode |
|---|---|
| No downtime tolerated | Active/Active |
| High throughput required | Active/Active |
| Small system, cost first | Active/Passive |
| Can tolerate brief downtime | Active/Passive |
Stateful:
Stateless:
| Priority | Type | Protocol | Port range | Source | Allow/ Deny | Ghi chú |
|---|---|---|---|---|---|---|
| 0 | Inbound | ANY | 0-65535 | 0.0.0.0/0 | Allow | Can Delete/Edit Inbound rules. |
| 2000 | Inbound | ANY | 0-65535 | 0.0.0.0/0 | Deny | Cannot Delete/Edit Inbound rules. |
if you want to **delete** the newly created rule.
6. Edit **Priority:** enter the weight (priority) for the rule. The rule weight must not be the same as a number already in the Network ACL. We process rules by weight, starting from the lowest to the highest, regardless of Allow or Deny. The maximum weight you can set is **32766**.
7. Edit **Protocol:** add the access protocol you want to allow/deny to enter the Subnet. We are providing you with 1 of 4 options: ANY, TCP, UDP, ICMP.
8. Edit **Port range:** the port number or range of ports to start and end.
9. Edit **Source:** the desired IP or IP range/CIDR to allow/deny access according to Inbound rules.
10. Edit **Allow/Deny:** allow or deny the specified traffic.
11. If you want to add more Inbound rules, continue to select **Add rule** and repeat steps 6, 7, 8, 9, and 10.
12. If you want to delete multiple Inbound rules, continue to select the icon at the rules you want to delete. **Note: You cannot edit or delete the default Inbound rules deny created by us.**
13. Select **Save** to save the entered/selected edits or select **Cancel** to cancel the edit changes.
***
#### Editing the Outbound Rules List
To edit the Outbound rule list (rules that allow traffic to exit), follow these steps:
1. Access the vServer service home page at the following link: if you want to delete the newly created rule.
6. Edit **Priority:** enter the weight (priority) for the rule. The rule weight must not be the same as a number already in the Network ACL. We process rules by weight, starting from the lowest to the highest, regardless of Allow or Deny. The maximum weight you can set is **32766**.
7. Edit **Protocol:** add the access protocol you want to allow/deny to exit the Subnet. We are providing you with 1 of 4 options: ANY, TCP, UDP, ICMP.
8. Edit **Port range:** the port number or range of ports to start and end.
9. Edit **Destination:** the desired IP or IP range/CIDR to allow/deny access according to Outbound rules.
10. Edit **Allow/Deny:** allow or deny the specified traffic.
11. If you want to add more Outbound rules, continue to select **Add rule** and repeat steps 6, 7, 8, 9, and 10.
12. If you want to delete multiple Outbound rules, continue to select the icon at the rules you want to delete. **Note: You cannot edit or delete the default Outbound rules deny created by us.**
13. Select **Save** to save the entered/selected edits or select **Cancel** to cancel the edit changes.
***
#### Associating/Disassociating a Subnet with a Network ACL
To apply the rules of a Network ACL to a specific subnet, you need to associate that subnet with the Network ACL. You can associate a Network ACL with multiple subnets, but a subnet can only be associated with one Network ACL at a time.
To associate a subnet with a Network ACL, follow these steps:
1. Access the vServer service home page at the following link: 
.
2. In the **Associated Subnets** section, you can disassociate a **Subnet** from the **Network ACL** by selecting the Subnet you want to disassociate.
6. Select **Save** to save the entered/selected edits or select **Cancel** to cancel the edit changes.
{% hint style="info" %}
**Notes:**
* When you associate a subnet with a new Network ACL, the Inbound rules and Outbound rules of the new Network ACL will start to apply to traffic to and from that subnet.
* You can associate a subnet with a different Network ACL at any time. At this time, we will disconnect the old association and perform the new association according to your edit, ensuring that at any time a subnet can only be attached to one Network ACL. Changing the subnet association can affect the traffic to and from that subnet.
{% endhint %}
***
#### **Delete a Network ACL**
You can only delete a Network ACL if it is not associated with any subnets. If the Network ACL you want to delete is still associated with subnets, follow the instructions above to **Disassociate Subnets from a Network ACL** before deleting the Network ACL.
**To delete a Network ACL, follow these steps:**
1. Access the vServer service home page at the following link: 
.
4. In the delete confirmation screen, select **Delete** if you are sure you want to delete this Network ACL, or **Cancel** if you want to cancel the deletion.
