mirror of
https://github.com/nickpoida/og-aws.git
synced 2025-03-09 15:40:06 +00:00
Addressed review comments.
This commit is contained in:
parent
5edafa05ca
commit
80d80b3fb3
1 changed files with 1 additions and 1 deletions
|
@ -879,7 +879,7 @@ ALB
|
||||||
- ALBs do not (yet) support routing based on HTTP “Host” header or HTTP verb.
|
- ALBs do not (yet) support routing based on HTTP “Host” header or HTTP verb.
|
||||||
- Instances in the ALB's target groups have to either have a single, fixed healthcheck port (“EC2 instance”-level healthcheck) or the healthcheck port for a target has to be the same as its application port (“Application instance”-level healthcheck) - you can't configure a per-target healthcheck port that is different than the application port.
|
- Instances in the ALB's target groups have to either have a single, fixed healthcheck port (“EC2 instance”-level healthcheck) or the healthcheck port for a target has to be the same as its application port (“Application instance”-level healthcheck) - you can't configure a per-target healthcheck port that is different than the application port.
|
||||||
- ALBs are VPC-only (they are not available in EC2 Classic)
|
- ALBs are VPC-only (they are not available in EC2 Classic)
|
||||||
- In a target group, if there is no healthy target, all requests are routed to all targets. An example: you add a target group containing a single service (with a long init phase maybe) as target to a listener, it does not pass health checks (yet), requests will still reach your (initializing) service.
|
- In a target group, if there is no healthy target, all requests are routed to all targets. For example, if you point a listener at a target group containing a single service that has a long initialization phase (during which the health checks would fail), requests will reach the service while it is still starting up.
|
||||||
|
|
||||||
Elastic IPs
|
Elastic IPs
|
||||||
-----------
|
-----------
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue