AWS load balancers table

http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/SvcIntro.html
Abiquo supports AWS Classic load balancers and AWS Application Load Balancers

AWS will assign a previously unhealthy machine a healthy status after a number of successful health checks.
See Abiquo Configuration Properties#amazon for how to set the healthy threshold of machines in AWS in the abiquo.properties file. 

• AWS will only accept the following characters: A-Z, a-z, 0-9 and "-". 
• You cannot change the Name in AWS

• ROUND_ROBIN
• LEAST_

• AWS load balancers are created for virtual datacenter networks, which are VPC subnets
• To create a load balancer, you must assign at least one subnet
• When you edit the load balancer, you can add new subnets and delete subnets
• The platform supports VMs in different subnets attached to the same load balancer

For high availability, create private networks (subnets) in different availability zones in your virtual datacenter

• You must create at least one routing rule. There must always be at least one routing rule in the load balancer
• You can only create one routing rule per protocol and port

• To list and upload SSL server certificates to IAM your user requires IAM privileges to manage IAM
• Abiquo never stores SSL certificates, so you cannot create a routing rule for a secure connection in an Abiquo-only load balancer that is not assigned to a subnet

• If you do not create a health check, AWS will create a default health check with the following specifications:
  
  • Name in the format "PROTOCOL:port", for example, "TCP:80"
  • TCP check to one of the ports specified in a routing rule
• AWS will only allow you to create one health check per load balancer

If a firewall does not display, it may not have been properly synchronized. In this case, you will need to click Cancel, synchronize firewalls and start again creating a new load balancer