- cache-proxy ›
Link one AWS ELB to many AWS EC2 instances you have running. An alternative to HAProxy that can support SSL if configured correctly. Only works for HTTP/HTTPS services.
To deploy this charm you will need at a minimum:
- a AWS cloud environment
- working Juju installation
- a successful bootstrap
You will want to deploy this charm on an existing host, possibly your 0 host. Mostly because this service configures an ELB host and does not require resources itself to operate.
juju deploy aws-ec2-elb --to 0
It may be useful to setup a config yaml before deploy, so you start with the right settings:
Then deploy with this command:
juju deploy aws-ec2-elb --config myconfig.yaml --to 0
The ELB has no name by default, which causes it to not configure. This is intentional because it does not undeploy ELB's
when you change the name (currently no built-in mechanism to know the changed values on config-changed).
- Set the elb-name, aws_access_key, aws_secret_key, elb_region and elb_availability_zones in one go.
- HTTP is enabled on port 80 by default, at this point you can add some websites and it will update.
- Enable HTTPS and set the certificate ID if you want HTTPS
- Force local upgrade: juju upgrade-charm --force --repository charms aws-ec2-elb
- (string) AWS access key
- (string) AWS secret key
- (string) comma seperated list of AZ's for this ELB
- (string) AWS name for the ELB
- (string) AWS Region for this ELB
- (int) How often the check is made in seconds.
- (int) Number of seconds the load balancer will wait for a check to return a result.
- (int) ELB port for regular HTTP
- (string) AWS SSL Certificate ID
- (int) ELB port for HTTPS