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:
- In the EC2 management console:
- Select Load Balancers from the left navigation pane
- Click the Create Load Balancer button

- In the “Compare and select load balancer type” panel:
- Locate the Application Load Balancer section
- Click Create

Configuring Load Balancer Settings
In the “Create Application Load Balancer” configuration panel:
- Basic configuration:
- Load balancer name:
FCJ-Management-LB
- Scheme: Internet-facing
- IP address type: IPv4

- Network mapping:
- VPC: AutoScaling-Lab
- Availability Zones: Select all three public subnets in ap-southeast-1a, ap-southeast-1b, and ap-southeast-1c

⚠️ Warning: Ensure you select only public subnets for internet-facing load balancers. Private subnets cannot receive traffic from the internet.
- Security and routing configuration:
- Security groups: FCJ-Management-SG
- Listeners and routing: Set default action to forward to FCJ-Management-TG

- Review the configuration summary:
- Verify all settings are correct
- Click Create load balancer

Verifying Load Balancer Deployment
After successful creation:
- Select FCJ-Management-LB from the load balancers list
- Review the load balancer details, including DNS name, state, and listeners

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

💡 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.