AWS Well-Architected Framework

• 1($) - Focuses on operations in the cloud, including monitoring, incident response, and continuous improvement.

• 2($) - Emphasizes protecting data, systems, and assets through strong security practices and controls.

• 3($) - Concerns the ability of a system to recover from failures and meet business and customer demands.

• 4($) - Focuses on using computing resources efficiently to meet system requirements and adapting to changing demands.

• 5($) - Involves managing and reducing costs associated with cloud services while delivering the necessary performance and functionality.

• 6($) - Addresses the environmental impact of cloud operations and focuses on designing architectures that reduce energy consumption and waste, promoting sustainability in cloud practices.

• 1($) provide a high-level strategy or set of guidelines for responding to a particular type of situation or incident. They describe what needs to be done, but not necessarily how to do it in detail.
• 2($) provide detailed, step-by-step instructions for performing specific tasks or resolving particular issues. They focus on the "how" rather than the "what" or "why."

An email notification is sent to the administrator when the CPU utilization of an EC2 instance exceeds 80% for 5 consecutive minutes.

• 1($)

  A new EC2 instance is launched, or a configuration parameter is modified in an RDS database.

• 2($)

  An alert is triggered when the CPU utilization of an EC2 instance exceeds 80% for 5 consecutive minutes.

• 3($)

  A DDoS attack disrupts the availability of your web application, or a data breach occurs due to a security vulnerability.

The ability of a workload to perform its required function correctly and consistently over an expected period of time

1($) provide direction to your organization on expected outcomes,

2($) provide specific measurable outcomes to be achieved for your workloads.