Flexible Load Balancing automatically distributes traffic across multiple targets – Nobus FCS instances, containers and IP addresses – in a single Availability Zone or multiple Availability Zones.
Flexible Load Balancing can detect unhealthy targets, stop sending traffic to them, and then spread the load across the remaining healthy targets.
Use Nobus Virtual Private Environment (Nobus VPE) to create and manage security groups associated with load balancers to provide additional networking and security options. You can also create an internal (non-internet-facing) load balancer.
Flexible Load Balancing provides integrated certificate management and SSL/TLS decryption, allowing you the flexibility to centrally manage the SSL settings of the load balancer and offload CPU intensive work from your application.
You can load balance HTTP/HTTPS applications for layer 7-specific features, or use strict layer load balancing for applications that rely on the TCP and UDP protocols.
Flexible Load Balancing provides integration with Nobus metrics and request tracing in order to monitor performance of your applications in real time.
Flexible Load Balancer provides basic load balancing across multiple Nobus FCS instances and operates at both the request level and connection level. Flexible Load Balancer is intended for applications that were built within the FCS network. We recommend Application Load Balancer for Layer 7 and Network Load Balancer for Layer 4 when using Virtual Private Cloud (VPE).
High Availability
You can distribute incoming traffic across your Nobus FCS instances in a single Availability Zone or multiple Availability Zones. Flexible Load Balancer automatically scales its request handling capacity in response to incoming application traffic.
Health Checks
Flexible Load Balancer can detect the health of Nobus FCS instances. When it detects unhealthy FCS instances, it no longer routes traffic to those instances and spreads the load across the remaining healthy instances.
Security Features
When using Nobus Virtual Private Cloud (Nobus VPE), you can create and manage security groups associated with Flexible Load Balancer to provide additional networking and security options. You can also create a Flexible Load Balancer without public IP addresses to serve as an internal (non-internet-facing) load balancer.
SSL Offloading
Flexible Load Balancer supports SSL termination, including offloading SSL decryption from application instances, centralized management of SSL certificates, and encryption to back-end instances with optional public key authentication. Flexible cipher support allows you to control the ciphers and protocols the load balancer presents to clients.
Sticky Sessions
Flexible Load Balancer supports the ability to stick user sessions to specific Nobus FCS instances using cookies. Traffic will be routed to the same instances as the user continues to access your application.
IPv6 Support
Flexible Load Balancer supports the use of both the Internet Protocol version 4 and 6 (IPv4 and IPv6) for FCS networks.
Layer 4 or Layer 7 Load Balancing
You can load balance HTTP/HTTPS applications and use Layer 7-specific features, such as X-Forwarded and sticky sessions. You can also use strict Layer 4 load balancing for applications that rely purely on the TCP protocol.
Operational Monitoring
Flexible Load Balancer metrics such as request count and request latency are reported by Nobus CloudWatch.
Logging
Use the Access Logs feature to record all requests sent to your load balancer, and store the logs in Nobus S3 for later analysis. The logs are useful for diagnosing application failures and analyzing web traffic. You can use Nobus CloudTrail to record Flexible Load Balancer API calls for your account and deliver log files. The API call history enables you to perform security analysis, resource change tracking, and compliance auditing.