Issue link: https://read.uberflip.com/i/1187300
Amazon Web Services – HPC Lens AWS Well-Architected Framework Page 21 4. Lambda saves job and parameters in an Amazon DynamoDB table. 5. DynamoDB triggers a Lambda function to process the incoming job and determines job segmentation based on data indexes. 6. Lambda submits each segment as a message to Amazon Simple Notification Service (Amazon SNS). 7. Amazon SNS triggers a Lambda function to process each segment. 8. Lambda segments pull required data from Amazon S3 for processing. 9. Results are saved back to a DynamoDB table once each segment finishes. 10. User is updated with results during client-side polling to API Gateway. The Pillars of the Well-Architected Framework This section describes HPC in the context of the five pillars of the Well- Architected Framework. Each pillar discusses design principles, definitions, best practices, evaluation questions, considerations, key AWS services, and useful links. Operational Excellence Pillar The operational excellence pillar includes the ability to run and monitor systems to deliver business value and continually improve supporting processes and procedures. Design Principles In the cloud, there are a number of principles that drive operational excellence: • Traditional versus cloud-native: HPC architectures typically take one of two forms. The first is a traditional cluster configuration with a head login instance, compute nodes, scheduler, and queue. The second is considered to be cloud-native with automated deployments, the use of serverless capability, managed services, and a single workload per (ephemeral) cluster. While the best approach depends on the environment sought for HPC users, cloud-native architectures can further optimize operational considerations.