Please enable JavaScript.

Coggle requires JavaScript to display documents.

HA Architecture, HA Architecture, On-Premises Services with AWS, Elastic…

- - - - Supports homogenous migrations:
        
        ORACLE → ORACLE
        
        MSQL Server → Amazon Aurora
- - - - :star:
        
        Application Load Balancers
        
        are best suited for load balancing of HTTP and HTTPS traffic. They operate at Layer 7 and are application aware. They are intelligent, and you can create advanced request routing, sending specified request to specific web servers.
      - :star:
        
        Network Load Balancer
        
        are best suited for load balancing of TCP traffic where extreme performance is required. Operating at the connection level (Layer 4), Network Load Balancer are capable of handling millions of requests per second, while maintaining ultra-low latencies.
        Use for extreme performance !
      - :star:
        
        Classic Load Balancer
        
        are the legacy Elastic Load Balancers. You can load balance HTTP/HTTPS applications and use layer 7-specific features, such as X-Forwarded and sticky sessions. You can also use strict Layer 4 load balancing for applications that rely purely on the TCP protocol.
        
        If your application stops responding, the ELB (Classic Load Balancer) responds with a 504 error
        This means that the application is having issues. This could be either at the Web Server layer or at the Database Layer.
        Identify where the application is failing, and scale it up or out where possible
- - - - You can configure your Auto Scaling group to maintain a specified number of running instances at all times
      - To maintain the current instance levels Amazon EC2 Auto Scaling performs a periodic health check on running instances within an Auto Scaling group
      - When Amazon EC2 Auto Scaling finds an unhealthy instance, it terminates that instance and launches a new one
  - - - is the most basic way to scale your resources, where you specify only the change in the maximum, minimum, or desired capacity of your Auto Scaling group
      - Amazon EC2 Auto Scaling manages the process of creating or terminating instances to maintain the updated capacity
  - - - means that scaling actions are performed automatically as a function of time and date
      - This is useful when you know exactly when to increase or decrease the number of instances in your group, simply because the need arises on a predictable schedule
  - - - A more advanced way to scale your resources - using scaling policies - lets you define parameters that control the scaling process
      - For example, let's say that you have a web application that currently runs on two instances and you want the CPU utilization of the Auto Scaling group to stay at around 50 percent when the load on the application changes. This method is useful for scaling in response to changing conditions, when you don't know when those conditions will change. You can set up Amazon EC2 Auto Scaling to respond for you. We will do this in the next lab
  - - - You can also use Amazon EC2 Auto Scaling in combination with AWS Auto Scaling to scale resources across multiple services
      - AWS Auto Scaling can help you maintain optimal availability and performance be combining predictive scaling and dynamic scaling (proactive and reactive approaches, respectively) to scale your Amazon EC2 capacity faster
- - - - Groups uses a launch template or a launch configuration as a configuration template for its EC2 instances. You can specify information such as the AMI ID, instance type, key pair, security groups, and block device mapping for your instances
  - - - Logical component. Web server group or Application group or Database group etc
  - - - Scaling Options provides several ways for you to scale your Auto Scaling groups. For example, you can configure a group to scale based on the occurrence of specified conditions (dynamic scaling) or on a schedule