| vCloud Element | Notes |
|---|
| vCloud Director documentation |
|
| SSL certificates | - 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 network
|
| Healthy threshold | - AWS will assign a previously unhealthy machine a healthy status after a number of successful health checks. Check the value configured for your platform with your system administrator.
|
| Modifications | You cannot change the following attributes in AWS: |
| Load balancer Name | - AWS will only accept the following characters: A-Z, a-z, 0-9 and "-".
- You cannot change the name after Abiquo creates the load balancer in AWS (when a valid load balancer is saved with a subnet assigned to it)
|
| Algorithm | |
| Abiquo-only load balancers | - AWS load balancers are created for virtual datacenter networks, which are VPC subnets
- Abiquo will not create a load balancer in AWS until it is assigned to at least one subnet
- You can create a load balancer in Abiquo only, by not supplying a subnet
- If you delete the load balancer directly in the provider, it will remain in Abiquo only
|
| High availability | - For high availablility, create private networks (subnets) in different availability zone in your virtual datacenter
- Abiquo 4.0+ supports virtual machines in different subnets attached to the same load balancer
|
| Multiple incoming connections | Use one load balancer with multiple incoming connections to different ports |
| Routing rules | - 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 path
|
| Subnet | - If you do not supply a subnet when creating the load balancer, Abiquo will not create the LB in AWS
- When you edit the load balancer, you can add new subnets and delete subnets
- Abiquo 4.0+ supports virtual machines in different subnets attached to the same load balancer
|
| Routing rule protocol in | AWS accepts HTTP, HTTPS, TCP |
| Routing rule port in | AWS accepts 80, 443 and 1024-65535 inclusive |
| SSL certificate | Can be a new certificate or an existing one registered in AWS with an ARN |
| Health check | - 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
|
| Firewalls | - 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
|