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 ELB, as it provides high availability and fault tolerance.
- It is highly recommended that a security group for ELB opens only the required ports and protocols.
- Always configure health checks for ELB on appropriate ports and protocols. If ELB is created for a web server, use HTTP/HTTPS in health checks, instead of TCP.
- 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 ELB.
- Use ELB deletion protection to prevent accidental deletion.
- Use cross-zone load balancing in a Classic Load Balancer for evenly distributing the load across...