ELB best practices are as follows:
- While defining a load balancer, it is recommended you identify target AZs and target groups
- Use multiple AZs in the ELB as it provides high availability and fault tolerance
- It is highly recommended that a security group for the ELB opens only required ports and protocols
- Always configure health checks for the ELB on appropriate ports and protocols
- If the ELB is created for a web server, use the HTTP/HTTPS protocol in health checks instead of the TCP protocol
- Do not create internet-facing ELBs for internal needs
- Use SSL security certificates to encrypt and decrypt HTTPS connections where possible
- If a heavy traffic spike is expected on a given schedule, contact AWS support and ask them to pre-warm the ELB
- Use ELB deletion protection from accidental deletion
- Use cross-zone load balancing in a Classic Load Balancer for evenly distributing the load across all EC2 instances in associated AZs
- Carefully enable connection draining on ELBs associated with...