Please enable JavaScript.
Coggle requires JavaScript to display documents.
M4 (ELB, auto scaling, Termination policy, route 53) - Coggle Diagram
M4
ELB
ELB node
If you only provide one subnet, ELB will launch two nodes in the Availability Zone of your subnet.
If you provide two subnets in different Availability Zones, ELB will launch one node in each Availability Zone.
-
-
listener
-
rule
Each rule specifies a target group, condition, and priority. When the condition is met, the traffic is forwarded to the target group.
You must define a default rule for each listener, and you can add rules that specify different target groups based on the content of the request (also known as content-based routing).
-
auto scaling
-
-
simple scaling
he main issue with simple scaling is that after a scaling activity is started, the policy must wait for the scaling activity or health check replacement to complete and the cooldown period to expire before responding to additional alarms. Cooldown periods help to prevent the initiation of additional scaling activities before the effects of previous activities are visible.
In contrast, with step scaling the policy can continue to respond to additional alarms, even while a scaling activity or health check replacement is in progress. Therefore, all alarms that are breached are evaluated by Amazon EC2 Auto Scaling as it receives the alarm messages.
-
route 53
feature
● Use the Route 53 console to register a domain name and configure Route 53 to route internet traffic to
-
● After you register your domain name, Route 53 automatically creates a public hosted zone that has the
-
● To route traffic to your resources, you create records, also known as resource record sets, in your
-
● You can create special Route 53 records, called alias records, that route traffic to S3 buckets,
CloudFront distributions, and other AWS resources.
-