Create Load Balancer

Creating an Application Load Balancer

ℹ️ Information: Application Load Balancers operate at the application layer (Layer 7) and are ideal for HTTP/HTTPS traffic routing. They provide advanced request routing capabilities, support for containerized applications, and integration with AWS services.

Navigate to the Load Balancer creation interface:

  1. In the EC2 console:
    • Select Load Balancers from the left navigation pane
    • Click the Create Load Balancer button

Load Balancer Creation Interface

  1. In the Compare and select load balancer type panel:
    • Locate the Application Load Balancer section
    • Click Create

Load Balancer Type Selection

Configuring Load Balancer Settings

In the Create Application Load Balancer configuration panel:

  1. Basic configuration:
    • Load balancer name: fcaj-alb
    • Scheme: Internet-facing
    • IP address type: IPv4

Basic Load Balancer Configuration

  1. Network mapping:
    • VPC: AutoScaling-Lab
    • Availability Zones: Select all two public subnets in us-east-1a, us-east-1b

Network Mapping Configuration

⚠️ Warning: Ensure you select only public subnets for internet-facing load balancers. Private subnets cannot receive traffic from the internet.

  1. Security and routing configuration:
    • Security groups: fcaj-sg
    • Listeners and routing: Set default action to forward to fcaj-tg

Security and Routing Configuration

  1. Review the configuration summary:
    • Verify all settings are correct
    • Click Create load balancer Configuration Review
  2. Your Application Load Balancer (ALB) created successsfully Load Balancer Creation Success

Verifying Load Balancer Deployment

After successful creation

  1. Explore the load balancer’s connections:
    • Select Resource map - new to visualize the load balancer architecture
    • Verify connections to target groups and registered targets

Load Balancer Resource Map

💡 Pro tip: Application Load Balancers support content-based routing, allowing you to route requests to different target groups based on URL paths, host headers, or query parameters. This enables microservices architectures where different services handle specific request patterns.

🔒 Security Note: For production workloads, consider implementing HTTPS listeners with certificates from AWS Certificate Manager (ACM) to ensure encrypted communication between clients and your load balancer.