Kyle Somers’ Post

Navigating the world of Amazon Elastic Load Balancers (ELB)? Whether you're a novice or a seasoned pro, this series of blog posts from Builder Eugene White will shed light on selecting the perfect load balancer for your needs. Ready to embark on this journey?

Don't miss out on our latest article highlighting the crucial role of Elastic Load Balancers (ELBs) on AWS. Learn how the correct selection and setup of ELBs can optimize your infrastructure, ensuring high availability, seamless user experience. Click now to uncover the potential that ELBs can bring to your business! #AWS #ElasticLoadBalancers #CloudOptimization

Hello, #connections  , 🚀 Excited to share my progress on #day70 of the #100DaysofDevOps♾ Today, Let's getting started with AWS Network Load Balancer Happy Learning😊 #90daysofdevops #90daysofdevopschallenge

Certainly! In AWS, a load balancer distributes incoming network traffic across multiple servers to ensure no single server is overwhelmed. There are primarily two types of load balancers: 1. **Application Load Balancer (ALB):** - Operates at the application layer (Layer 7) of the OSI model. - Routes traffic based on content, making it suitable for applications with varying load. - Supports features like host-based and path-based routing. 2. **Network Load Balancer (NLB):** - Works at the transport layer (Layer 4) and is ideal for handling TCP/UDP traffic. - Distributes incoming traffic evenly across targets within one or more Availability Zones. Key Concepts: - **Target Groups:** - Logical groupings of instances or services registered with a load balancer. - ALB and NLB route traffic to targets based on rules defined in target groups. - **Listeners and Rules:** - Load balancers use listeners to check for connection requests. - Rules within listeners define how traffic should be routed based on conditions. - **Health Checks:** - Load balancers periodically check the health of registered targets to ensure they are operational. - Unhealthy targets are automatically removed from the load balancing rotation. - **Auto Scaling Integration:** - Load balancers can work seamlessly with Auto Scaling groups to adapt to changing traffic conditions. - Automatically registers and deregisters instances based on scaling events. - **Security Groups:** - Associated with load balancers to control incoming and outgoing traffic. - Security groups are configured to allow traffic from specific sources to the load balancer. - **Cross-Zone Load Balancing:** - Distributes traffic evenly across instances in all enabled Availability Zones. - Helps ensure that no single zone is overwhelmed. - **SSL/TLS Offloading:** - Load balancers can handle SSL/TLS encryption and decryption, offloading this work from backend instances. Load balancers in AWS play a crucial role in ensuring high availability, fault tolerance, and scalability for applications. #awscloud #awscommunity #awscommunity #awsjobs #awsdevops #awscertification #awstraining #awscloudpractitioner #awscommunityday

📖 Story time! Our Enclaves product is built on top of Amazon Web Services (AWS) Nitro Enclaves. While building, we encountered (in addition to many others) an unexpected challenge: unexplained clock drift. The enclave clock was drifting by approximately a second per day, meaning the system time was falling further behind real-time between deployments “This level of clock drift would have huge implications for apps that rely on time-sensitive operations.” How did we solve this? Read below to find out ⬇ https://lnkd.in/er63br4J

A good article, which points out the need for protection against going too fast. IaC has enabled infra to be built very quickly, and it can be destroyed just as quickly. AWS has this in a few areas that matter, like S3 Bucket deletion. This is good, but it may also be helpful to look for protection in IaC as well, like Terraform lifecycle, and “replace then destroy” options. Take a look!

If you are running your application out of the Elastic Kubernetes Service (EKS) on AWS you likely have multiple endpoints you would like users to be able to reach. One good approach to set this up in many cases is to use an Application Load Balancer (ALB). ALB’s have lots of good features like high scalability, HTTP/2 support, sticky sessions, and request-based routing. This request-based routing is supported because the ALB has access to the HTTP headers and other information for incoming requests. This article from JV shows how you can use these headers and request paths to route traffic to different parts of your application in your Kubernetes cluster. https://lnkd.in/e75BmeBf

Hello, #connections  , 🚀 Excited to share my progress on #day71 of the #100DaysofDevOps♾ Today, Let's getting started with AWS Gateway Load Balancer Happy Learning😊 #90daysofdevops #90daysofdevopschallenge

Interviewer : What do you know about load balancers ?   Load balancers are of two types , network and application ❌❌❌❌❌❌❌❌❌❌❌❌     We do have two load balancers types , regional load balancer and VPC based load balancers .   In region we have global accelerator and in VPC we do have Network load balancer and application load balancer . The major difference between Network load balancer and application load balancer is application load balancer supports only http and https and network load balancer support tcp and udp protocal. Even http and https are tcp protocols but application load balancer doesn’t support UDP .  udp is mainly used for streaming or gamming application or online application. that is not supported by ALB this is the major difference between these two.   Interviewer : Fair enough, Can you walk me through steps as per my requirement.  So, I need 3 subnets, private only, from NV AZ 1A 1B 1C. When someone tries to access my web application, it should communicate in a secure way.   Imagine it’s a three-tier architecture: Web - App - Db. First, I'll create a VPC with 3 private subnets and 3 public subnets. Am not going to keep anything in public subnets, instead il use it for NATs and NLB’s and make sure all VPC components are configured appropriately just to avoid the miss communication between private and NAT :) Post that, with the help of ACM Amazon Certificate Manager, I'll make sure my domain is updated with SSL for secure communication. Then, I'll create target groups and select only private servers. Post that , I'll create a load balancer and make sure I'm selecting public subnets for it., I'll also select TLS under listeners with our ACM which were initially issued by AWS. Once done, I'll configure Route53 for domain forwarding. Interviewer: Impressive!! Please do subscribe my YouTube channel here and watch the detailed video on what interviewer asked.    https://lnkd.in/gEgqftTk #AWS #CloudComputing #Networking #LoadBalancing #VPC #Security #SSL #InfrastructureAsCode #DevOps #WebHosting #Route53 #ACM #TechStack #ArchitectureDesign #SysAdmin

Many people hosting websites today will have multiple subdomains for different use cases and if you're running your backend out of the Elastic Kubernetes Service (EKS) you can make these available to your end users via an AWS Application Load Balancers (ALB). You can use the same ALB for many subdomains rather than creating a different one for each. You just need to setup the proper annotations on the Ingress resources in your EKS cluster. This example from Shivanshu Sharma details all the configuration needed to setup a single ALB in AWS to route to multiple subdomains using resources inside your EKS cluster. https://lnkd.in/eawmqRNw