Skip to main content

AWS : Elastic Load Balancer Exam Tips and Preparation Key Points



Start with what is Elastic Load Balancing?

Elastic Load Balancing automatically distribute incoming application traffic to multiple destinations, such as Amazon EC2 instances, containers, IP address, and lambda functions. It can handle a variety of application traffic load in a single Availability Zone or multiple Availability Zones.

Key points:

The following two types of load balancer:

1. Internet Facing: has public IP

2. Internal Load Balancer: routes traffic within a VPC

There are three categories of Load Balancer:

1. Application Load Balancer
2. Network Load Balancer
3. Classic Load Balance

First Application Load Balancer

Operates at Layer 7.
Supports WebSockets and Secure WebSockets.
Supports SNI.
Supports IPv6.

Second Network Load Balancer ( The NLB is the recommended Load Balancer to be used at Layer 4)

Operates at Layer 4.
Preserves the source IP.
Provides reduced latency compared to other Load Balancers.
Handles millions of requests per seconds.

Third Classic Load Balancer
Operates at Layer 4.
Features Cross Zone Load Balancing.

Idle Connection Timeout: 
Is the period of inactivity between the client and the EC2 instance in which the Load Balancer terminates the connection. By default, it is 60 seconds.

Enable Cross Zone Load Balancing, to distribute traffic evenly across the pool of registered AWS instances.

Connection Draining stops the load balancer sending traffic to faulty instances.

Proxy Protocol: To receive the clients IP and User Agent, it needs to be enabled. (only on Network Load Balancer and Classic Load Balancer)

Sticky Sessions: Ensures that the load balancer sends future user request to the EC2 instance that received the initial request.

Auto Scaling Group: Lets you increase or decrease the number of EC2 instances based upon CPU, RAM, Scheduled Scaling (usually used when you predict that there will be an increase in load in X time ex: Marketing Campaign)

Thanks for being here

Comments

Popular posts from this blog

How to Speedup your WordPress site with Amazon CloudFront.

Introduction A WordPress performance is quite excellent . The number of WordPress plugins to handle performance is such evidence. But the easiest way to improve your user experience is to accelerate the entire WordPress website using CloudFront. This will help you not only improve site response time reduces the necessary infrastructure, reducing the load on the Web server, so you can reduce the total cost of the infrastructure works WordPress. CloudFront is actually a site can greatly help your site to respond to unexpected load when gained popularity. Today this post is to clarify the method of providing a reasonable standard configuration on the WordPress website or blog. How does CloudFront help? Amazon CloudFront is to improve the user's experience accessing the Web site in several ways: 1.  Anycast DNS is to ensure that customers are routed to the nearest edge location. 2.  The cached content is available to users at the edge position (i

Linux System : Free Employee Monitoring with Automatic Screenshots

Introduction :   A utomatic screen-shots  of Linux system directly import  on your web server with Linux samba server service and scrot command. 1)  Setup web panel UI on your web server :   Get web panel PHP/HTML code from Github URL: https://github.com/raj412/Employee-Monitoring-for-Linux-System It’s work in Linux server LAMP environment(no need database for this configuration ) Defult login username password is admin/1234. You can change username/passwrod from login.php file in line number #6 Login Page : Dashboard : Screenshot Page : 2)  Samba server configuration on web server : I.  Install Samba on your server where you setup Linux screenshot log system web panel. sudo apt-get update sudo apt-get install samba II.  Set a password for your user in Samba sudo smbpasswd -a <user_name> III.  Share gallery-images folder from you web panel. This is my web panel gallery-images p

How to control high traffic load on Apache servers : optimization performance of APACHE2 & PHP-FPM

Everyone handle high traffic loads  on Apache server. During down-time they forget to check server memory . Apache not used lot of memory  still server not responding. All time we restart Apache service and all things will start working good. I also faced same issue numerous time and all-time  used same solution : Restart Apache. After lots of research and reading found one solution. In this blog you see step-by-step guide to apache2 performance settings. System environment: Intel(R) Xeon(R) CPU 3.10GHz, 4 cores | 8GB RAM Ubuntu 16.04 Apache2 version using mpm_event PHP FPM (5.6,7.1) First,  Calculate process size : Download : python script file “ps_mem.py” from Github Open this and ps_mem.py file upload on you server :  https://github.com/raj412/ps_mem chmod a+x ps_mem.py sudo python ps_mem.py Output like this:  See here : 12 Apache processes, consuming a total of  35.7MiB, so each Apache process is using roughly 3MiB of RAM. The 42 php-fpm process u