Ingress overview
Understanding Ingress is crucial for efficiently managing incoming data or requests to your AWS resources.
Ingress is a Kubernetes resource that manages external access to services within a cluster. It acts as a reverse proxy, routing traffic to the appropriate service based on defined rules.
Ingress is more Kubernetes-specific and focused on routing within a cluster, while Elastic Load Balancers (ELB) is an AWS service designed for distributing traffic across multiple resources in the AWS cloud. This helps in load balancing and scalability.
The three types of load balancers in AWS are:
Application Load Balancer (ALB)
This load balancer operates at the application layer (Layer 7) of the OSI model. It is designed to distribute incoming traffic across multiple targets based on rules that are configured for specific URLs, HTTP methods, or other application-level parameters.
Network Load Balancer (NLB)
This type of load balancer operates at the transport layer (Layer 4) of the OSI model. It is specifically designed for handling TCP, UDP, and TLS traffic with high throughput and ultra-low latency.
Classic Load Balancer (CLB)
This is an original load balancer type provided by Amazon Web Services (AWS). It operates at both Layer 4 (Transport Layer) and Layer 7 (Application Layer) of the OSI model. It is designed to distribute incoming application or network traffic across multiple targets in one or more Availability Zones.
AWS Ingress Benefits
- To track traffic patterns and load on our services.
- To optimize performance and resource allocation.
- To identify delays in request handling, allowing you to pinpoint bottlenecks and optimize service response times.
For installing Ingress, see Installing Ingress and for viewing the dashboard, see Ingress dashboard.