Please enable JavaScript.
Coggle requires JavaScript to display documents.
High Availability (load balancers (own DNS name - never an IP address…
High Availability
load balancers
own DNS name -
never an IP address
classic load balancers
use for keeping costs down
X-Forwarded-For header
to get IP address of end user
application load balancers
layer 7
network load balancers
layer 4
monitoring
instances
reported as
InService
OutOfService
Health Checks
gateway timeouts
sticky sessions
enable users to
stick to an EC2 instance
cross-zone load balancing
path patterns
direct traffic to different instances
based on the request URL
design
everything fails
plan for failure
Route53
health checks
failover to a different region
use multiple AZs and multiple regions
where you can
examples
multi-AZ databases
S3 storage classes
standard
infrequently accessed
Internet Gateway
VPC endpoints
Elastic Beanstalk
quickly deploy applications
it handles
capacity provisioning
load balancing
scaling
health monitoring
aimed at developers
scaling
up
e.g increase size of EC2 instance
out
increase number of instances
auto-scaling groups