Now Network Load Balancer Is Accessible In Asia Pacific (Osaka) Region

Network Load Balancer is an ideal solution for load balancing of Transmission Control Protocol (TCP) and Transport Layer Security (TLS) traffic where utmost performance is essential. Network Load Balancer is exceedingly available. Network Load Balancer is created to manage traffic as it increases and can load balance millions of requests/sec. Network Load Balancer provides very low latencies for latency-sensitive applications. Besides, Network Load Balancer is optimized to manage unexpected and traffic patterns while using one static IP address per Availability Zone. Network Load Balancer is the fourth layer of the Open Systems Interconnection (OSI) model routes traffic to targets inside Amazon Virtual Private Cloud (Amazon VPC). Network Load Balancer functions at connection level (Layer 4), directing connections to Amazon EC2 instances, containers, and IP addresses linked with IP protocol data. Additionally, it stores the client-side source IP, permitting applications to view the IP address of the client that can then be utilized by applications for additional functioning. Now this Network Load Balancer feature is accessible in the Asia Pacific (Osaka) region. To get the full list of AWS Regions where Network Load Balancer is accessible, refer AWS Region Table. To know further on Network Load Balancer, refer the AWS blog or Elastic Load Balancing.

Deep Dive Into Amazon Route 53

Amazon Route53 is a cloud based Domain Name System (DNS) web service.

It is developed to route end users to Internet applications like www.yourchoicexyz.com will be resolving some IP address like 192.0.2.4 as numeric. Route53 is also compatible with IPV6.

Amazon Route53 effectively connects any user request with infrastructures running in AWS like :

1. EC2 instances
2. Elastic Load balancers
3. Amazon S3 buckets

Also, can connect infrastructure outside AWS.

Simply we can configure Route53 for checking DNS health checks and depending on the status of health check routing traffic to healthy endpoints. Amazon Route53 also helps with domain registration.

Ex. yourchoicexyz.com and Amazon Route53 will configure DNS settings for domain automatically.

Benefits :

1. Flexible :

• Amazon Route53 can route traffic based on the following criteria such as latency, geo location and endpoint health check. Also, can configure multiple traffic policies and define which policy is to be active at a given time.
• You can create and change traffic policies using the GUI in the Route53 console or Amazon Route53 API.
• Feature of Traffic Flow versioning can put the history of changes in traffic policies, so that we can easily roll back to any previous version using  console or API.

2. Fast :

• Route53 is designed to automatically route end users to optimal locations depending on network condition. It also lets you further improve your end user's experience by running your application in multiple locations. 
• Route53 offers low query latency for your end users and low update latency for DNS management.

3. Secure :

• By using Access Management (IAM) and Route53 with AWS identity, we can grant unique credentials and manage permissions for user in your AWS account.

4. Cost-Effective :

• You simply pay only for the resources you use. The number of queries that the service answers for each of your domains through the service.

Terms Used For Route53 :

1. Hosted Zone :

• Hosted zone is nothing but configuring a new domain under Route53 to manage records for the domain. Registering A domain under Route53 is nothing but creating a hosted Zone.

2. Record Set :

• In each Hosted Zone, We can create multiple Record Sets. It is nothing but adding or creating or configuring any record for that particular domain.
• Types of records can be created as record set are A Record, CNAME Record, MX Record, TXT records, Alias etc.
• In the Route53 console, we are also intimated with the syntax and example for adding record sets for any hosted zone.

Kindly go through below screen-shots which helps for more practical view on configuring Route53 in AWS console :

Image 1 : To Create Hosted Zone



Image 2 : To Create Record Set in Created Record Zone

 

We hope this blog will help to understand the Amazon Route 53 basics. If you have any queries related to this blog topic, then feel free to write us at support@cloud.in  

Application Load Balancer Vs. Classic Load Balancer

Elastic Load Balancing automatically divides incoming application traffic over different targets, like Amazon EC2 instances, containers, IP addresses, and Lambda functions. It can manage the differing load of your application traffic in one Availability Zone or over different Availability Zones. Elastic Load Balancing offers three types of load balancers which all presents the high availability, automatic scaling, and robust security required to make your applications defect liberal.

Let's compare Application Load Balancers and Classic Load Balancers,

• Classic Load Balancer

• Application Load Balancer

1. Usage Pattern

• A Classic Load Balancer is employed for simple load balancing of traffic across multiple EC2 instances.
• Application Load Balancer is employed for microservices or container-based architectures where there is a need to route traffic to multiple services or load balance across multiple ports on the same EC2 instance.

2. Supported Protocols

• Classic Load Balancer work at layer 4 and supports HTTP, HTTPS, TCP, SSL
• Application Load Balancer work at layer 7 and supports HTTP, HTTPS, HTTP/2, WebSockets

3. Supported Platforms

• Classic Load Balancer supports both EC2-Classic and EC2-VPC
• Application Load Balancer supports only EC2-VPC

4. Back-end Server Authentication

• Back-end Server Authentication allows authentication of the instances. Load balancer communicates with associate instance provided that the general public key that the instance presents to the load balancer matches a public key within the authentication policy for the load balancer. Classic Load Balancer supports whereas Application Load Balancer doesn't support Back-end Server Authentication

5. Back-end Server Authentication

• Back-end Server Authentication allows authentication of the instances. Load balancer communicates with associate instance provided that the general public key that the instance presents to the load balancer matches a public key within the authentication policy for the load balancer. Classic Load Balancer supports whereas Application Load Balancer doesn't support Back-end Server Authentication.

5.1 Cross-zone Load Balancing

• Cross-zone Load equalization facilitate distribute incoming requests equally across all instances in its enabled AZs. By default, Load Balancer can equally distribute requests evenly across its enabled AZs, no matter the instances it hosts.
1. Classic Load Balancer support Cross-zone load balancing, but for Classic it should be enabled.
2. Application Load Balancer support Cross-zone load balancing but for ALB it is always enabled.

5.2 Health Checks

• Both Classic & Application Load Balancer each support Health checks to manage if the instance is healthy or unhealthy.

5.3 CloudWatch Metrics

• Both Classic & Application Load Balancer integrate with CloudWatch to produce metrics, with ALB providing additional metrics.

5.4 Access Logs

• Access logs capture detailed information about requests sent to the load balancer. Every log contains information like the time the request was received, the client’s IP address, latencies, request ways, and server responses.
1. Classic Load Balancer provide access logs.
2. Application Load Balancer also provide access logs with providing additional attributes

6. Dynamic Ports

• Classic load balancer does not support the dynamic port Mapping with ECS.
• ALB support the dynamic port Mapping with ECS which permit two containers of a service to run on a one server on dynamic ports that ALB automatically detects and reconfigures itself.

7. Host-Based Routing & Path-Based Routing

• Host-based Routing : Use host conditions to outline rules that forward requests to totally different target group supported the host name within the host header. This allows ALB to support multiple domains employing a single load balancer.
• Path-based Routing : Use path conditions to outline rules that forward requests to completely different target group supported the universal resource locator within the request. Every path condition has one path pattern. If the universal resource locator (URL) in an exceedingly request matches the trail pattern in a listener rule specifically, the request is routed victimization that rule.
1. Classic load balancer does not supports Host-based & Path-based routing.
2. Application load balancer supports Host-based & Path-based routing.

8. Deletion Protection

• Classic load balancer does not support deletion protection.
• Load balancer could not be deleted if we enabled the deletion protection. ALB Support deletion protection.

 

If you have any queries related to Elastic Load Balancing or its types, then write us at sales@cloud.in