Issue link: https://read.uberflip.com/i/1187300
Amazon Web Services – HPC Lens AWS Well-Architected Framework Page 1 Introduction The AWS Well-Architected Framework helps you understand the pros and cons of decisions you make while building systems on AWS. 1 By using the Framework you will learn architectural best practices for designing and operating reliable, secure, efficient, and cost-effective systems in the cloud. It provides a way for you to consistently measure your architectures against best practices and identify areas for improvement. We believe that having well-architected systems greatly increases the likelihood of business success. In this "Lens" we focus on how to design, deploy, and architect your High- Performance Computing (HPC) workloads on the AWS Cloud. HPC workloads run exceptionally well in the cloud. The natural ebb and flow and bursting characteristic of HPC workloads make them particularly well suited for pay-as-you-go cloud infrastructure. The ability to fine tune cloud resources and create cloud-native architectures accelerates the turnaround of HPC workloads naturally. For brevity, we have only covered details from the Well-Architected Framework that are specific to HPC workloads. You should still consider best practices and questions that haven't been included in this document when designing your architecture. We recommend that you read the AWS Well-Architected Framework whitepaper. 2 This paper is intended for those in technology roles, such as chief technology officers (CTOs), architects, developers, and operations team members. After reading this paper, you will understand AWS best practices and strategies to use when designing and operating HPC in a cloud environment. Definitions The AWS Well-Architected Framework is based on five pillars: operational excellence, security, reliability, performance efficiency, and cost optimization. When architecting solutions, you make tradeoffs between pillars based upon your business context. These business decisions can drive your engineering priorities. You might reduce cost at the expense of reliability in development environments, or, for mission-critical solutions, you might optimize reliability with increased costs. Security and operational excellence are generally not traded off against other pillars.